CtrlK
BlogDocsLog inGet started
Tessl Logo

emergency-field-succession

Use when a ruler dies on military campaign and succession must be secured before news spreads. Covers securing final wishes, maintaining secrecy, road closures, heir retrieval with military escort, and formal installation before announcing the death, following King Zhao's field succession precedent.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 compact, well-sequenced procedure with concrete steps and a verification checklist that closes the feedback loop. It is appropriately concise and well-organized for a single-purpose skill with no bundle dependencies.

DimensionReasoningScore

Conciseness

Lean body that assumes competence — a brief overview and six numbered steps with no padding or explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Concrete, specific guidance throughout an instruction-only procedure — 'Close roads to prevent information leak', 'Send trusted agents to bring the designated heir', 'Use military escort for protection' — actionable without code.

3 / 3

Workflow Clarity

A clearly sequenced six-step process culminating in a dedicated Verification section with explicit validation checkpoints (confirm wishes were witnessed, validate secrecy/Installation, check army intact), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

A short, well-organized single-file skill with clear sections and no need for external references; per the simple-skills note this warrants a top score.

3 / 3

Total

12

/

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.

The description is specific, third-person, and pairs a clear 'Use when' trigger with a concrete list of the actions the skill covers, plus a historical precedent that anchors it. It clearly answers both what and when with minimal padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'securing final wishes, maintaining secrecy, road closures, heir retrieval with military escort, and formal installation before announcing the death' — matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers both 'what' (the Covers... action list) and 'when' via an explicit 'Use when a ruler dies on military campaign and succession must be secured before news spreads' trigger clause.

3 / 3

Trigger Term Quality

Natural trigger phrasing a user would say — 'ruler dies on military campaign', 'succession must be secured', 'before news spreads' — gives good coverage of the domain's terms.

3 / 3

Distinctiveness Conflict Risk

A highly specific niche (emergency field succession on campaign) with distinct triggers, unlikely to fire for any other skill.

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.