AGENT SKILL

crypto-plain-language-explainer

Rewrite crypto and finance jargon into plain language with concrete analogies, and split every explanation into need-to-know versus can-skip for a newcomer investor. Shared across the crypto investment board. Use as the final pass on any output going to the user, when a specialist answer is dense with terms the user has not shown they understand, or when a decision record needs its newcomer summary.

License 许可
Apache-2.0
所属仓库
cwik-tech/octopus
最近更新
2026-10-27
Stars
★ 0
Forks
0

01 前言 Front Matter

name
crypto-plain-language-explainer
description
Rewrite crypto and finance jargon into plain language with concrete analogies, and split every explanation into need-to-know versus can-skip for a newcomer investor. Shared across the crypto investment board. Use as the final pass on any output going to the user, when a specialist answer is dense with terms the user has not shown they understand, or when a decision record needs its newcomer summary.

03 SKILL.md 正文

Crypto Plain-Language Explainer

Purpose

The board's reasoning is only useful if the user can follow it. This skill preserves the substance and the uncertainty while removing the vocabulary barrier. It never simplifies a risk away; if the honest answer is "this could go to zero," the plain-language version says exactly that.

Method

  1. Scan the draft for every term a newcomer would not know. Typical offenders: TVL, FDV, float, unlock, slashing, sequencer, oracle, impermanent loss, restaking, MEV, L2, rollup, bridge, wrapped asset, basis, funding rate, drawdown, sizing, risk budget.
  2. Decide for each term: define inline, replace with plain wording, or move to can-skip.
  3. Rewrite using the sentence rules below.
  4. Split the final output into two labelled blocks: Need to know and Can skip for now.
  5. Check that no risk, downside, or uncertainty statement was softened in the rewrite.

Sentence rules

  • Define a term the first time it appears, in the same sentence, in under fifteen words.
  • Prefer the concrete over the abstract: "the team can release 20% more tokens in March" beats "significant unlock overhang."
  • One idea per sentence. If a sentence has "which" or "whereas," split it.
  • Numbers keep their dates: "as of 12 August 2026" stays attached.
  • Never replace a total-loss warning with "volatile" or "high risk." Say "you could lose all of it."

Analogy bank

Use these when they fit; do not force them.

Concept Analogy
Private key A signing key: anyone who gets it may move the funds, while losing every recovery path may lock you out
Exchange custody A company controls the keys, so access depends on both its systems and your legal rights against it
Proof of stake Validators post a bond; some protocols penalize specified faults, while rewards may combine fees and new issuance
Smart contract A vending machine — it does exactly what it was built to do, including the bugs
Upgradeable contract A vending machine whose owner can rewire it overnight
L2 An express lane that settles up with the main highway's toll booth periodically
Bridge A border crossing with extra guards or machinery that can fail between the two ledgers
Token unlock Early employees' stock options all vesting the same week
FDV vs market cap The price of the whole building versus the price of the floors currently for sale
Impermanent loss A pool rebalances as relative prices change, so its return can lag simply holding the assets
Yield from emissions A store paying you in its own coupons that it prints freely
Invalidation trigger The tripwire you set before entering so you do not argue with yourself later
Risk budget The amount you have already decided you can afford to set on fire this year

Need-to-know versus can-skip

Need to know contains only what changes the user's decision or their understanding of the downside. Usually two to four sentences:

  • What the board decided and the single biggest reason.
  • The worst realistic outcome.
  • The one event that would mean the board was wrong.
  • Any action the user needs to take or condition they need to watch.

Can skip for now contains the mechanics, the secondary risks, the full evidence trail, and the debate. Label it clearly and keep it, because the user may come back to it.

Quality check before returning

  • Would a smart adult with no crypto background understand the need-to-know block without looking anything up?
  • Is every downside stated at least as bluntly as in the original?
  • Did any date or source fall off a number?
  • Did any contrarian objection disappear in the rewrite?

04 同仓库更多 Skills

cwik-tech
cwik-tech/octopus

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.

★ 0
cwik-tech
cwik-tech/octopus

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.

★ 0
cwik-tech
cwik-tech/octopus

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.

★ 0
cwik-tech
cwik-tech/octopus

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.

★ 0
cwik-tech
cwik-tech/octopus

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.

★ 0
cwik-tech
cwik-tech/octopus

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.

★ 0