CtrlK
BlogDocsLog inGet started
Tessl Logo

imperial-inspection-tour-protocol

Use when planning a royal inspection tour or standardizing governance across regions. Structures a five-year inspection cycle covering four cardinal directions with ritual obligations, measurement standardization, and audience protocols.

72

Quality

89%

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

86%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 lean, well-organized instruction-only protocol with concrete specifics and an explicit validation section. The main gap is the absence of an explicit retry loop when validation checks fail.

Suggestions

Add a brief feedback loop under Validation, e.g. 'If a region's weights/measurements are inconsistent, re-issue standards and re-verify before closing the tour.'

For the Southern/Western/Northern tours, instead of only 'Follow same protocol as eastern tour', note any direction-specific ritual or gift differences to avoid ambiguity.

DimensionReasoningScore

Conciseness

Lean, terse bullet structure with no padding or explanation of concepts Claude already knows; every token earns its place, e.g. 'Standardize: calendar, measurements, weights'.

5 / 5

Actionability

Concrete, specific guidance throughout (months, 'Dai Zong (Mount Tai)', 'fire ritual (祡)', 'five jade tablets (五瑞)') with minor gaps; no code but appropriately instruction-only.

4 / 5

Workflow Clarity

A clear 7-step sequence with an explicit Validation section, but lacking an explicit retry/feedback loop for failed validation checkpoints.

4 / 5

Progressive Disclosure

Self-contained skill with no bundle files; content is well-organized into Overview, Steps, Cycle Schedule, Expected Outcomes, and Validation sections with no nested references.

5 / 5

Total

18

/

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 third person, concise, and clearly states both what the skill does and when to invoke it. Trigger phrases are natural and the niche is distinctive with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete structural actions — 'Structures a five-year inspection cycle covering four cardinal directions with ritual obligations, measurement standardization, and audience protocols' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (structures a five-year inspection cycle...) and 'when' (Use when planning a royal inspection tour...) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'planning a royal inspection tour' and 'standardizing governance across regions' would plausibly be said by a user, but a few synonyms/common variations are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (imperial inspection tours) with distinct triggers; minimal realistic overlap with other skills.

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.