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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 an efficient, well-organized instruction-only skill with a clear sequenced workflow and validation checkpoints. The main gaps are soft, non-executable phrasing in a few steps and the absence of an explicit validation failure-recovery loop.

Dimension	Reasoning	Score
Conciseness	Lean bullet-based content with no padding and no over-explanation of concepts Claude already knows; every line earns its place. Not below 5 because there is no discernible waste or over-explanation.	5 / 5
Actionability	Concrete, specific procedural guidance (named positions, named conduct) for an instruction-only skill; absence of code is not penalized. Not a 5 because some steps are soft ('Display appropriate humility', 'offer guidance when appropriate') rather than fully unambiguous.	4 / 5
Workflow Clarity	A clearly sequenced four-phase process with an explicit Validation section providing checkpoints. Not a 5 because the validation lacks an error-recovery feedback loop (no 'if validation fails, do X') that the top anchor expects.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, no external references needed, with well-organized sections (Overview, Steps, Decision Points, Expected Outcomes, Validation); the simple-skill exception applies. Not below 5 because structure is clear and no nested references exist.	5 / 5
	Total	18 / 20 Passed

Description

80%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 is well-structured, explicit about both purpose and trigger conditions, and occupies a distinct niche. Its main weakness is limited keyword/synonym variation in the trigger, relying on a single natural phrase.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete phases ('south-facing authority during regency, formal return of power at maturity, and north-facing minister position post-transition'), with only minor coverage gaps. Not a 5 because the actions are phase labels rather than a comprehensive enumeration of concrete operations.	4 / 5
Completeness	Explicitly answers both what (the three transition phases following Zhou Gong's model) and when ('Use when transitioning power from a regent to a young ruler coming of age') with a concrete trigger phrase. Not below 5 because both elements are present and explicit.	5 / 5
Trigger Term Quality	One solid natural trigger phrase ('Use when transitioning power from a regent to a young ruler coming of age') but no synonyms or common variations. Not a 4 because the anchor expects good keyword coverage with only a few missing; here there is essentially a single trigger clause.	3 / 5
Distinctiveness Conflict Risk	A clear narrow niche (regent-to-ruler power transition) with distinct triggers and minimal overlap risk with other skills. No neighboring anchor fits better given how specific the domain is.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: kg/ontology/ontology-v1/skus/procedural/skill_076/SKILL.md
Commit: 6b836e3

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.