succession-transfer-protocol

Use when designing a multi-step succession sequence to transfer leadership to a designated heir. Models King Shoumeng of Wu's brother-to-brother chain (寿梦→诸樊→余祭→余眜→季札) with safeguards for refusal.

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

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 content is well-structured and concise for a simple instruction-only protocol skill, with clear sequencing and validation. Its weakest point is actionability: the step guidance remains abstract where concrete, executable specifics would help Claude actually apply the protocol.

Suggestions

Make each step bullet actionable by specifying how, not just what — e.g., replace 'Secure commitment from current leader' with a concrete mechanism like 'Record the leader's signed/witnessed endorsement of the heir in the succession charter'.

Tighten overlap between 'Decision Points' and 'Expected Outcomes' by merging redundant refusal-handling guidance into one section, freeing tokens for more concrete execution detail.

Add a short reusable template (heir → chain order → fallback) that Claude can fill in, turning the abstract steps into a copy-paste-ready artifact.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the 'Expected Outcomes' and 'Decision Points' sections overlap somewhat and could be trimmed, placing it at score 4 rather than the fully lean score 5.	4 / 5
Actionability	Guidance is concrete in the worked example (named chain Shoumeng→Zhufan→Yuji→Yumei→Ji Zha) but the step bullets stay abstract ('Secure commitment', 'Make the protocol a binding command') without executable specifics, matching the score-3 anchor of incomplete concrete guidance.	3 / 5
Workflow Clarity	A clear four-step sequence (Designate→Establish→Safeguard→Refusal) plus an explicit Validation section and refusal fallback gives most checkpoints; it is not score 5 because the validation checks are generic confirmations rather than executable, verifiable commands.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references, the skill is well-organized into clearly headed sections (Overview, Steps, Example, Decision Points, Outcomes, Validation), meeting the simple-skill exception for score 5.	5 / 5
	Total	16 / 20 Passed

Description

87%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 strong: it explicitly states both what the skill does and when to use it, with a distinctive niche and natural trigger terms. Specificity is good but slightly below fully comprehensive, as the actions are conceptual rather than exhaustive.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'designing a multi-step succession sequence', 'transfer leadership to a designated heir', 'Models...brother-to-brother chain', 'safeguards for refusal' — with only minor coverage gaps, matching the score-4 anchor rather than the more comprehensive score-5.	4 / 5
Completeness	Explicit 'Use when...' clause supplies the when, and 'Models King Shoumeng of Wu's brother-to-brother chain...with safeguards for refusal' states the what concretely, satisfying the score-5 anchor for both.	5 / 5
Trigger Term Quality	Natural phrases a user would say ('succession sequence', 'transfer leadership', 'designated heir', 'refusal') give good keyword coverage, but a few common synonyms are missing, so it sits at score 4 rather than the fully comprehensive score 5.	4 / 5
Distinctiveness Conflict Risk	The highly specific niche (succession-transfer protocol, named historical chain, refusal safeguards) gives clear distinct triggers with minimal conflict risk against other skills.	5 / 5
	Total	18 / 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_068/SKILL.md
Commit: 6b836e3

Reviewed: 13 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.