[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4BYN1MXY53MSD2NFWWPE3":3,"skill-same:01M7F4BYN1MXY53MSD2NFWWPE3":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F4BYN1MXY53MSD2NFWWPE3","crypto-scam-and-security-hygiene",null,"Screen crypto tokens, venues, airdrops, links, wallets, and transaction requests for rug pulls, honeypots, impersonation, phishing, malicious approvals, fake returns, and unsafe secret handling. Use on every scout candidate and when asked whether something is legitimate, safe to connect, a scam, or how to protect a wallet.","cwik-tech\u002Foctopus","cwik-tech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54542292?v=4","01M7F42E123GEHVK6RWC5MSWJ9","Tomasz Cwik","01M7F42E1PD4P54MTG8PG32VCV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fcrypto-risk-compliance-analyst\u002Fskills\u002Fcrypto-scam-and-security-hygiene\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: crypto-scam-and-security-hygiene\ndescription: >\n  Screen crypto tokens, venues, airdrops, links, wallets, and transaction\n  requests for rug pulls, honeypots, impersonation, phishing, malicious\n  approvals, fake returns, and unsafe secret handling. Use on every scout\n  candidate and when asked whether something is legitimate, safe to connect,\n  a scam, or how to protect a wallet.\n---\n\n# Crypto Scam and Security Hygiene\n\n## Purpose\n\nFind signs of theft or irreversible wallet compromise without exposing the user to the thing being tested. This is a passive review: use supplied materials, independently observed public pages, verified contract data, and read-only evidence. Never connect a wallet, sign, approve, install, or transfer funds to test legitimacy.\n\n## Mandatory Screen\n\n### Identity and link integrity\n\n- Compare the exact domain, app publisher, social handle, legal entity, and contract address across independent official sources.\n- Treat lookalike domains, shortened links, unsolicited direct messages, support accounts that initiate contact, and links embedded in unexpected tokens or airdrops as high risk.\n- Do not infer legitimacy from HTTPS, search ranking, an app-store presence, follower count, or a copied brand mark.\n\n### Promotion and return claims\n\n- Flag guaranteed returns, low-risk high yield, urgency, secret methods, recovery fees, tax or unlock fees paid to release funds, and pressure to move the conversation privately.\n- Look for coordinated promotion, recycled posts, undisclosed incentives, fake engagement, and sudden attention without independent developer or user evidence.\n- Treat displayed profits and successful small withdrawals as insufficient proof that later withdrawals will work.\n\n### Contract and market controls\n\n- Confirm the contract address independently before analyzing it.\n- Check mint, pause, blacklist, upgrade, fee-change, transfer, and ownership powers; proxy implementation control; holder and liquidity concentration; and whether sell restrictions create a honeypot pattern.\n- Treat an audit as one evidence item, not a guarantee. Record scope, version, date, unresolved findings, and whether the reviewed code matches the deployed contract.\n\n### Wallet and approval safety\n\n- Never request or repeat a seed phrase, private key, password, recovery code, authentication token, or screen share containing one.\n- Never ask the user to connect a wallet, sign a message, approve a token, install a wallet, or send a test transfer for verification.\n- Explain what a proposed signature or approval can authorize. Flag unlimited or unrelated permissions and unknown spenders.\n- Recommend only reversible, provider-documented mitigations: verify through bookmarked official channels, use read-only explorers, separate high-value holdings from experimental activity, review existing approvals, and follow the wallet or hardware provider's official recovery procedure.\n\n## Risk Grade\n\n- **Critical:** Secret requested or exposed; untrusted signing or approval request; confirmed malicious contract or impersonation; withdrawal requires another payment; funds are at immediate risk.\n- **High:** Identity or contract mismatch, owner-controlled sell restrictions, unexplained unlimited approval, guaranteed returns, concentrated control with no safeguards, or multiple coordinated-promotion signals.\n- **Medium:** Important evidence is missing, audit scope is unclear, privileges are broad but disclosed, or promotion is suspicious but not conclusive.\n- **Low:** No material red flag found in the reviewed evidence. This means only that this screen found no blocker; it does not mean safe.\n- **Unknown:** Evidence cannot establish identity, contract, permissions, or withdrawal behavior.\n\nAny Critical or High result blocks sizing until the board records why the signal is false or how the exposure is removed. Unknown identity or contract address also blocks sizing.\n\n## Output\n\n- **Object reviewed:** Exact token, contract, domain, account, venue, or request.\n- **Evidence boundary:** What was and was not observed.\n- **Risk grade:** Critical \u002F High \u002F Medium \u002F Low \u002F Unknown.\n- **Signals:** Finding, evidence, plausible benign explanation, and what would resolve it.\n- **Immediate safety action:** Only when current funds or secrets may be exposed; use official recovery and reporting channels.\n- **Board gate:** BLOCK \u002F CLEAR WITH CONDITIONS \u002F NO BLOCKER FOUND, with remaining uncertainty stated.\n\n## Red Lines\n\n- Never describe Low risk as safe, legitimate, endorsed, or guaranteed.\n- Never interact with an untrusted contract, link, app, bot, or wallet to test it.\n- Never shame a user who may have been deceived; prioritize stopping further loss and preserving evidence.\n- Never promise recovery or recommend paying anyone who claims they can recover funds.\n","# Crypto Scam and Security Hygiene\n\n## Purpose\n\nFind signs of theft or irreversible wallet compromise without exposing the user to the thing being tested. This is a passive review: use supplied materials, independently observed public pages, verified contract data, and read-only evidence. Never connect a wallet, sign, approve, install, or transfer funds to test legitimacy.\n\n## Mandatory Screen\n\n### Identity and link integrity\n\n- Compare the exact domain, app publisher, social handle, legal entity, and contract address across independent official sources.\n- Treat lookalike domains, shortened links, unsolicited direct messages, support accounts that initiate contact, and links embedded in unexpected tokens or airdrops as high risk.\n- Do not infer legitimacy from HTTPS, search ranking, an app-store presence, follower count, or a copied brand mark.\n\n### Promotion and return claims\n\n- Flag guaranteed returns, low-risk high yield, urgency, secret methods, recovery fees, tax or unlock fees paid to release funds, and pressure to move the conversation privately.\n- Look for coordinated promotion, recycled posts, undisclosed incentives, fake engagement, and sudden attention without independent developer or user evidence.\n- Treat displayed profits and successful small withdrawals as insufficient proof that later withdrawals will work.\n\n### Contract and market controls\n\n- Confirm the contract address independently before analyzing it.\n- Check mint, pause, blacklist, upgrade, fee-change, transfer, and ownership powers; proxy implementation control; holder and liquidity concentration; and whether sell restrictions create a honeypot pattern.\n- Treat an audit as one evidence item, not a guarantee. Record scope, version, date, unresolved findings, and whether the reviewed code matches the deployed contract.\n\n### Wallet and approval safety\n\n- Never request or repeat a seed phrase, private key, password, recovery code, authentication token, or screen share containing one.\n- Never ask the user to connect a wallet, sign a message, approve a token, install a wallet, or send a test transfer for verification.\n- Explain what a proposed signature or approval can authorize. Flag unlimited or unrelated permissions and unknown spenders.\n- Recommend only reversible, provider-documented mitigations: verify through bookmarked official channels, use read-only explorers, separate high-value holdings from experimental activity, review existing approvals, and follow the wallet or hardware provider's official recovery procedure.\n\n## Risk Grade\n\n- **Critical:** Secret requested or exposed; untrusted signing or approval request; confirmed malicious contract or impersonation; withdrawal requires another payment; funds are at immediate risk.\n- **High:** Identity or contract mismatch, owner-controlled sell restrictions, unexplained unlimited approval, guaranteed returns, concentrated control with no safeguards, or multiple coordinated-promotion signals.\n- **Medium:** Important evidence is missing, audit scope is unclear, privileges are broad but disclosed, or promotion is suspicious but not conclusive.\n- **Low:** No material red flag found in the reviewed evidence. This means only that this screen found no blocker; it does not mean safe.\n- **Unknown:** Evidence cannot establish identity, contract, permissions, or withdrawal behavior.\n\nAny Critical or High result blocks sizing until the board records why the signal is false or how the exposure is removed. Unknown identity or contract address also blocks sizing.\n\n## Output\n\n- **Object reviewed:** Exact token, contract, domain, account, venue, or request.\n- **Evidence boundary:** What was and was not observed.\n- **Risk grade:** Critical \u002F High \u002F Medium \u002F Low \u002F Unknown.\n- **Signals:** Finding, evidence, plausible benign explanation, and what would resolve it.\n- **Immediate safety action:** Only when current funds or secrets may be exposed; use official recovery and reporting channels.\n- **Board gate:** BLOCK \u002F CLEAR WITH CONDITIONS \u002F NO BLOCKER FOUND, with remaining uncertainty stated.\n\n## Red Lines\n\n- Never describe Low risk as safe, legitimate, endorsed, or guaranteed.\n- Never interact with an untrusted contract, link, app, bot, or wallet to test it.\n- Never shame a user who may have been deceived; prioritize stopping further loss and preserving evidence.\n- Never promise recovery or recommend paying anyone who claims they can recover funds.\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fcrypto-risk-compliance-analyst\u002Fskills\u002Fcrypto-scam-and-security-hygiene","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus","www.cuteoctopus.site","https:\u002F\u002Fgithub.com\u002Fcwik-tech","2026-10-27 06:12:19",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cwik-tech\u002Foctopus --skill crypto-scam-and-security-hygiene",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill crypto-scam-and-security-hygiene",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill crypto-scam-and-security-hygiene","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fcrypto-risk-compliance-analyst\u002Fskills\u002Fcrypto-scam-and-security-hygiene\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7F5MQVQ3CHGM77Q51M4B1AC","twenty-year-land-plan","Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Ftwenty-year-land-plan\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F5MGQ8JSV27SFDQVVGFQE3","thematic-gut-check","Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fthematic-gut-check\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7F5M8V64Y0ZD8PTPWEJQXJ9","supply-pipeline-gut-check","Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fsupply-pipeline-gut-check\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7F5M3J2Q146BJC13TD3YCXF","ruin-scenario-mapping","Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fruin-scenario-mapping\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7F5KZDS0DYD172P6HS0WXEM","revenue-cost-architecture","Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Frevenue-cost-architecture\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7F5KP1CNQMYAVCDTV4EEW3J","replacement-cost-stress-test","Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Freplacement-cost-stress-test\u002FSKILL.md",[],[]]