CtrlK
BlogDocsLog inGet started
Tessl Logo

five-punishments-judicial-procedure

Use when adjudicating criminal cases or determining punishments under the five-tier system. Applies graduated verification from 五刑 to 五罚 to 五过, with doubt-based amnesty protocols and fine schedules for 3,000 categorized crimes.

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-organized procedural skill with a clear graduated workflow and explicit validation checkpoints; its main gap is actionability, since guidance is conceptual rather than executable.

Suggestions

Add concrete procedural mechanics or worked examples (e.g., how to evaluate each of the five testimony types, or a sample amnesty decision) so officials can act rather than just describe.

Make the fine-schedule units explicit (define '率') and show how contested-fine escalation to 五过 is actually carried out.

DimensionReasoningScore

Conciseness

The body is lean and well-structured: short labeled sections, a compact fine-schedule table, and lists without padding or explanation of concepts Claude already knows.

3 / 3

Actionability

It gives concrete decision branches and a specific fine schedule, but offers no executable commands, code, or precise procedural mechanics an official could follow; it describes rather than fully instructs.

2 / 3

Workflow Clarity

The graduated process (五刑 → 五罚 → 五过) is clearly sequenced and the Validation section provides explicit checkpoints verifying party presence, graduated order, doubt-amnesty, and fine-rate matching.

3 / 3

Progressive Disclosure

As a short, single-purpose skill (~70 lines) with no external references needed, the well-organized sections satisfy the simple-skill allowance for a top progressive-disclosure score.

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, specific description with an explicit 'Use when' trigger and clear niche; its main weakness is jargon-heavy trigger terms that users would seldom say verbatim.

Suggestions

Soften the 五刑/五罚/五过 jargon with plain-language equivalents users are more likely to voice (e.g., 'punishment, fine, mitigation tiers').

Add common natural phrasings such as 'sentencing', 'penalty determination', or 'criminal punishment' alongside the technical terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'adjudicating criminal cases', 'determining punishments', 'graduated verification from 五刑 to 五罚 to 五过', 'doubt-based amnesty protocols', and 'fine schedules', matching the highest anchor.

3 / 3

Completeness

Explicitly answers both what (graduated verification, amnesty protocols, fine schedules for 3,000 crimes) and when ('Use when adjudicating criminal cases or determining punishments under the five-tier system').

3 / 3

Trigger Term Quality

Includes relevant domain terms ('criminal cases', 'punishments', 'fines', 'amnesty') but relies on technical five-tier-system jargon (五刑/五罚/五过) that an ordinary user would rarely voice, missing common natural variations.

2 / 3

Distinctiveness Conflict Risk

The narrow five-tier punishment niche with domain-specific triggers makes it clearly distinguishable and unlikely to fire for unrelated skills.

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.