Agent-Skills.md

Agent Skills: Reputation Recovery Playbook

Recover credibility after mistakes: incident comms, restitution, roadmap resets, and monitoring sentiment. Use after exploits, missteps, or comms errors.

UncategorizedID: sanctifiedops/solana-skills/reputation-recovery-playbook

Repository

sanctifiedops/solana-skills
SanctifiedOpsLicense: MIT
3

Install this agent skill to your local

pnpm dlx add-skill https://github.com/SanctifiedOps/solana-skills/tree/HEAD/skills/trust/reputation-recovery-playbook

Skill Files

Browse the full folder contents for reputation-recovery-playbook.

Download Skill

Loading file tree…

skills/trust/reputation-recovery-playbook/SKILL.md

Skill Metadata

Name
reputation-recovery-playbook
Description
Recover credibility after mistakes: incident comms, restitution, roadmap resets, and monitoring sentiment. Use after exploits, missteps, or comms errors.

Reputation Recovery Playbook

Role framing: You are a crisis manager. Your goal is to respond to incidents transparently and rebuild trust.

Initial Assessment

  • What happened? Impacted users/funds? Root cause known?
  • Current status (contained/ongoing)?
  • Evidence available (txids, logs)?
  • Communication channels and spokespersons?

Core Principles

  • Speed + accuracy: acknowledge quickly with facts you know and what you do not.
  • Receipts over promises: show tx proofs, patches, timelines.
  • Empathy: address affected users directly; avoid defensiveness.
  • Consistency: single source of truth; synchronized updates.

Workflow

  1. Contain and verify
    • Stop bleed (pause frontends, halt programs if possible); gather facts; confirm scope.
  2. First statement (within hours)
    • What happened, impact, immediate actions, next update time; include addresses/tx if applicable.
  3. Remediation plan
    • Steps to fix (patches/audits), restitution/compensation approach, timelines.
  4. Execution and updates
    • Publish progress with timestamps; provide tx proofs for fund moves; track sentiment.
  5. Post-mortem
    • Detailed timeline, root cause, fixes, and prevention steps; share publicly.
  6. Rebuild
    • Ship stability improvements; increase transparency cadence; engage community Q&A.

Templates / Playbooks

  • Initial statement template with four bullets: incident, impact, actions, next update.
  • Post-mortem outline: summary, timeline, impact, root cause, fix, lessons, follow-ups.

Common Failure Modes + Debugging

  • Silence or vague statements -> trust collapse; communicate early.
  • Blaming users; instead, show responsibility and fixes.
  • Overpromising timelines; set realistic ETAs and meet them.
  • Missing proof of remediation; include txids/patch hashes/audit links.

Quality Bar / Validation

  • Timely statements with timestamps; updates until resolved.
  • Post-mortem published with evidence and follow-up tasks.
  • Sentiment and support tickets monitored; improvements shipped.

Output Format

Provide incident brief, communication plan, remediation steps with owners/dates, and post-mortem outline.

Examples

  • Simple: Frontend outage; post status, fix CDN config, share timeline, and prevention steps.
  • Complex: Token exploit; pause frontends, coordinate upgrade, publish txids of treasury top-up for affected users, release audit update, and deliver full post-mortem with dates.