CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crisis-response-planner

Use when the user asks to "build our social crisis protocol", "mentions are exploding — what do we do first", or "when do we pause the posting queue"; produces a 1-5 severity ladder with tunable Estimated trigger thresholds (mention-velocity multiples vs the 7-day listening baseline, sentiment flip, journalist/regulator contact, employee-conduct class), the first-mechanical-action rule — pause ALL scheduled posts AND paid amplification, with dated state markers dropped to the channels proposal protocol and reconciled post-incident — a pre-approved holding-statement library with committed update cadences, when-NOT-to-post rules, a spokesperson/approval matrix, and a post-crisis retro template; re-runs the social-quality-auditor pre-publish gate before un-pausing the queue. Not for email deliverability incidents (blocklist, spam-rate spikes) — use deliverability-qa; inside a launch window launch-day-conductor owns incident handling. 社媒危机预案/暂停队列/声明库/发言人矩阵

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced, highly actionable runbook with strong validation checkpoints (receipts, gate re-run, open-state semantics) covering a genuinely multi-step, high-stakes workflow. Its weaknesses are token-level redundancy — the proposal-path mechanics and routing exclusions are restated several times — and reliance on external repo paths that cannot be verified from this bundle.

Suggestions

State the 'operation: propose request to registry-events.py' mechanics once in the Skill Contract and reference it tersely elsewhere; it currently appears four times across Instructions and Save Results.

Consolidate the launch-window stand-down and deliverability routing exclusions into one place (the scope guard already covers them) instead of repeating them in step 1, Reference Materials, and the description of instructions.

Include the actual retro-template fields and a skeleton of the protocol document so the expected output is copy-paste ready rather than described.

DimensionReasoningScore

Conciseness

The body does not explain concepts Claude already knows, but it is noticeably repetitive: the 'authorized operation: propose request to registry-events.py' formula appears four times, and the channel-registry sole-writer rule and the launch-window/deliverability routing each repeat two to three times across the scope guard, instructions, Save Results, and references. This matches 'mostly efficient but could be tightened'; it is above level 2 because the padding is redundant constraint restatement rather than unnecessary explanation.

3 / 5

Actionability

Guidance is concretely executable for an instruction-only skill: default thresholds (3x/5x/10x the 7-day baseline), receipt fields (actor, time, status, platform evidence), named statement scenario families, NEEDS_INPUT fallback when no baseline exists, and copy-paste Quick Start prompts. It stops short of level 5 because the retro template and the protocol document's actual shapes are described rather than shown.

4 / 5

Workflow Clarity

Eight numbered steps in a clear sequence (mode routing → ladder → pause receipts → statements → when-not-to-post → matrix → stand-down → retro) with explicit validation checkpoints and feedback loops: missing/partial receipts keep surfaces OPEN and escalated, 'Do not declare stand-down complete from an unpause proposal alone', the gate re-run before un-pausing, and a 'Done when' checklist. This matches the top anchor including error-recovery loops.

5 / 5

Progressive Disclosure

Sections are well organized (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with clearly signaled one-level references. It is not level 5 because no bundle files exist and every reference resolves to a path outside the skill directory (e.g. ../../../references/echo-benchmark.md), so the split between inline content and referenced material is structural rather than verified.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense but high-signal description that explicitly states concrete capabilities, natural trigger phrases, and hard negative boundaries against neighboring skills. Its only weakness is that trigger coverage relies on three quoted phrasings without the broader synonym set users might naturally use for a social/PR crisis.

DimensionReasoningScore

Specificity

The description enumerates the full deliverable set concretely — 'produces a 1-5 severity ladder with tunable Estimated trigger thresholds (mention-velocity multiples vs the 7-day listening baseline...)', 'pause ALL scheduled posts AND paid amplification', 'pre-approved holding-statement library', 'when-NOT-to-post rules', 'spokesperson/approval matrix', and 'post-crisis retro template'. This matches the anchor for multiple specific concrete actions with comprehensive coverage; it is not level 4 because there are no material gaps in what the skill produces.

5 / 5

Completeness

It opens with an explicit 'Use when...' clause containing concrete trigger phrases and separately states what the skill produces, including the pre-publish gate re-run before un-pausing. Both 'what' and 'when' are explicit and concrete, matching the top anchor; level 4 would require the 'when' to be less specific than the quoted phrasings provided.

5 / 5

Trigger Term Quality

Natural quoted trigger phrases are present ('build our social crisis protocol', 'mentions are exploding — what do we do first', 'when do we pause the posting queue') alongside concrete negative signals (blocklist, spam-rate spikes). It falls below level 5 because common user synonyms such as 'PR crisis', 'social media backlash', or 'viral for the wrong reasons' are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (social crisis protocol with severity ladder and queue-pause mechanics) and it explicitly fences off adjacent skills: 'Not for email deliverability incidents (blocklist, spam-rate spikes) — use deliverability-qa; inside a launch window launch-day-conductor owns incident handling.' Minimal conflict risk, matching level 5 rather than level 4's minor-overlap framing.

5 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 32 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

social/host/crisis-response-planner/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.