CtrlK
BlogDocsLog inGet started
Tessl Logo

merit-based-reward-classification

Use when designing a tiered reward system for contributions or ranking officials by merit. Classifies service into four tiers: moral guidance (封邑 grants), administrative execution (卿位 titles), military labor, and routine service, allocating rewards systematically from highest to lowest.

57

Quality

72%

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_092/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.

A compact, well-organized classification framework with a clear workflow and validation section. It would benefit from trimming generic filler and making lower-tier rewards and the classification mechanism more concrete.

Suggestions

Remove generic filler lines ('ensures fair recognition', 'motivates continued loyalty') that restate the obvious.

Replace vague Tier 3/4 recognition ('appropriate honors', 'acknowledged') with concrete reward types matching the specificity of Tiers 1-2.

Add a compact classification table or worked example showing a contributor mapped to a tier and reward, to make the process directly executable.

DimensionReasoningScore

Conciseness

Mostly efficient structured content, but lines like 'This system ensures fair recognition by categorizing contributions into distinct tiers' and 'Fair distribution that motivates continued loyalty' are padding that could be trimmed.

3 / 5

Actionability

Tier criteria and a 5-step implementation process give concrete guidance, but Tier 3/4 recognition ('appropriate honors', 'acknowledged') stays vague and no classification template or table is provided.

3 / 5

Workflow Clarity

Implementation Steps are clearly sequenced and a dedicated Verification section provides explicit checkpoints ('before rewards are allocated', 'Validate that…', 'Check that…'); minor gaps versus a full validate-fix-retry loop.

4 / 5

Progressive Disclosure

A compact (<50 line) single-purpose skill with no need for external references and well-organized section headers (Overview, Tiers, Implementation, Verification); fits the simple-skill 5 anchor.

5 / 5

Total

15

/

20

Passed

Description

67%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 well-structured description that clearly states both what the skill does and when to use it, with concrete tier-based actions and strong distinctiveness. Trigger-term coverage is adequate but could include more natural phrasings and synonyms.

Suggestions

Broaden trigger terms with natural synonyms users might say, e.g. 'rewarding contributors', 'classifying merit', 'allocating rewards by contribution'.

Consider adding a concrete output artifact phrase (e.g. 'produces a tiered reward allocation') to sharpen the 'what'.

DimensionReasoningScore

Specificity

Names several concrete actions ('Classifies service into four tiers', 'allocating rewards systematically from highest to lowest', 'ranking officials by merit') and enumerates the four tiers; minor coverage gaps keep it just below 5.

4 / 5

Completeness

Explicit 'Use when…' clause provides the trigger and the classification/allocation behavior states the what; both present with the 'when' solid but not maximally specific.

4 / 5

Trigger Term Quality

'designing a tiered reward system' and 'ranking officials by merit' are reasonably natural phrases, but coverage lacks common synonyms or variations a user might phrase differently.

3 / 5

Distinctiveness Conflict Risk

The classical merit-reward niche with distinctive tier terminology is clearly distinguishable; only minor overlap risk with adjacent ranking/reward skills.

4 / 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.

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.