CtrlK
BlogDocsLog inGet started
Tessl Logo

nine-provinces-administration

Use when establishing regional administrative divisions or designing taxation and tribute systems. Divides territory into nine provinces (州) with soil classification, graduated tax rates, tribute specifications, and water-route transport planning.

75

Quality

92%

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-only skill with a clear sequenced workflow and an explicit validation checklist. Its main gap is actionability: guidance names categories (tax rates, tribute items) without supplying the concrete per-province values that would make it directly usable.

Suggestions

Make tax and tribute steps actionable by including a concrete per-province table or inline list (e.g., which province maps to which soil rank, tax rate, and tribute items) rather than "Assign tax rates based on land productivity."

Replace "List specific tribute items per province (silk, salt, metals, timber, etc.)" with an actual per-province tribute mapping so Claude can produce the output directly.

Tighten the Validation section into a verify→fix→retry feedback loop (e.g., "If a province lacks a documented tax rate, return to Step 3 before proceeding") to make the error-recovery path explicit.

DimensionReasoningScore

Conciseness

Lean, list-based body with no padding or explanations of concepts Claude already knows; every section (Overview, Steps, Decision Points, Validation) earns its place.

3 / 3

Actionability

Concrete enumerations exist (province names, soil types like 白壤/黑坟, ranking terms 上上/上中) but core instructions stay abstract — "Assign tax rates based on land productivity" and "Establish graduated payment schedules" lack the actual per-province rates and tribute lists that would make them executable.

2 / 3

Workflow Clarity

Five numbered steps give a clear sequence, and a dedicated Validation section provides explicit checkpoints ("Verify…", "Confirm…", "Check that…"), with Decision Points handling conditional cases.

3 / 3

Progressive Disclosure

Under ~50 lines, single-purpose, no external references needed, and well-organized into clearly labeled sections — meeting the simple-skill allowance for a top score.

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.

A strong description: third-person, concise, with an explicit "Use when" trigger and a concrete enumeration of capabilities. It cleanly answers what the skill does and when to invoke it, with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Divides territory into nine provinces (州) with soil classification, graduated tax rates, tribute specifications, and water-route transport planning" — matching the top anchor for several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (the nine-province division with soil/tax/tribute/transport components) and when ("Use when establishing regional administrative divisions or designing taxation and tribute systems").

3 / 3

Trigger Term Quality

The trigger phrase "Use when establishing regional administrative divisions or designing taxation and tribute systems" uses natural task-oriented language a user would plausibly say for this niche.

3 / 3

Distinctiveness Conflict Risk

The nine-provinces / tribute-system framing is a narrow, well-defined niche unlikely to collide with other skills; triggers are domain-specific and unambiguous.

3 / 3

Total

12

/

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.