CtrlK
BlogDocsLog inGet started
Tessl Logo

posthumous-title-abolition

Use when abolishing the posthumous title system (谥法) to prevent subjects from judging rulers. Establishes sequential numbering from 始皇帝 onward as an alternative naming convention. Abolished by Qin Shi Huang in 221 BCE.

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.

A clean, well-organized procedure with a clear step sequence and an explicit validation section. The only weakness is mild supplementary padding in the Historical Context and Expected Outcomes sections.

Suggestions

Trim or fold the Historical Context and Expected Outcomes sections into the steps where relevant to improve token efficiency.

Add a brief feedback loop in the Validation section (e.g., what to fix and re-check if a verification fails) to strengthen the recovery path.

DimensionReasoningScore

Conciseness

The core Steps are lean, but the "Historical Context" and "Expected Outcomes" sections add supplementary context beyond what is needed to execute the procedure and could be tightened.

2 / 3

Actionability

For an instruction-only policy skill the guidance is concrete and specific — named conventions (始皇帝, Second Emperor, Third Emperor) and explicit procedural steps rather than vague direction.

3 / 3

Workflow Clarity

Four steps are clearly sequenced and a dedicated "Validation" section provides explicit verification checks, so validation is present rather than implicit.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, and well-organized into clear sections (Overview, Steps, Expected Outcomes, Historical Context, Validation).

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.

A well-constructed description with an explicit Use-when trigger, concrete actions, and strong distinctiveness within a narrow niche. It uses third-person voice and avoids padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "abolishing the posthumous title system (谥法)" and "Establishes sequential numbering from 始皇帝 onward" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (abolish 谥法, establish sequential numbering) and when via the "Use when abolishing..." trigger clause.

3 / 3

Trigger Term Quality

Covers the natural vocabulary of its niche — "posthumous title system", "谥法", "始皇帝", "Qin Shi Huang" — terms a user working on this topic would actually say.

3 / 3

Distinctiveness Conflict Risk

A highly specific governance-reform niche with distinctive triggers (谥法, 始皇帝) that is very unlikely to fire for an unrelated skill.

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.