Install any skill in seconds. Free to start, no credit card required.
Get Started Free →renehdzgtz/crypto-crisis-communications
Expert system for managing communications during crises in Web3 and crypto environments.
Passed 18 of 22 test cases with the skill, and 15 of 22 without it.
and 1 more in the full report
4 fixed14 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
A pseudonymous account with 150 followers posted a tweet alleging our bridge contract is insolvent. Should we immediately publish a formal public press release and tag major news outlets, or evaluate specific metrics first?
| Checked | Without skill | With skill |
|---|---|---|
| Advises against immediate public engagement for small unamplified claims | Passed | Passed |
| Establishes engagement traction thresholds such as exceeding 500 interactions or influencer pickup before responding publicly | Missed | Passed |
The instructions your model reads when the skill loads.
For: Protocol marketing leads, DAO communication teams, Web3 founders, community managers
Philosophy: In crypto, your response speed and honesty matter more than the incident itself. Silence kills trust. Transparency rebuilds it.
Before executing any module, ask:
Then classify and route:
| Crisis Type | Severity | Module |
|---|---|---|
| Smart contract exploit / hack | 🔴 Critical | [MODULE 1: Security Incident Response] |
| FUD / misinformation campaign | 🟡 High | [MODULE 2: FUD & Misinformation] |
| Token price crash / community panic | 🟡 High | [MODULE 3: Market Crisis Response] |
| Governance attack / hostile proposal | 🟡 High | [MODULE 4: Governance Crisis] |
| Team controversy / personal scandal | 🟠 High | [MODULE 5: Reputational Crisis] |
| Negative press / media attack | 🟠 Medium | [MODULE 6: Media Crisis] |
| Community revolt / mod controversy | 🟡 Medium | [MODULE 7: Community Conflict] |
| Post-crisis recovery plan | Any | [MODULE 8: Recovery & Trust Rebuild] |
Trigger: Smart contract was exploited, funds were drained, vulnerability was found, or protocol was attacked.
Minute 0–15: Internal lockdown
test cases passed, vs 15 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.