Reconstructs after the fact what happened in a leveraged crypto liquidation crash: branching ratios, fill-log timelines, tape reconstruction, participation anomalies, and evidence standards. Analyses past cascades with rigorous data; it never predicts future liquidations or prices. Use when asking 'cascade forensics', 'analyse this liquidation event', 'what happened in this crash', 'branching ratio', 'reconstruct the timeline', 'was this a cascade'. Not for reading a live set-up (ac-liquidation-hunt-analysis), not for the trade record (ac-crypto-trading-discipline), not for generic research method (ac-deep-researcher).
cp -r cryptoskill/skills/exchanges/anoscranel-ac-cascade-forensics .claude/skills/clawhub install anoscranel-ac-cascade-forensicsCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
read_only Phase 1 single-mode classification — multi-mode breakdown deferred to Phase 2.
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed