CtrlK
BlogDocsLog inGet started
Tessl Logo

qin-standardization-system

Use when implementing uniform standards across a newly unified empire. Covers weights and measures (衡石丈尺), writing system (书同文字), transportation (车同轨), Five Elements cosmology, and symbolic renaming of rivers and populace.

68

Quality

83%

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

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 well-structured, concise procedural skill with concrete numerical specifics and an explicit validation section. The main gaps are a few abstract directives that lack the concrete standard value, and the absence of feedback-loop checkpoints between batch steps.

Suggestions

Add the specific standard values to the abstract steps (e.g. state the unified axle width and the standard script name) so every step is directly executable.

Insert inter-step validation checkpoints or a validate->fix->retry loop for the batch/destructive operations (renaming rivers/populace, empire-wide standardization) rather than only an end-of-process Validation section.

Trim the redundancy between the Overview and Expected Outcomes sections to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (it does not over-explain Five Elements cosmology or the historical context), with only mild redundancy between the Overview and Expected Outcomes sections that could be trimmed.

4 / 5

Actionability

Most steps are concrete and specific (6-inch caps, 6-foot carriages, tenth-month calendar start, rename Yellow River to 'Virtue River'), but a few steps are high-level directives without the underlying spec ('Build roads to standard specifications', 'Unify all measuring instruments').

4 / 5

Workflow Clarity

Steps are clearly numbered 1-6 and an explicit Validation section with three checks is present, but there are no inter-step checkpoints or validate->fix->retry feedback loops for these empire-wide batch operations.

4 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained, and well-organized into clear sections (Overview, Steps, Expected Outcomes, Validation) with no need for external bundle files, meeting the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

87%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 description with an explicit 'Use when...' trigger, clear statement of what the skill covers, and a distinctive niche. The main weakness is that several listed items read as covered topics rather than concrete performed actions, and a few natural synonyms are missing.

DimensionReasoningScore

Specificity

Lists several specific concrete coverage areas (衡石丈尺, 书同文字, 车同轨, Five Elements cosmology, renaming of rivers and populace) with only minor gaps, though the verbs ('implementing', 'Covers') are somewhat generic rather than distinct concrete actions.

4 / 5

Completeness

Explicitly answers both 'what' (covers the listed standardization domains) and 'when' ('Use when implementing uniform standards across a newly unified empire') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes an explicit 'Use when implementing uniform standards across a newly unified empire' trigger plus domain keywords (weights and measures, writing system, Five Elements cosmology), though a few natural synonyms (e.g. 'Qin', 'standardization' as a noun) are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a highly specific historical niche (Qin-era empire standardization) with distinct triggers and minimal realistic overlap with other skills.

5 / 5

Total

18

/

20

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.