CtrlK
BlogDocsLog inGet started
Tessl Logo

regent-power-transition-protocol

Use when transitioning power from a regent to a young ruler coming of age. Follows Zhou Gong's model: south-facing authority during regency, formal return of power at maturity, and north-facing minister position post-transition.

72

Quality

87%

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 compact, well-structured protocol skill with a clear phased workflow and validation section. Its main weakness is actionability, where several steps remain abstract rather than specifying concrete, verifiable criteria.

Suggestions

Tighten actionability by replacing vague checks with concrete criteria, e.g. specify what 'can handle administrative duties' means (age threshold, completed mentorship tasks, or a sample decision the ruler must make unaided).

Make the transition ceremony steps more concrete and verifiable — name the specific acts that constitute 'formally return governing authority' (e.g. a written edict, public court proclamation) so the Validation section has explicit items to check.

Add a brief note on how to detect/handle a ruler who is not yet ready, since 'Assessing Readiness' currently gives no concrete signal for deferring the transition.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — short labeled phases with no padding explaining concepts Claude already knows, and every section earns its place.

3 / 3

Actionability

Guidance is concrete in places ('regent moves to the north-facing position', 'ruler takes the throne') but several steps stay abstract ('Confirm the ruler can handle administrative duties', 'Display appropriate humility'), so it lands at 'some concrete guidance but incomplete' rather than fully actionable.

2 / 3

Workflow Clarity

The four phases (During Regency → Assessing Readiness → Transition Ceremony → Post-Transition Conduct) are clearly sequenced, and a dedicated Validation section provides explicit checkpoints for verifying each phase.

3 / 3

Progressive Disclosure

This is a simple, under-50-line skill with no need for external references, and its sections (Overview, Steps, Decision Points, Expected Outcomes, Validation) are well-organized, satisfying the simple-skills allowance for a top score.

3 / 3

Total

11

/

12

Passed

Description

90%

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-constructed description with an explicit 'Use when' trigger, clear what/when coverage, and a distinct niche. The only soft spot is specificity, where the actions are ceremonial phases rather than a tight enumerated action list.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('south-facing authority during regency, formal return of power at maturity, and north-facing minister position post-transition'), but these are ceremonial/narrative beats rather than a comprehensive list of distinct operations, so it sits at the 'names domain and some actions' anchor rather than the multi-action level 3.

2 / 3

Completeness

It explicitly answers both what ('Follows Zhou Gong's model: south-facing authority... formal return of power... north-facing minister position') and when ('Use when transitioning power from a regent to a young ruler coming of age'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

'Use when transitioning power from a regent to a young ruler coming of age' uses the natural phrasing a user would say in this niche, with good coverage of the domain's terms (regent, transitioning power, young ruler coming of age).

3 / 3

Distinctiveness Conflict Risk

The regent-to-ruler power transition niche is highly specific with distinct triggers, making it unlikely to fire for an unrelated skill.

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.