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

80%

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

Fix and improve this skill with Tessl

tessl review fix ./kg/ontology/ontology-v1/skus/procedural/skill_068/SKILL.md

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 concise, well-organized instruction-only skill with a clear sequenced workflow and explicit validation. The weakest dimension is actionability, where steps describe intent more than they specify exactly what to produce.

Suggestions

Make each step produce a concrete artifact, e.g. 'Document the chain as a written, signed succession order listing each holder and their successor'.

Specify the refusal fallback concretely, e.g. 'on persistent refusal, revert to primogeniture and record the deviation in the order'.

Add a short worked mini-example inside the Steps (beyond the Example Application) so the binding-command mechanism is unambiguous.

Dimension	Reasoning	Score
Conciseness	Lean bullet steps with no padding and no exposition of concepts Claude already knows (e.g. no 'what is succession' preamble); every line earns its place. Not a 2 because there is no unnecessary explanation to trim.	3 / 3
Actionability	Steps are concrete in shape ("Create a chain of succession through brothers", "Make the protocol a binding command") but remain descriptive rather than precisely executable, omitting key details like what form the binding command takes or how to document it. Not a 1 because genuine guidance is given; not a 3 because nothing is copy-paste ready or fully specified.	2 / 3
Workflow Clarity	Clear sequence (Designate → Establish Sequence → Build Safeguards → Handle Refusal) supported by an Example Application, Decision Points, and an explicit Validation checklist with verification steps. Not a 2 because validation checkpoints and the refusal feedback path are explicitly present.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references, organized into well-labeled sections (Overview, Steps, Example, Decision Points, Expected Outcomes, Validation); per the simple-skills note this is sufficient for a 3. Not a 2 because structure is clean and self-contained.	3 / 3
	Total	11 / 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.

A clear, well-triggered description with explicit what/when guidance and strong distinctiveness. Its main weakness is moderate specificity, where the named actions are somewhat abstract rather than crisply concrete.

Suggestions

Sharpen the actions into more concrete verbs, e.g. 'design the brother-to-brother chain, document each handoff as a binding command, and define the refusal fallback'.

Add a couple of natural trigger variations a user might actually say, such as 'succession planning', 'leadership handoff', or 'designating an heir'.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("designing a multi-step succession sequence to transfer leadership to a designated heir", "safeguards for refusal") but they remain fairly abstract compared to the highly concrete anchor-3 example. Not a 3 because the actions lack the specificity of extract/fill/merge; not a 1 because multiple real actions are named.	2 / 3
Completeness	Explicitly answers both 'when' ("Use when designing a multi-step succession sequence...") and 'what' (transfers leadership to a designated heir via a chain with safeguards). Not a 2 because the 'Use when' trigger and the capability statement are both explicit.	3 / 3
Trigger Term Quality	Includes relevant natural terms ("succession sequence", "transfer leadership", "designated heir", "refusal") a user might say, but coverage of common variations is limited for this niche scenario. Not a 1 because the keywords are natural rather than jargon; not a 3 because variations are thin.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive niche grounded in King Shoumeng of Wu's brother-to-brother chain with refusal safeguards; triggers ("succession sequence", "designated heir") are unlikely to fire for unrelated skills. Not a 2 because the scope is sharply bounded rather than broadly overlapping.	3 / 3
	Total	10 / 12 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: 79c272f

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