crypto-portfolio-construction
Build a crypto portfolio policy from user-approved loss capacity, liquidity needs, time horizon, concentration limits, custody constraints, rebalancing rules, and stress scenarios without inventing allocation defaults. Use when setting up or reviewing a portfolio, or when drift, concentration, liquidity, or drawdown may have breached its standing rules.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- crypto-portfolio-construction
- description
- Build a crypto portfolio policy from user-approved loss capacity, liquidity needs, time horizon, concentration limits, custody constraints, rebalancing rules, and stress scenarios without inventing allocation defaults. Use when setting up or reviewing a portfolio, or when drift, concentration, liquidity, or drawdown may have breached its standing rules.
03 SKILL.md 正文
Crypto Portfolio Construction
Purpose
Write the standing portfolio rules in calm conditions so later decisions do not improvise risk tolerance under pressure. This skill does not infer how much loss a user can bear and does not treat stablecoins as cash. It derives a policy from explicit constraints or, when they are missing, compares labelled scenarios without choosing one.
Required Inputs
| Input | Why it matters |
|---|---|
| Capital allocated to crypto | Denominator for book-level limits |
| Relationship to the user's broader finances | Tests whether crypto loss threatens near-term obligations |
| Liquidity needs and time horizon | Prevents locking or risking money needed soon |
| Maximum crypto-book and position loss the user explicitly accepts | Anchors the stress budget |
| Existing positions, venues, wallets, and liabilities | Reveals concentration, leverage, custody, and tax constraints |
| Governing jurisdiction and account or entity type where material | Identifies legal and tax questions for the risk seat |
| Current review packet | Diligence, risk, contrarian, market, and dated-fact inputs |
Do not invent a missing value. Mark the recommendation PENDING and provide scenarios showing how the missing choice changes the result.
Procedure
1. Establish the loss boundary
- Keep emergency funds, near-term liabilities, and money the user cannot afford to lose outside the crypto risk budget.
- Record the maximum book-level loss and position-level loss the user has explicitly affirmed.
- Separate willingness to tolerate volatility from financial capacity to absorb permanent loss.
- If these differ, the lower capacity governs the analysis.
2. Define functional buckets
Use buckets only when they match the user's purpose:
- Core thesis: Longer-horizon assets reviewed under an explicit thesis and invalidation rule.
- Speculative sleeve: Positions modeled under a total-loss scenario.
- Reserve: Optional liquidity for future decisions. A stablecoin or custodial balance still carries issuer, depeg, venue, and access risk and must pass risk review.
The labels do not supply percentages. Derive ranges from the loss boundary and stress tests.
3. Run stress scenarios
At minimum model:
- Core assets suffer a severe historical or user-selected drawdown.
- Every speculative position goes to zero together.
- The reserve suffers a stated stablecoin, custody, or access loss.
- Correlated positions decline together while liquidity and exit depth worsen.
- Any leverage or borrowing reaches its liquidation or repayment condition.
For each assumption, cite the source or label it as a scenario rather than a forecast. The proposed allocation must remain within the user's affirmed book-level loss under the combined scenario they choose.
4. Set concentration constraints
Measure exposure by both ticker and shared failure factor:
- base-asset beta and ecosystem dependence;
- common bridge, oracle, custodian, exchange, or stablecoin;
- narrative and liquidity source;
- common governance, treasury, or counterparty.
Ask the user to approve the maximum exposure to each material factor. If no cap exists, compare at least three labelled cap scenarios and show the stress loss under each; do not name one "balanced" or "recommended."
5. Define rebalancing and exit rules
Record:
- target ranges and the user-approved drift that triggers review;
- review cadence and the events that require an unscheduled review;
- whether rebalancing uses new contributions, sales, or both;
- liquidity, fees, taxes, lockups, and slippage that may make a rule impractical;
- thesis invalidation, risk-clearance withdrawal, and position-cap breaches;
- any profit-taking rule the user explicitly chooses.
Do not supply a universal take-profit ladder, calendar, or drawdown response. Show how candidate rules would have behaved under multiple scenarios, including whipsaw and tax costs.
6. Define market-regime handling before use
A regime label may inform a pre-agreed rule but does not determine allocation by itself. If the user wants regime scaling, document the exact scale, evidence threshold, maximum change, and review trigger before applying it. Without that policy, show regime effects as scenarios only.
Output
- Decision status: READY or PENDING, with missing user choices named.
- Loss boundary: Book-level and position-level limits explicitly affirmed by the user.
- Buckets: Purpose and derived allocation ranges, not generic profile defaults.
- Stress table: Scenario, assumption source, portfolio loss, liquidity impact, and breached constraint.
- Concentration map: Ticker and shared failure-factor exposures.
- Standing rules: Rebalancing, invalidation, review, and optional profit-taking rules with costs and exceptions.
- Scenario comparison: At least three labelled alternatives when a material constraint is missing; no preferred option selected.
- Professional-review questions: Material financial, legal, or tax decisions outside the board's competence.
Red Lines
- Do not infer loss capacity, net worth, liquidity needs, or risk tolerance.
- Do not call a generic allocation conservative, balanced, aggressive, safe, or suitable for the user.
- Do not treat stablecoins or exchange balances as risk-free reserves.
- Do not turn a market-regime label or diligence score into an allocation percentage through a fixed multiplier.
- Do not recommend action while a material user constraint or required specialist review is missing.
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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.