respond-to-military-defeat

Use when recovering from a major military defeat or rebuilding forces after a loss. Based on Duke Mu's response to the Xiao defeat, covers personal accountability, commander restoration, public acknowledgment, and rebuilding strategy.

Quality

92%

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

85%

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

The content is well-structured and concise with a clear sequenced workflow plus explicit validation checkpoints, suiting a simple instruction-only skill. Its main weakness is actionability, where several steps remain general and lack concrete examples or templates.

Suggestions

Tighten vague bullets into concrete directives — e.g., replace 'Increase support and resources for them' with specific actions like 'Reinforce their units with fresh troops and replenish supplies'.

Add a concrete example or template for the public acknowledgment, such as a short sample declaration text that admits fault and records the lesson.

Specify what 'symbolic acts' means in step 6 beyond the parenthetical 'burning boats', or commit to one concrete act rather than an open-ended suggestion.

Dimension	Reasoning	Score
Conciseness	The body is lean — short numbered steps with 1–3 tight bullets each, no padding, no explaining of concepts Claude already knows — so every token earns its place per the score-3 anchor.	3 / 3
Actionability	Guidance is concrete in places ('Wear mourning clothes', 'Return commanders to their former ranks') but several bullets stay general ('Strengthen forces over time', 'Increase support and resources for them') and no concrete templates or examples (e.g., a sample public declaration) are provided, leaving key details incomplete.	2 / 3
Workflow Clarity	Seven steps are clearly sequenced and supported by a Decision Points branch and an explicit Validation section with three checkpoints ('Verify...', 'Confirm...', 'Check... before initiating rebuilding'), satisfying the clear-sequence-with-validation score-3 anchor; this is not a destructive/batch op so no cap applies.	3 / 3
Progressive Disclosure	At roughly 50 lines with no external references needed (no bundle files present) and cleanly organized into Overview, Steps, Decision Points, Expected Outcomes, and Validation sections, it meets the simple-skill bar for score-3 organization.	3 / 3
	Total	11 / 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 strong: it pairs a clear 'Use when' trigger with a concrete enumeration of the skill's four capabilities, grounded in a specific historical example that makes it distinctive. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	The description lists multiple specific concrete actions — 'personal accountability, commander restoration, public acknowledgment, and rebuilding strategy' — matching the multi-action score-3 anchor rather than the partial-coverage score-2 anchor.	3 / 3
Completeness	It explicitly answers both 'what' ('covers personal accountability, commander restoration, public acknowledgment, and rebuilding strategy') and 'when' via a 'Use when...' clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	It leads with a natural 'Use when' trigger and surfaces phrasings a user would actually say ('recovering from a major military defeat', 'rebuilding forces after a loss'), giving good keyword coverage rather than the limited single-term score-2 case.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and distinctive — 'Based on Duke Mu's response to the Xiao defeat' with triggers around military defeat/rebuilding — making overlap with other skills unlikely.	3 / 3
	Total	12 / 12 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_025/SKILL.md
Commit: 79c272f

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