CtrlK
BlogDocsLog inGet started
Tessl Logo

merit-based-title-evaluation

Use when evaluating officials for noble titles or ranking meritorious service. Applies the five-tier classification (勋劳功伐阅) to determine title rank, land grants, and hereditary privileges based on contribution type.

71

Quality

86%

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 well-organized, concise instruction-only skill with a clear workflow and explicit validation checks. The main weakness is the absence of a worked example and explicit error-recovery loops.

Suggestions

Add one fully worked example (a sample official, their service, the assigned tier, title rank, land grant, and hereditary terms) to make the end-to-end process copy-paste concrete.

Add an explicit feedback loop in the Validation section: if an assignment fails a check, re-classify the contribution and re-evaluate before recording the oath.

State how magnitude mapping drives reward proportionality (e.g., dynasty-saving service → highest rank + largest grant) so the reward-determination step is unambiguous.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every line earns its place and the skill assumes Claude's competence.

5 / 5

Actionability

Provides concrete, specific guidance — named tiers with definitions, magnitude criteria, and a service-type-to-tier decision map — but lacks a fully worked end-to-end example that would lift it to 5.

4 / 5

Workflow Clarity

A clear four-step sequence (classify, evaluate magnitude, determine reward, record oath) with a Decision Points map and a three-item Validation section; recovery/feedback loops are implicit rather than explicit, keeping it below 5.

4 / 5

Progressive Disclosure

A short single-purpose skill (under 50 lines, no bundle files) organized into clear Overview/Steps/Decision Points/Expected Outcomes/Validation sections, satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong, specific description with an explicit 'Use when' trigger and a clear statement of what the skill does. It is highly distinct and unlikely to be activated for the wrong skill.

DimensionReasoningScore

Specificity

Lists several concrete actions ('determine title rank, land grants, and hereditary privileges', 'ranking meritorious service') with only minor coverage gaps, falling just short of the fully comprehensive 5-anchor example.

4 / 5

Completeness

Explicitly answers both what ('Applies the five-tier classification (勋劳功伐阅) to determine title rank, land grants, and hereditary privileges') and when ('Use when evaluating officials for noble titles or ranking meritorious service') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when evaluating officials for noble titles or ranking meritorious service' clause supplies natural phrases a user would say, with good but not exhaustive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (noble-title evaluation via the five-tier 勋劳功伐阅 classification) 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.

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.