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.

70

Quality

85%

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 concise, well-structured decision framework with clear sequencing and explicit validation. The main weakness is actionability: the magnitude-evaluation and reward-determination steps are descriptive rather than concrete, lacking specific thresholds or output formats.

Suggestions

Replace the open magnitude questions with concrete decision criteria or a scoring rubric (e.g., crisis vs. peacetime thresholds) so rankings are reproducible.

Provide an example filled-in oath/title record or a template showing the expected output structure for step 4.

Add concrete guidance mapping each tier to a typical land-grant size or hereditary span so the reward step is actionable rather than a category list.

DimensionReasoningScore

Conciseness

Lean and efficient — every section (Overview, Steps, Decision Points, Expected Outcomes, Validation) earns its place with no padding or explanation of concepts Claude already knows, fitting the score-3 anchor.

3 / 3

Actionability

Decision Points give concrete tier-mapping rules, but the magnitude-evaluation step is only open questions ('Did the service save the dynasty?') and the reward step lists categories (title rank, land grant, hereditary privileges) without concrete values, leaving it at the 'some concrete guidance but incomplete' anchor.

2 / 3

Workflow Clarity

Four steps are clearly sequenced and an explicit Validation section provides a 3-point checklist verifying classification, oath recording, and proportionality — matching the 'clear sequence with explicit validation steps / checklists' anchor.

3 / 3

Progressive Disclosure

Under 50 lines, single-purpose, with well-organized labeled sections and no bundle files needed; per the rubric's simple-skills note this qualifies for a 3 without external file references.

3 / 3

Total

11

/

12

Passed

Description

85%

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 description that is specific, third-person, and clearly pairs an explicit 'Use when' trigger with a concrete statement of capability. Trigger-term coverage is the only soft spot, as the narrow domain leaves few synonym variations.

Suggestions

Broaden trigger terms slightly to surface more natural phrasings a user might say, e.g. 'awarding noble titles', 'hereditary rank', or 'granting land for service'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'determine title rank, land grants, and hereditary privileges' and 'ranking meritorious service' — rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both: the 'Use when evaluating officials for noble titles or ranking meritorious service' clause gives the trigger, and the rest states what it does (applies the five-tier classification to determine rank, land, and heredity).

3 / 3

Trigger Term Quality

Relevant natural phrases ('noble titles', 'meritorious service') are present, but coverage is narrow with limited common variations, so it sits at the 'some relevant keywords but missing variations' anchor rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The niche is highly distinct (noble-title evaluation via the 勋劳功伐阅 classification) with triggers unlikely to overlap with other skills, matching the clear-niche anchor.

3 / 3

Total

11

/

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.