CtrlK
BlogDocsLog inGet started
Tessl Logo

governance-transition-framework

Use when transitioning from conquest to stabilization or diagnosing dynastic failure. Applies the principle that 取与守不同术也 (taking and keeping power require different methods), shifting from military force (诈力) to benevolence and adaptability (顺权).

62

Quality

73%

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

Quality

Content

71%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.

The body is well-structured, concise, and includes validation checkpoints with clear sequencing. Its main weakness is actionability: the Application steps stay at a high level rather than giving concrete, discriminating guidance.

Suggestions

Replace vague Application steps like 'Adjust policies accordingly' with concrete decision criteria or example policy shifts tied to each phase's Prioritize/Focus/Approach axes.

Add one or two short worked examples (e.g., a conquest→stabilization transition scenario) showing how the framework changes specific recommendations, to make the guidance more executable.

Tighten the Overview to avoid restating the Core Principle, or merge them so each token earns its place.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the Overview restates the Core Principle, a minor redundancy that could be trimmed.

4 / 5

Actionability

The Decision Framework gives concrete per-phase axes (Prioritize/Focus/Approach), but the Application steps are high-level ('Adjust policies accordingly', 'Transition leadership approach') without specific executable guidance.

3 / 5

Workflow Clarity

A clear three-step sequence (assess → adjust → transition) is paired with an explicit Validation section containing verification checkpoints, with only minor gaps.

4 / 5

Progressive Disclosure

A simple, under-50-line single-purpose skill with well-organized section headers and no need for external bundle files, satisfying the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

75%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.

The description cleanly answers both 'what' and 'when' with a distinctive, low-conflict niche. Specificity and trigger-term coverage are adequate but could name more concrete operations and natural synonyms.

DimensionReasoningScore

Specificity

Names the domain and a few concrete actions ('transitioning from conquest to stabilization', 'diagnosing dynastic failure', 'shifting from military force to benevolence and adaptability'), but the actions are conceptual rather than operational, leaving coverage incomplete.

3 / 5

Completeness

An explicit 'Use when transitioning from conquest to stabilization or diagnosing dynastic failure' clause gives the trigger, and the rest clearly states what the skill does (applies the 取与守不同术也 principle, shifting 诈力 to 顺权).

5 / 5

Trigger Term Quality

Relevant niche keywords like 'conquest', 'stabilization', and 'dynastic failure' are present, but common variations or synonyms a user might naturally say are missing.

3 / 5

Distinctiveness Conflict Risk

The dynastic-governance-transition niche with classical-Chinese triggers is highly specific and unlikely to fire for unrelated skills.

5 / 5

Total

16

/

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.