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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%Weight 40%Scale 1-3

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

A well-structured, actionable runbook with strong workflow sequencing and validation gates, weakened only by mild verbosity from repeated propose-path phrasing and dense inline cross-linking.

Suggestions

Collapse the repeated 'via an authorized operation: propose request to registry-events.py to memory/events/channels.ndjson' phrasing into one defined term referenced later to cut repetition.

Consolidate the cross-skill links into the Reference Materials / Next Best Skill sections so the Instructions stay focused on the procedure.

Tighten the Skill Contract Writes/Promotes bullets, which restate several file paths already named in the Instructions.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no conceptual filler), but the authorized 'operation: propose' / 'registry-events.py' phrasing and inter-skill cross-links are restated across several sections, which could be tightened.	2 / 3
Actionability	As an instruction-only skill it gives concrete, copy-ready guidance — velocity multiples 3x/5x/10x, all-clear at <1.5x baseline for 24h, named memory paths, and a named approver per statement — meeting the fully-executable-guidance anchor.	3 / 3
Workflow Clarity	An 8-step sequence opens with routing checks and ends with a stand-down that re-runs the pre-publish gate before un-pausing, giving explicit validation checkpoints for the risky pause/un-pause operation.	3 / 3
Progressive Disclosure	Sections are well organized and references are listed one level deep in Reference Materials, but no bundle files exist here and the ~70-line body is dense; the external cross-repo references could be more clearly separated from inline content.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 tightly scoped, third-person description that pairs concrete capabilities with natural-language triggers and explicit out-of-scope routing. It earns the top anchor on every dimension with no over-claims or fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — a 1-5 severity ladder, the pause-the-queue rule, a pre-approved holding-statement library, a spokesperson/approval matrix, and a post-crisis retro template — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers what (ladder, pause rule, statement library, matrix, retro) and when (a 'Use when the user asks to…' clause with concrete triggers), and adds when-not exclusions, satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Quotes three natural user phrases ('build our social crisis protocol', 'mentions are exploding — what do we do first', 'when do we pause the posting queue') plus routing negations, giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear social-crisis niche with distinct triggers and explicit exclusions (deliverability-qa for email incidents, launch-day-conductor inside launch windows), making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

75%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 4a77c48

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.