[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4BDMBADPKDGG0YFD2EJ5B":3,"skill-same:01M7F4BDMBADPKDGG0YFD2EJ5B":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},"01M7F4BDMBADPKDGG0YFD2EJ5B","crypto-position-sizing",null,"Calculate conditional crypto position sizes from an explicitly approved loss budget, conservative executable-loss scenarios, current portfolio exposure, liquidity, and completed diligence and risk reviews. Use when asked how much to buy, whether a cleared asset fits the portfolio, how to rebalance, or how staged entry and invalidation choices change the amount at risk.","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-portfolio-strategist\u002Fskills\u002Fcrypto-position-sizing\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: crypto-position-sizing\ndescription: >\n  Calculate conditional crypto position sizes from an explicitly approved loss\n  budget, conservative executable-loss scenarios, current portfolio exposure,\n  liquidity, and completed diligence and risk reviews. Use when asked how much\n  to buy, whether a cleared asset fits the portfolio, how to rebalance, or how\n  staged entry and invalidation choices change the amount at risk.\n---\n\n# Crypto Position Sizing\n\n## Purpose\n\nSize from loss capacity rather than upside. A numeric recommendation is allowed only after the user has affirmed the relevant loss budget and the required board reviews are complete. Otherwise return labelled scenarios that expose the missing decision without selecting one.\n\n## Preconditions\n\nAll must be present before a recommendation:\n\n1. **User-approved constraints:** Crypto-book size, position loss budget, liquidity needs, time horizon, and any relevant tax, custody, or leverage constraints.\n2. **Diligence:** Asset and protocol findings, including unknowns and severity, not merely a score.\n3. **Risk clearance:** Custody, counterparty, regulatory or tax uncertainty, scam, and wallet-security blockers.\n4. **Contrarian review and dated facts:** Material objections recorded and current inputs sourced.\n5. **Portfolio policy:** Remaining bucket and shared-factor capacity.\n6. **Market assessment:** Conditional regime evidence and what would change it; no automatic multiplier.\n7. **Invalidation and exit mechanics:** A thesis condition plus a realistic estimate of loss if exit occurs late or cannot execute.\n\nIf any item is missing, return **PENDING** with scenarios only.\n\n## Method\n\n### 1. Choose a conservative loss fraction\n\nFor each plausible exit path, estimate the fraction of the position that could be lost after slippage, gaps, fees, taxes, lockups, depegs, contract failure, or total loss. Use 100% for any path where capital can become unrecoverable. Do not treat a stop price as executable when liquidity cannot support the proposed size.\n\n### 2. Calculate the loss-budget ceiling\n\n```text\nloss-budget ceiling = user-approved position loss budget \u002F conservative loss fraction\n```\n\nExample: if the user has affirmed a 0.5% book-level loss budget and the conservative executable-loss fraction is 50%, the loss-budget ceiling is 1% of the book. This is arithmetic, not a recommendation.\n\n### 3. Apply independent ceilings\n\nThe candidate size cannot exceed the smallest of:\n\n- loss-budget ceiling;\n- remaining bucket capacity;\n- ticker concentration limit;\n- shared-factor concentration limit;\n- liquidity and slippage capacity;\n- custody, venue, jurisdiction, or tax constraint;\n- any user-approved regime rule.\n\nShow every ceiling, its source, and which one binds. A diligence score may affect the scenario assumptions or block eligibility, but it does not map mechanically to a percentage.\n\n### 4. Model dependence and correlation\n\nUse dated measurements over more than one relevant window where available. Correlation and beta are estimates that can change sharply during stress. Also map shared bridges, oracles, exchanges, stablecoins, ecosystems, and counterparties that return data misses. If measurements are unavailable, do not substitute a category label as fact; present a conservative shared-factor scenario.\n\n### 5. Compare execution choices\n\nFor a single entry and any staged alternative, show:\n\n- entry condition and amount;\n- expected fees, slippage, tax or reporting implications, and operational complexity;\n- what new evidence a later tranche waits for;\n- maximum loss if the adverse event occurs before all tranches or between them.\n\nStaging is not automatically safer. It may reduce timing concentration while increasing costs or leaving the user exposed during later entries.\n\n### 6. Separate thesis invalidation from order mechanics\n\nAn invalidation trigger states why the thesis is wrong. An executable exit plan states how the position can be reduced under actual liquidity and custody constraints. Record both. For illiquid, locked, bridged, or contract-dependent assets, include a scenario where exit is unavailable.\n\n### 7. Return recommendation or scenarios\n\n- **Recommendation:** Only when all preconditions are met. State size as a maximum under the named assumptions, not a promise of suitability or return.\n- **Scenarios:** When a material input is missing, show at least three neutral labels such as lower-loss, middle-loss, and higher-loss. For each, state the assumed loss budget and resulting ceiling. Do not select one for the user.\n\n## Output\n\n- **Gate status:** CLEARED or PENDING, with missing items.\n- **User-approved loss budget:** Percent of book and dollars when supplied.\n- **Loss scenarios:** Trigger, conservative loss fraction, liquidity assumptions, and evidence status.\n- **Ceiling table:** Each independent cap, source, and binding constraint.\n- **Maximum conditional size:** Or neutral scenario range if constraints are incomplete.\n- **Execution comparison:** Single entry and staged alternatives with conditions and costs.\n- **Invalidation and exit:** Thesis trigger, executable plan, and no-exit scenario.\n- **Residual risks:** What remains even if every condition is followed.\n- **Professional-review questions:** Financial or tax choices requiring a qualified adviser.\n\n## Red Lines\n\n- Do not choose the user's acceptable loss, allocation profile, reserve floor, take-profit ladder, or minimum meaningful position.\n- Do not use a diligence score, market label, or arbitrary beta threshold as a direct sizing table.\n- Do not imply a stop order caps loss where gaps, liquidity, custody, or contract failure can prevent execution.\n- Do not recommend action before all required reviews and material user constraints are present.\n- Do not present the calculation as personalized professional financial or tax advice.\n","# Crypto Position Sizing\n\n## Purpose\n\nSize from loss capacity rather than upside. A numeric recommendation is allowed only after the user has affirmed the relevant loss budget and the required board reviews are complete. Otherwise return labelled scenarios that expose the missing decision without selecting one.\n\n## Preconditions\n\nAll must be present before a recommendation:\n\n1. **User-approved constraints:** Crypto-book size, position loss budget, liquidity needs, time horizon, and any relevant tax, custody, or leverage constraints.\n2. **Diligence:** Asset and protocol findings, including unknowns and severity, not merely a score.\n3. **Risk clearance:** Custody, counterparty, regulatory or tax uncertainty, scam, and wallet-security blockers.\n4. **Contrarian review and dated facts:** Material objections recorded and current inputs sourced.\n5. **Portfolio policy:** Remaining bucket and shared-factor capacity.\n6. **Market assessment:** Conditional regime evidence and what would change it; no automatic multiplier.\n7. **Invalidation and exit mechanics:** A thesis condition plus a realistic estimate of loss if exit occurs late or cannot execute.\n\nIf any item is missing, return **PENDING** with scenarios only.\n\n## Method\n\n### 1. Choose a conservative loss fraction\n\nFor each plausible exit path, estimate the fraction of the position that could be lost after slippage, gaps, fees, taxes, lockups, depegs, contract failure, or total loss. Use 100% for any path where capital can become unrecoverable. Do not treat a stop price as executable when liquidity cannot support the proposed size.\n\n### 2. Calculate the loss-budget ceiling\n\n```text\nloss-budget ceiling = user-approved position loss budget \u002F conservative loss fraction\n```\n\nExample: if the user has affirmed a 0.5% book-level loss budget and the conservative executable-loss fraction is 50%, the loss-budget ceiling is 1% of the book. This is arithmetic, not a recommendation.\n\n### 3. Apply independent ceilings\n\nThe candidate size cannot exceed the smallest of:\n\n- loss-budget ceiling;\n- remaining bucket capacity;\n- ticker concentration limit;\n- shared-factor concentration limit;\n- liquidity and slippage capacity;\n- custody, venue, jurisdiction, or tax constraint;\n- any user-approved regime rule.\n\nShow every ceiling, its source, and which one binds. A diligence score may affect the scenario assumptions or block eligibility, but it does not map mechanically to a percentage.\n\n### 4. Model dependence and correlation\n\nUse dated measurements over more than one relevant window where available. Correlation and beta are estimates that can change sharply during stress. Also map shared bridges, oracles, exchanges, stablecoins, ecosystems, and counterparties that return data misses. If measurements are unavailable, do not substitute a category label as fact; present a conservative shared-factor scenario.\n\n### 5. Compare execution choices\n\nFor a single entry and any staged alternative, show:\n\n- entry condition and amount;\n- expected fees, slippage, tax or reporting implications, and operational complexity;\n- what new evidence a later tranche waits for;\n- maximum loss if the adverse event occurs before all tranches or between them.\n\nStaging is not automatically safer. It may reduce timing concentration while increasing costs or leaving the user exposed during later entries.\n\n### 6. Separate thesis invalidation from order mechanics\n\nAn invalidation trigger states why the thesis is wrong. An executable exit plan states how the position can be reduced under actual liquidity and custody constraints. Record both. For illiquid, locked, bridged, or contract-dependent assets, include a scenario where exit is unavailable.\n\n### 7. Return recommendation or scenarios\n\n- **Recommendation:** Only when all preconditions are met. State size as a maximum under the named assumptions, not a promise of suitability or return.\n- **Scenarios:** When a material input is missing, show at least three neutral labels such as lower-loss, middle-loss, and higher-loss. For each, state the assumed loss budget and resulting ceiling. Do not select one for the user.\n\n## Output\n\n- **Gate status:** CLEARED or PENDING, with missing items.\n- **User-approved loss budget:** Percent of book and dollars when supplied.\n- **Loss scenarios:** Trigger, conservative loss fraction, liquidity assumptions, and evidence status.\n- **Ceiling table:** Each independent cap, source, and binding constraint.\n- **Maximum conditional size:** Or neutral scenario range if constraints are incomplete.\n- **Execution comparison:** Single entry and staged alternatives with conditions and costs.\n- **Invalidation and exit:** Thesis trigger, executable plan, and no-exit scenario.\n- **Residual risks:** What remains even if every condition is followed.\n- **Professional-review questions:** Financial or tax choices requiring a qualified adviser.\n\n## Red Lines\n\n- Do not choose the user's acceptable loss, allocation profile, reserve floor, take-profit ladder, or minimum meaningful position.\n- Do not use a diligence score, market label, or arbitrary beta threshold as a direct sizing table.\n- Do not imply a stop order caps loss where gaps, liquidity, custody, or contract failure can prevent execution.\n- Do not recommend action before all required reviews and material user constraints are present.\n- Do not present the calculation as personalized professional financial or tax advice.\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fcrypto-portfolio-strategist\u002Fskills\u002Fcrypto-position-sizing","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-position-sizing",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill crypto-position-sizing",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill crypto-position-sizing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fcrypto-portfolio-strategist\u002Fskills\u002Fcrypto-position-sizing\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",[],[]]