CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

86%

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

72%

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

A well-organized, lean procedural reference for an instruction-only skill, with explicit validation steps — a real strength. It is held back by abstract directives that lack operational specificity and by validation that sits as an end-checklist rather than inline feedback loops.

Suggestions

Make abstract directives operational: replace 'Address underlying grievances' and 'Maintain stability' with concrete, sequenced actions (e.g., specific steps to diagnose grievance sources and act on them).

Inline the validation checkpoints within each workflow phase and add a validate→fix→retry feedback loop for the destructive rebellion-management steps, rather than relegating all checks to a detached end section.

Tighten the repeated feedback-channel list: 公卿献诗, 瞽献曲, 史献书 appears in both the Prevention Phase and the Validation section — reference it once and have Validation confirm it by name.

DimensionReasoningScore

Conciseness

The body is lean bullet points with brief classical-Chinese quotes and translations that are domain-specific source material, not padding about concepts Claude already knows; it does not over-explain.

3 / 3

Actionability

Concrete elements exist (named feedback channels, the 召公 crown-prince example), but several directives are abstract — 'Address underlying grievances', 'Maintain stability', 'Suppress firmly but justly' — leaving operational detail incomplete, which fits score 2 rather than 3.

2 / 3

Workflow Clarity

Processes are clearly numbered across phases and an explicit Validation section with checkpoints exists, but validation is a detached end-checklist rather than inline checkpoints with error-recovery feedback loops that the score-3 anchor expects for destructive operations like rebellion management.

2 / 3

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into clear, well-signaled sections (Natural Disaster Response, Rebellion Management, Regency Protocol, Validation), which per the simple-skills note earns a 3 without external references.

3 / 3

Total

10

/

12

Passed

Description

100%

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 description: it pairs an explicit 'Use when...' trigger with a concrete, multi-part capability list in a distinctive niche. Voice follows the accepted 'Use when...' imperative form rather than first/second person, so no specificity penalty applies.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'earthquake interpretation, historical pattern recognition, rebellion prevention... regency protocols, and power restoration' — rather than vague language, matching the score-3 anchor for listing several specific concrete actions.

3 / 3

Completeness

It 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 an explicit trigger clause.

3 / 3

Trigger Term Quality

'political crises, natural disasters, or rebellions' are natural terms a user would actually say when needing this skill, giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

The Zhou-dynasty crisis-management niche with its specific triggers (earthquake interpretation, regency protocols) is clearly distinct and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
baojie/shiji-kb
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.