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.

Quality

82%

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

78%Weight 40%Scale 1-5

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, single-purpose skill body with a clear workflow and verification checklist. The main gaps are mild redundancy with the description and the absence of an explicit validate-and-fix feedback loop in the verification section.

Suggestions

Tie verification directly into the implementation steps as interleaved checkpoints (e.g., after step 6, verify communication protocols before defining rules of engagement) and add a brief 'if a check fails, revise and re-verify' loop to lift workflow_clarity.

Tighten the opening line and 'Expected Outcome' section to remove overlap with the frontmatter description, improving conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with concrete role definitions and steps, but the opening restatement ('A command structure for organizing military forces...') and the 'Expected Outcome' section slightly echo the description and could be trimmed.	4 / 5
Actionability	Implementation Steps and Decision Points give concrete, specific organizational guidance (divide into three equal groups, appoint by merit, scale to two armies or 三行), appropriate for an instruction-only skill, though some steps like 'Appoint commanders based on merit and experience' remain high-level without selection criteria.	4 / 5
Workflow Clarity	A clear 7-step sequence is followed by explicit Verification checks (merit-based appointment, commander+deputy per army, tested communication protocols), but verification is post-hoc rather than interleaved and lacks an error-recovery feedback loop, so it stops short of a 5.	4 / 5
Progressive Disclosure	No bundle files exist and the body is under 50 lines with a single organizational purpose, so the well-organized section structure (Overview, Command Structure, Staff Positions, Implementation Steps, Decision Points, Verification) fully satisfies the simple-skill exception for progressive disclosure.	5 / 5
	Total	17 / 20 Passed

Description

78%Weight 40%Scale 1-5

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 'Use when' trigger and a well-scoped, distinctive niche. It falls just short of top marks because the trigger coverage and action-verb variety are slightly limited rather than truly comprehensive.

Suggestions

Add one or two more natural trigger variants to the 'Use when' clause (e.g., '...or when setting up an army command structure / battle formation') to broaden trigger_term_quality and completeness.

Lead with one or two additional concrete verbs (e.g., 'divide, appoint, and coordinate') so the action list reads as comprehensive rather than a single organize/restructure action.

Dimension	Reasoning	Score
Specificity	Names the domain action ('organizing or restructuring military forces into a command hierarchy') and several concrete elements (Central/Upper/Lower armies, 御戎/右 staff positions, communication protocols, two-army and 三行 scaling), but the active verbs are limited to organize/restructure, leaving a minor coverage gap versus a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers both what (the command-hierarchy organization and its covered components) and when ('Use when organizing or restructuring military forces into a command hierarchy'), but the 'when' offers essentially one trigger clause rather than the multiple concrete trigger variants that would reach a 5.	4 / 5
Trigger Term Quality	Includes natural niche phrases a user would say ('organizing or restructuring military forces', 'command hierarchy', 'three-army system') plus distinctive terms (三军, 御戎, 右, 三行), but a few natural variations like 'battle formation' or 'army command structure' are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, highly specific niche (classical Chinese three-army organization) with distinctive triggers (三军, 御戎, 右, 三行) that make conflict with other skills unlikely.	5 / 5
	Total	17 / 20 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_093/SKILL.md
Commit: 6b836e3

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