five-zones-governance

Use when establishing concentric administrative zones or assigning graduated obligations by distance from a capital. Structures five zones (五服) from 甸服 to 荒服, each with specific tribute and governance requirements.

Quality

81%

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.

The body is a tight, well-structured reference whose core zone table is concrete and complete, supported by sequenced steps and a validation section. The main gaps are mild padding in 'Expected Outcomes' and the absence of an explicit validation-failure feedback loop.

Suggestions

Trim or remove the 'Expected Outcomes' section, which restates the system's purpose already covered in 'Overview', to tighten conciseness toward the lean anchor.

Make 'Implementation Steps' more actionable by specifying how boundaries are measured/marked and what 'appropriate officials' means per zone.

Add a short feedback loop after the 'Validation' bullets (e.g., 'If a check fails, re-measure the offending boundary or re-notify the relevant leader, then re-validate') to reach the top workflow-clarity anchor.

Dimension	Reasoning	Score
Conciseness	The Zone Structure table is dense and earns its tokens, but the 'Expected Outcomes' bullets ('Organized territorial administration', 'Graduated obligations based on proximity', 'Clear governance hierarchy') and generic implementation steps restate the obvious — minor padding that keeps it just below the 'lean, every token earns its place' anchor.	4 / 5
Actionability	The zone table gives concrete, spec-like guidance (exact li ranges and tribute types per sub-zone), but the 'Implementation Steps' are high-level ('Assign appropriate officials', 'Monitor compliance and adjust as needed') with no specifics on how to measure/mark zones, leaving minor gaps.	4 / 5
Workflow Clarity	A clear 5-step sequence is paired with an explicit 'Validation' section of three verification bullets, but there is no error-recovery feedback loop (what to do when a check fails), so it stops at 'clear sequence with most checkpoints' rather than the 'feedback loops for error recovery' anchor.	4 / 5
Progressive Disclosure	Under 50 lines with no external references needed, the body is well-organized into clearly headed sections (Overview, Zone Structure, Implementation Steps, Expected Outcomes, Validation), meeting the simple-skill exception for a top progressive-disclosure score.	5 / 5
	Total	17 / 20 Passed

Description

75%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.

The description is well-formed: third-person voice, explicit 'Use when' trigger, and a clear, distinctive niche. Its main weakness is moderate specificity and trigger-term naturalness, where the actions and keywords are somewhat formal rather than comprehensive and conversational.

Suggestions

Add one or two more concrete actions (e.g., 'defines tribute tiers per sub-zone and maps officials to each ring') to lift specificity toward the 'several specific actions' anchor.

Soften trigger phrasing toward terms a user would naturally type (e.g., 'five-zones / 五服 tribute system', 'graduated tribute by distance') and add synonyms so trigger-term coverage reaches 'good keyword coverage'.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('establishing concentric administrative zones', 'assigning graduated obligations by distance'), but does not enumerate several specific actions; it sits at the 'domain + 1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.	3 / 5
Completeness	Explicitly answers both 'what' ('Structures five zones (五服) from 甸服 to 荒服, each with specific tribute and governance requirements') and 'when' ('Use when establishing concentric administrative zones or assigning graduated obligations by distance from a capital') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes relevant domain terms ('五服', '甸服', '荒服', 'concentric administrative zones', 'tribute and governance requirements'), but the natural phrasing a user would say is formal/jargony and missing common variations, so it lands at 'some relevant keywords but missing variations' rather than 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	The 五服 concentric-tribute-zones niche is highly specific with distinct triggers, making accidental activation by unrelated skills unlikely; this matches the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	16 / 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_008/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.