← Browse

@herdiansah/social-crisis-manager

B

Handle social media crises with strategic response and reputation management. Use when the user needs to manage a PR crisis, handle negative feedback storms, or protect brand reputation.

skillclaude

Install

agr install @herdiansah/social-crisis-manager --target claude

Writes 1 file into .claude/skills/, pinned to git-de25bbd4.

  • .claude/skills/social-crisis-manager/SKILL.md

Document


name: social-crisis-manager description: Handle social media crises with strategic response and reputation management. Use when the user needs to manage a PR crisis, handle negative feedback storms, or protect brand reputation.

Social Crisis Manager

When to Use This Skill

Use this skill when you need to:

  • Enhance team collaboration during a crisis
  • Improve stakeholder engagement
  • Facilitate clear dialogue under pressure
  • Manage reputation during negative events

Not Recommended For

  • Tasks requiring technical development
  • Deep data analysis (use social-listening-analyst)

Quick Reference

ActionCommand/Trigger
Create social crisis managercrisis management
Review and optimizereview social crisis manager
Get best practicessocial crisis manager best practices

Core Workflows

Workflow 1: Initial Social Crisis Manager Creation

Goal: Create a high-quality social crisis response plan from scratch.

  1. Discovery: Understand requirements, severity, and objectives.
  2. Planning: Develop strategy, messaging, and approach.
  3. Execution: Implement the plan (responses, statements).
  4. Review: Evaluate results and sentiment shift.
  5. Optimization: Refine based on feedback and outcome.

Workflow 2: Advanced Social Crisis Manager Optimization

Goal: Refine and optimize existing social crisis management for better results.

  1. Research: Gather relevant information and monitor mentions.
  2. Analysis: Evaluate options and approaches.
  3. Decision: Choose the best path forward.
  4. Implementation: Execute with precision.
  5. Measurement: Track success metrics (sentiment, volume).

Best Practices

  • Start with Clear Objectives: Define what success looks like (e.g., stopping the spread, changing sentiment) before beginning work.
  • Follow Industry Standards: Leverage proven frameworks (e.g., apologies, transparency) and best practices in communication.
  • Iterate Based on Feedback: Continuously improve responses based on public reaction and user input.
  • Document Your Process: Keep track of decisions and outcomes for future reference (post-mortem).
  • Focus on Quality: Prioritize excellence and empathy over speed, though speed is critical.

Checklist

Before considering your work complete:

  • Objectives clearly defined and understood
  • Research and discovery phase completed
  • Strategy or plan documented
  • Implementation matches requirements
  • Quality standards met (empathetic, checking facts)
  • Stakeholders informed and aligned
  • Results measured against goals
  • Documentation updated
  • Feedback collected
  • Next steps identified

Common Mistakes

MistakeWhy It's BadBetter Approach
Skipping researchLeads to misaligned solutions/tone deaf responsesInvest time in understanding context
Ignoring best practicesReinventing the wheel (often badly)Study successful examples/frameworks first
No clear metricsCan't measure successDefine KPIs upfront (e.g. sentiment score)

Integration Points

  • Tools: Integration with common communication platforms and social listening tools.
  • Workflows: Fits into existing team communication workflows.
  • Team: Collaborates with legal, PR, and leadership stakeholders.

Success Metrics

Track these metrics to measure effectiveness:

  • Quality of output (response reception)
  • Time to completion (response time)
  • Stakeholder satisfaction
  • Impact on business goals (reputation damage control)
  • Reusability of approach

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-de25bbd4a5732026-07-31