CtrlK
BlogDocsLog inGet started
Tessl Logo

govern-through-accessible-justice

Use when designing governance systems that ensure fair access to justice across all social levels. Covers territorial tours, open-air administration, and prompt dispute resolution following the model of rulers who personally judged cases under trees.

62

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_083/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized with a clear sequenced workflow and an explicit verification checklist, but its guidance stays at a principle level and carries light non-essential content. Making steps more concrete and trimming outcome padding would raise actionability and conciseness.

Suggestions

Convert principle-like bullets into specific actions with concrete detail (e.g., "Hold sessions at a fixed public spot weekly" instead of "Be physically present among the people").

Remove or compress the "Expected Outcomes" section, which restates motivation rather than instructing, to improve token efficiency.

Tie the Verification checklist directly back to the steps (e.g., note what to do if a check fails) so validation reads as a feedback loop rather than a standalone list.

DimensionReasoningScore

Conciseness

The body is mostly lean and free of concept-explaining fluff, but the "Expected Outcomes" section and abstract restatements like "Be physically present among the people" add tokens that could be trimmed without losing guidance.

2 / 3

Actionability

Concrete-enough directions appear ("Choose simple, public locations (e.g., under a tree)", "Resolve disputes promptly"), but most steps read as high-level principles rather than specific, executable guidance with key details.

2 / 3

Workflow Clarity

A clear four-step sequence (tour, establish venues, handle cases, ensure fairness) is paired with an explicit Verification checklist that confirms personal visits, venue accessibility, and prompt resolution.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, the content is organized into well-labeled sections (Overview, Steps, Expected Outcomes, Verification), satisfying the simple-skill allowance for progressive disclosure.

3 / 3

Total

10

/

12

Passed

Description

75%

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 has an explicit trigger and a clear, distinctive niche, but its action language leans abstract and several trigger terms are phrased more like historical description than natural user requests. Tightening the action list and using more common keywords would lift specificity and trigger-term quality.

Suggestions

Lead with concrete verbs the user would recognize (e.g., "Design governance procedures for in-person dispute resolution") rather than the abstract "designing governance systems that ensure fair access to justice".

Add natural trigger variations users would actually say (e.g., "fair justice system", "accessible courts", "public dispute resolution") alongside the historical phrasing.

Trim the illustrative clause ("following the model of rulers who personally judged cases under trees") to keep the description concise and trigger-focused.

DimensionReasoningScore

Specificity

Names the governance/justice domain plus several activities ("territorial tours, open-air administration, and prompt dispute resolution"), but the lead ("designing governance systems that ensure fair access to justice") is abstract and the actions read as thematic categories rather than a crisp concrete action list.

2 / 3

Completeness

An explicit "Use when designing governance systems..." trigger pairs with a "Covers..." clause, clearly answering both what the skill does and when to invoke it.

3 / 3

Trigger Term Quality

Some natural keywords appear ("governance", "justice", "dispute resolution"), but distinctive triggers like "territorial tours" and "rulers who personally judged cases under trees" are phrased in ways a user is unlikely to say verbatim, and common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The historical accessible-justice niche (personal territorial tours, under-tree administration) is highly specific with distinctive triggers, making conflict with other skills unlikely.

3 / 3

Total

10

/

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.