CtrlK
BlogDocsLog inGet started
Tessl Logo

five-zone-tribute-system

Use when managing tribute obligations or enforcing compliance across distance-based zones. Structures five concentric zones (五服制度) from daily offerings to lifetime homage, with escalation protocols for non-compliance.

70

Quality

88%

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.

A concise, well-structured reference skill that presents concrete decision/mapping tables and a clear escalation workflow without padding. The only notable gap is the absence of fully executable examples or an explicit error-recovery feedback loop, which is acceptable for an instruction/policy skill but keeps actionability and workflow clarity just below full marks.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding; it assumes Claude's competence and never over-explains concepts Claude already knows, with every line earning its place.

5 / 5

Actionability

Provides concrete, specific lookup tables (zone→obligation, violation→cultivation response, failed-cultivation→enforcement) that are actionable for an instruction/policy skill, though it stops short of executable code or commands.

4 / 5

Workflow Clarity

The escalation sequence is clearly laid out in two numbered/staged ladders (cultivation steps, then enforcement per zone), with checkpoints mostly explicit; it lacks an explicit validate→fix→retry feedback loop, though the policy nature does not demand one.

4 / 5

Progressive Disclosure

A simple, well-organized skill under 50 lines with no need for external references; clear section headers (Overview, Five Zones, Escalation Protocol, Expected Outcomes, Validation) provide easy navigation.

5 / 5

Total

18

/

20

Passed

Description

85%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 clear, concrete, and well-triggered description that explicitly covers both what the skill does and when to use it, occupying a distinct niche. The main weakness is trigger term quality, where the natural-language phrasing leans toward specialized historical vocabulary rather than everyday user terms.

Suggestions

Add more common synonyms a user might naturally say, e.g. 'compliance zones', 'tributary relations', or 'distance-based governance', to broaden natural trigger coverage.

Consider including an explicit file-type or artifact cue if this skill operates on specific outputs, to further sharpen trigger distinctiveness.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete capabilities ('Structures five concentric zones', 'escalation protocols for non-compliance'), covering the full scope from daily offerings to lifetime homage.

5 / 5

Completeness

Explicitly answers both 'what' (structures five concentric zones with escalation protocols) and 'when' ('Use when managing tribute obligations or enforcing compliance across distance-based zones').

5 / 5

Trigger Term Quality

Includes relevant keywords ('tribute obligations', 'enforcing compliance', 'distance-based zones') but they are specialized/historical jargon and lack common synonyms a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

The 五服制度 / distance-based tribute niche is highly specific with distinct triggers and minimal overlap risk 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.

Validation — 16 / 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.