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.

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.

The body is a concise, well-sequenced protocol with explicit validation, appropriate for an instruction-only skill. Its main weakness is actionability: several regional-tour steps defer to 'same protocol as eastern tour' or say 'perform regional rituals' without the concrete detail shown in the eastern tour.

Suggestions

Replace the repeated 'Perform regional rituals' with the specific ritual(s) for each direction, or explicitly enumerate which eastern-tour sub-steps apply so the southern, western, and northern tours are self-contained.

Spell out the southern, western, and northern tours' standardization and review checklist rather than relying solely on 'Follow same protocol as eastern tour', which leaves key details implicit.

Tighten the redundant opening line ('A five-year cycle of systematic inspection tours covering the four cardinal directions of the realm.'), which restates the description.

DimensionReasoningScore

Conciseness

Lean bullet-pointed content with no padded explanations of concepts Claude already knows; the opening line is mildly redundant with the description but every token largely earns its place.

3 / 3

Actionability

Strong concrete specifics ('five jade tablets (五瑞)', 'fire ritual (祡)', the numbered gift list) coexist with vague steps like 'Perform regional rituals' (repeated three times) and 'Follow same protocol as eastern tour' without restatement.

2 / 3

Workflow Clarity

A clear sequence from Preparation through the four tours to Return and Audience, plus a dedicated Validation section verifying standards, jade tablets, and documentation; the operation is not destructive so no forced cap applies.

3 / 3

Progressive Disclosure

Single-purpose, well-organized into clear sections (Overview, Steps, Cycle Schedule, Expected Outcomes, Validation) with no need for external references, satisfying the simple-skill allowance for well-organized sections.

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.

The description is well-crafted: it pairs an explicit 'Use when' trigger with a concrete inventory of what the skill structures, uses third-person voice, and occupies a distinct niche. It is concise without sacrificing specificity.

DimensionReasoningScore

Specificity

Lists multiple concrete elements — 'five-year inspection cycle', 'four cardinal directions', 'ritual obligations', 'measurement standardization', 'audience protocols' — rather than vague abstractions.

3 / 3

Completeness

Explicit 'Use when...' clause answers when, and 'Structures a five-year inspection cycle...' answers what, matching the score-3 anchor for both.

3 / 3

Trigger Term Quality

Provides two natural trigger phrases ('planning a royal inspection tour', 'standardizing governance across regions') that a user in this domain would plausibly say, exceeding the single-phrase score-2 anchor.

3 / 3

Distinctiveness Conflict Risk

A highly niche domain with distinct triggers unlikely to overlap with other skills, matching the score-3 'clear niche' anchor.

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.