CtrlK
BlogDocsLog inGet started
Tessl Logo

imperial-inspection-tour

Use when planning an imperial inspection tour (巡游) to demonstrate authority and inspect territories. Covers route planning, Feng and Shan sacrifices at Mount Tai, stele erection, local scholar consultation, and governance issue resolution.

68

Quality

81%

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

71%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 content is well-structured and concise with a clear sequenced workflow and validation section, but the guidance is more descriptive than executable, lacking concrete instructions or examples for how to perform each step.

Suggestions

Convert descriptive steps into executable guidance — e.g. specify how to select a route (criteria/radius), what a stele inscription should contain as a template, or what concrete artifacts to produce.

Add an explicit validation feedback loop (check -> fix -> re-check) for the destructive/batch-adjacent steps such as issuing amnesties or erecting steles.

Trim the Overview line that restates the frontmatter description to avoid redundant token use.

DimensionReasoningScore

Conciseness

The body is lean and mostly free of padding, assuming Claude's knowledge of imperial ritual; the Overview line slightly restates the frontmatter, a minor over-explanation that could be trimmed.

4 / 5

Actionability

The steps name concrete sub-tasks (route locations, sacrifice sites, stele inscriptions) but read as descriptive guidance rather than executable instructions, and offer no concrete artifacts or commands.

3 / 5

Workflow Clarity

The six steps form a clear, ordered sequence and the closing Validation section provides verification checkpoints, though the validation is confirmatory rather than an explicit error-recovery feedback loop.

4 / 5

Progressive Disclosure

This compact, single-purpose skill is well-organized into Overview, Steps, Expected Outcomes, and Validation sections with no need for external reference files, fitting the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

92%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 specific, well-triggered, and clearly distinguishes this niche skill from others, with concrete capabilities and an explicit 'Use when' clause. Minor expansion of trigger synonyms would make it perfect.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — route planning, Feng and Shan sacrifices, stele erection, local scholar consultation, and governance issue resolution — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what the skill does (covers route planning, sacrifices, steles, scholar consultation, governance) and when to use it via the clear 'Use when planning an imperial inspection tour' trigger clause.

5 / 5

Trigger Term Quality

Includes natural trigger phrases like 'imperial inspection tour' and the parenthetical '巡游', with solid coverage of synonyms, though a few natural variations (e.g. '巡狩', 'inspection progress') are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — imperial inspection tours with Feng/Shan rites at Mount Tai — making it unlikely to be triggered by any other skill.

5 / 5

Total

19

/

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.