military-campaign-protocol

Use when planning a righteous military campaign against a tyrannical ruler. Covers just-cause verification, alliance building, troop declaration, combat rules of engagement, and post-victory administration based on Tang and Wu Wang's campaigns.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./kg/ontology/ontology-v1/skus/procedural/skill_015/SKILL.md

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 concise, well-organized protocol with a clear phase sequence and a closing validation section. Weaker on actionability and workflow clarity, where several steps are abstract and validation is terminal rather than woven through the steps as feedback loops.

Suggestions

Tighten abstract steps like 'Maintain discipline' and 'Restore proper governance' into concrete, checkable actions (e.g. specific formation rules or named governance tasks).

Move verification earlier and add per-phase checkpoints with a validate→fix→retry loop, since regime-change operations are destructive and currently rely on a single terminal validation section.

Dimension	Reasoning	Score
Conciseness	The body is a lean, structured set of bullets that assumes Claude's competence and avoids explaining background concepts Claude already knows, with every section earning its place.	3 / 3
Actionability	Concrete procedures and quoted declarations (e.g. '匪台小子敢行举乱', '不过六步七步') are present, but several steps stay abstract ('Maintain discipline', 'Restore proper governance', 'Arrange allied forces properly'), leaving gaps in executable detail.	2 / 3
Workflow Clarity	The phases are clearly sequenced (Pre-Campaign → Alliance → Declaration → Battle → Post-Victory) and a Validation section exists, but there are no inter-step validation checkpoints or feedback loops for a destructive operation like regime change, capping clarity at 2.	2 / 3
Progressive Disclosure	It is a single cohesive file with well-organized sections and no nested or external references, which is appropriate given no bundle files exist and the content needs no split.	3 / 3
	Total	10 / 12 Passed

Description

85%

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 with explicit what/when structure, concrete action coverage, and a clearly distinct niche. Its main weakness is trigger breadth — a single narrow phrase rather than several natural keyword variations.

Suggestions

Add a few natural trigger variations users might say, e.g. 'overthrowing a tyrant', 'justified war', or 'regime change against a tyrannical ruler', to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'just-cause verification, alliance building, troop declaration, combat rules of engagement, and post-victory administration' — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It explicitly answers both 'what' ('Covers just-cause verification, alliance building...') and 'when' ('Use when planning a righteous military campaign...'), satisfying the both-answered anchor.	3 / 3
Trigger Term Quality	It offers a single trigger phrase ('planning a righteous military campaign against a tyrannical ruler') with little variation, so it has relevant keywords but misses common variations a user might naturally say.	2 / 3
Distinctiveness Conflict Risk	The niche framing ('righteous military campaign', 'Tang and Wu Wang's campaigns') gives it a clear, distinct trigger unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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_015/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.