CtrlK
BlogDocsLog inGet started
Tessl Logo

military-organization-three-armies

Use when organizing or restructuring military forces into a command hierarchy. Covers the three-army system (三军) with Central, Upper, and Lower armies, staff positions (御戎, 右), communication protocols, and scaling decisions for two-army or three-column (三行) configurations.

70

Quality

85%

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

85%

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

A concise, well-structured instruction skill with clear sequencing and an explicit verification section. Its main weakness is actionability: several implementation steps give direction without concrete detail.

Suggestions

Make vague implementation steps concrete — e.g. specify what "communication protocols" entails (signal flags, runner relays, watch schedule) rather than leaving the step abstract.

Add an explicit error-recovery feedback loop to the Verification section (e.g. "If a check fails, return to the relevant Implementation Step and re-verify") to close the gap between checkpoints and remediation.

Tighten the "Expected Outcome" line or fold it into Verification, since it largely restates the goal already implied by the structure.

DimensionReasoningScore

Conciseness

The body is lean — short bullet points and brief role descriptions with no padding or explanation of concepts Claude already knows, e.g. "**Commander**: Most experienced general (将中军)" and "**Chariot Driver** (御戎): Drives commander's chariot".

3 / 3

Actionability

Concrete structural guidance (named armies, 御戎/右 staff roles, "If forces are insufficient, reduce to two armies") is mixed with abstract steps like "Establish communication protocols between armies" and "Define rules of engagement and coordination" that lack specifics.

2 / 3

Workflow Clarity

A clear 7-step "Implementation Steps" sequence is paired with an explicit "Verification" section supplying concrete checkpoints (merit-based appointment, commander+deputy assigned, comms tested before deployment).

3 / 3

Progressive Disclosure

At ~44 lines with no external references needed, the well-organized sections (Command Structure subsections, Staff Positions, Decision Points, Verification) satisfy the simple-skill threshold for progressive disclosure.

3 / 3

Total

11

/

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, specific description with an explicit trigger and a clearly distinctive niche. The only gap is moderate coverage of natural trigger-term variations.

Suggestions

Broaden the trigger clause to capture more natural user phrasings, e.g. "Use when organizing or restructuring military forces into a command hierarchy, dividing troops into armies, or setting up a three-army (三军) command structure."

Consider adding a couple of plain-language synonyms ("army command structure", "troop deployment hierarchy") alongside the specialized terms to improve natural-term coverage.

DimensionReasoningScore

Specificity

It lists multiple concrete capabilities — "three-army system (三军) with Central, Upper, and Lower armies, staff positions (御戎, 右), communication protocols, and scaling decisions for two-army or three-column (三行) configurations" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

It explicitly answers both what ("Covers the three-army system...") and when ("Use when organizing or restructuring military forces into a command hierarchy") with an explicit trigger clause.

3 / 3

Trigger Term Quality

The single "Use when organizing or restructuring military forces into a command hierarchy" trigger is natural, but the description relies on one main phrasing and omits common variations a user might say (e.g. "set up an army command structure", "divide troops into armies").

2 / 3

Distinctiveness Conflict Risk

The niche domain and distinctive terms (三军, 御戎, 右, 三行, Central/Upper/Lower armies) give it a clear niche that is very unlikely to trigger for an unrelated skill.

3 / 3

Total

11

/

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.