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.

57

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./kg/ontology/ontology-v1/skus/procedural/skill_034/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 compact, well-structured procedure with explicit validation criteria and clean sectioning. Weaknesses are minor redundancy in restating the rationale and actionability gaps around how the decree is concretely issued.

Suggestions

Tighten the redundancy between Overview and step 1 so the abolition rationale is stated once.

Add concrete detail on the decree itself (form, content, where recorded) to make step 2 actionable rather than a high-level instruction.

Convert the trailing Validation list into inline checkpoints (e.g., 'after issuing the decree, verify…') to create an explicit feedback loop.

DimensionReasoningScore

Conciseness

The body is short and sectioned, but the abolition rationale is restated across the Overview, step 1, and step 2, and the Historical Context section adds explanation Claude largely already knows about 谥法 and Qin Shi Huang.

3 / 5

Actionability

The steps give specific domain guidance (name the first ruler 始皇帝, number successors sequentially) but lack concrete detail on how the decree is actually issued or recorded, leaving key execution detail unspecified.

3 / 5

Workflow Clarity

Steps 1–4 are clearly sequenced and a Validation section provides three explicit verify/confirm/check criteria; it falls short of 5 only because there is no validate-then-fix feedback loop integrated into the sequence.

4 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with no external bundle files, organized into clearly labeled sections (Overview, Steps, Expected Outcomes, Historical Context, Validation) — well-organized and self-contained.

5 / 5

Total

15

/

20

Passed

Description

66%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 clearly states what the skill does and when to use it, and is highly distinct within a niche historical-governance domain. Its main weakness is trigger-term naturalness and only moderate action specificity.

Suggestions

Add more natural-language trigger phrasing (e.g., 'when renaming rulers', 'when reforming dynastic titling') so non-specialist users can surface the skill.

List one or two additional concrete actions (e.g., 'drafts the abolition decree', 'defines the successor numbering scheme') to lift specificity beyond two actions.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions — 'abolishing the posthumous title system (谥法)' and 'Establishes sequential numbering from 始皇帝 onward' — but coverage is limited to these rather than comprehensive.

3 / 5

Completeness

Both 'what' (establishes sequential numbering as an alternative convention) and 'when' ('Use when abolishing the posthumous title system') are explicitly stated, though the trigger is narrow and somewhat intertwined with the what.

4 / 5

Trigger Term Quality

Relevant domain terms ('posthumous title system', '谥法', '始皇帝', 'sequential numbering') are present but they are specialized historical jargon lacking natural user synonyms or common variations.

3 / 5

Distinctiveness Conflict Risk

It occupies a clearly defined niche — abolishing the posthumous title (谥法) system — with distinct triggers and minimal realistic overlap with other skills.

5 / 5

Total

15

/

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.