crisis-management-protocol

Use when responding to political crises, natural disasters, or rebellions. Covers earthquake interpretation, historical pattern recognition, rebellion prevention through free expression (防民之口甚於防水), regency protocols, and power restoration.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%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.

A well-organized, concise protocol body with clear sequencing and a validation section. Its main weakness is actionability: several steps remain high-level directives rather than concrete, executable guidance.

Suggestions

Replace abstract directives like 'Apply lessons to current situation' and 'Address underlying grievances' with concrete, checkable actions (e.g., specific signals to look for, specific remediation steps to take).

Move validation items inline as checkpoints within each phase (e.g., verify feedback channels are functioning before moving from Prevention to Active Response) rather than only listing them at the end.

Consider trimming the generic 'Expected Outcomes' section or folding its content into the phase where each outcome is produced, to tighten the token budget further.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, using terse bullets and quoted principles with translations rather than padding; the only slight excess is the generic 'Expected Outcomes' section, keeping it just below the fully lean anchor.	4 / 5
Actionability	Concrete specifics exist (named feedback channels, historical precedents) but many directives are abstract ('Apply lessons to current situation', 'Address underlying grievances') without the concrete execution steps that would make guidance fully actionable.	3 / 5
Workflow Clarity	Phases are clearly sequenced (Prevention, Active Response, Regency) with numbered steps, and a Validation section provides verification items; not a 5 because checkpoints are end-loaded rather than inline feedback loops within each phase.	4 / 5
Progressive Disclosure	With no bundle files and no need for external references, the content is well-organized into clearly headed sections that stand alone, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	16 / 20 Passed

Description

87%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 strong, well-structured description that clearly states both capability and trigger conditions with concrete, distinctive phrasing. Minor room to add a few more natural synonyms, but it explicitly satisfies both what and when.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities (earthquake interpretation, historical pattern recognition, rebellion prevention, regency protocols, power restoration) with only minor coverage gaps, fitting the 'several specific actions' anchor above the 1-2 action midpoint.	4 / 5
Completeness	Explicitly answers both 'what' ('Covers earthquake interpretation... regency protocols, and power restoration') and 'when' ('Use when responding to political crises, natural disasters, or rebellions') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases ('political crises, natural disasters, or rebellions') are terms a user would plausibly say, with good though not exhaustive keyword coverage; not a 5 because common synonyms/variants are limited.	4 / 5
Distinctiveness Conflict Risk	The highly specific Zhou-dynasty framing (防民之口甚於防水, regency/power-restoration) carves a clear niche with distinct triggers and minimal conflict risk against generic skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: baojie/shiji-kb
Path: kg/ontology/ontology-v1/skus/procedural/skill_018/SKILL.md
Commit: 6b836e3

Reviewed: 13 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.