Resilience Classification Skill
Identify stablecoins where the default inference (from backing + governance) is incorrect and apply overrides.
When to Invoke
- After the resilience types and default inference are implemented
- When a new stablecoin is added to the tracker
- When auditing resilience scores for accuracy
Process
Step 1 — Identify candidates
Read all coins from src/lib/stablecoins.ts. For each, apply the default inference rules (see inferResilienceDefaults() in src/lib/report-cards.ts). Flag coins where the default is likely wrong based on:
collateral text containing keywords: "Solana", "tBTC", "WBTC", "delta-neutral", "perpetual", "CEX", "off-exchange", "Copper", "Ceffu", "Fireblocks", "bridged"
pegMechanism text containing: "Solana", "Bitcoin L2", "not Ethereum", "Tron"
contracts[] listing only non-Ethereum chains
backing = crypto-backed but collateral text mentions RWAs, bridges, or exotic strategies
- Coins on this known-override list: HYUSD, USDe, meUSD, USDD, sUSD (Synthetix), USDJ
Step 2 — Research each candidate
For each flagged coin, in parallel:
WebFetch official docs for collateral composition, custody arrangement, and chain architecture
WebSearch for "{coin name}" stablecoin collateral custody chain to find independent analysis
- Cross-reference with existing
collateral and pegMechanism text fields
Step 3 — Classify
For each coin, determine the correct tier:
| Sub-factor |
Question |
Tiers |
chainRisk |
Where does the core protocol live and where is collateral held? |
ethereum (100), stage1-l2 (66), established-alt-l1 (33), unproven (0) |
collateralQuality |
What are the trust assumptions in backing assets? |
native (100), eth-lst (66), alt-lst-bridged-or-mixed (33), exotic (0) |
custodyModel |
Who holds the collateral and can it be verified on-chain? |
onchain (100), institutional (50), cex (0) |
Classification rules:
- chainRisk: Based on where the protocol's smart contracts and collateral vaults live, NOT where the token is bridged to
- collateralQuality: For mixed collateral, use the tier of the riskiest significant component (>15% of backing). Stablecoin portions don't count here (handled by dependency risk)
- custodyModel: If ANY significant portion is held off-chain by a non-institutional custodian, classify as
cex
- When uncertain between two tiers, choose the riskier (lower score) tier
Step 4 — Present findings
For each coin needing an override, present:
## {Name} ({Symbol}) — ID: {id}
### Default inference
- chainRisk: {inferred} — {correct/wrong because...}
- collateralQuality: {inferred} — {correct/wrong because...}
- custodyModel: {inferred} — {correct/wrong because...}
### Proposed overrides
- {field}: {value} — {justification with source URL}
### No override needed
- {fields where default is correct}
Step 5 — Apply
After user approval, edit src/lib/stablecoins.ts to add only the override fields that differ from defaults. Example:
usd("123", "Example", "EX", "crypto-backed", "decentralized", {
// ... existing fields ...
chainRisk: "established-alt-l1",
collateralQuality: "alt-lst-bridged",
}),
Run npm run build to verify.
1---2name: resilience-classify3description: Research and classify stablecoins for resilience sub-factor overrides (chainRisk, collateralQuality, custodyModel). Run after types/defaults are implemented to identify coins needing explicit overrides.4metadata:5 source: https://skillmd.com/skills/diegosouzapw/resilience-classify6---78# Resilience Classification Skill910Identify stablecoins where the default inference (from backing + governance) is incorrect and apply overrides.1112## When to Invoke1314- After the resilience types and default inference are implemented15- When a new stablecoin is added to the tracker16- When auditing resilience scores for accuracy1718## Process1920### Step 1 — Identify candidates2122Read all coins from `src/lib/stablecoins.ts`. For each, apply the default inference rules (see `inferResilienceDefaults()` in `src/lib/report-cards.ts`). Flag coins where the default is likely wrong based on:2324- `collateral` text containing keywords: "Solana", "tBTC", "WBTC", "delta-neutral", "perpetual", "CEX", "off-exchange", "Copper", "Ceffu", "Fireblocks", "bridged"25- `pegMechanism` text containing: "Solana", "Bitcoin L2", "not Ethereum", "Tron"26- `contracts[]` listing only non-Ethereum chains27- `backing` = `crypto-backed` but collateral text mentions RWAs, bridges, or exotic strategies28- Coins on this known-override list: HYUSD, USDe, meUSD, USDD, sUSD (Synthetix), USDJ2930### Step 2 — Research each candidate3132For each flagged coin, in parallel:33- `WebFetch` official docs for collateral composition, custody arrangement, and chain architecture34- `WebSearch` for `"{coin name}" stablecoin collateral custody chain` to find independent analysis35- Cross-reference with existing `collateral` and `pegMechanism` text fields3637### Step 3 — Classify3839For each coin, determine the correct tier:4041| Sub-factor | Question | Tiers |42|---|---|---|43| `chainRisk` | Where does the core protocol live and where is collateral held? | `ethereum` (100), `stage1-l2` (66), `established-alt-l1` (33), `unproven` (0) |44| `collateralQuality` | What are the trust assumptions in backing assets? | `native` (100), `eth-lst` (66), `alt-lst-bridged-or-mixed` (33), `exotic` (0) |45| `custodyModel` | Who holds the collateral and can it be verified on-chain? | `onchain` (100), `institutional` (50), `cex` (0) |4647**Classification rules:**48- **chainRisk**: Based on where the protocol's smart contracts and collateral vaults live, NOT where the token is bridged to49- **collateralQuality**: For mixed collateral, use the tier of the riskiest significant component (>15% of backing). Stablecoin portions don't count here (handled by dependency risk)50- **custodyModel**: If ANY significant portion is held off-chain by a non-institutional custodian, classify as `cex`51- When uncertain between two tiers, choose the riskier (lower score) tier5253### Step 4 — Present findings5455For each coin needing an override, present:5657```58## {Name} ({Symbol}) — ID: {id}5960### Default inference61- chainRisk: {inferred} — {correct/wrong because...}62- collateralQuality: {inferred} — {correct/wrong because...}63- custodyModel: {inferred} — {correct/wrong because...}6465### Proposed overrides66- {field}: {value} — {justification with source URL}6768### No override needed69- {fields where default is correct}70```7172### Step 5 — Apply7374After user approval, edit `src/lib/stablecoins.ts` to add only the override fields that differ from defaults. Example:7576```typescript77usd("123", "Example", "EX", "crypto-backed", "decentralized", {78 // ... existing fields ...79 chainRisk: "established-alt-l1",80 collateralQuality: "alt-lst-bridged",81}),82```8384Run `npm run build` to verify.