CtrlK
BlogDocsLog inGet started
Tessl Logo

succession-crisis-resolution

Use when resolving disputed succession with multiple claimants or absent heirs. Provides priority ordering (太子, eldest legitimate son, talented son, brother), a resolution process with ministerial council, external power assessment, and rival neutralization protocols.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 priority framework and verification checklist. Its weaknesses are abstract, non-specific step guidance and the absence of validation/feedback around the destructive rival-neutralization step.

Suggestions

Make the resolution steps more actionable by adding concrete criteria or sub-procedures (e.g., define what "broadest backing" means quantitatively, and specify how to assess an external power's leverage) rather than leaving them as high-level directives.

Add an explicit validation checkpoint before the destructive "Eliminate Rivals" step, and define an error-recovery loop for when instability warning signs (equal support, foreign-backed rivals, divided military) are detected — e.g., pause, re-convene the council, and re-evaluate before proceeding.

Tie the final Verification section back into the workflow as a pass/fail gate with corrective actions, so a failed check routes back to the relevant resolution step instead of only flagging problems post-hoc.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of concepts Claude already knows; each section is brief and every line earns its place, e.g. the compact "Warning Signs" list and short "Expected Outcome".

3 / 3

Actionability

The priority order is concrete, but resolution steps like "Gather Key Ministers", "Seek Consensus", and "Eliminate Rivals: Remove or neutralize competing claimants if necessary" are abstract directions rather than specific, executable guidance, leaving key details missing.

2 / 3

Workflow Clarity

The 7-step process is clearly sequenced and a Verification section exists, but the destructive "Eliminate Rivals" step has no inline validation gate and there is no error-recovery feedback loop when instability warning signs are detected.

2 / 3

Progressive Disclosure

Under 50 lines with no need for external references, yet organized into clear sections (Overview, Priority Order, Resolution Process, Warning Signs, Expected Outcome, Verification), satisfying the simple-skill allowance for a top score.

3 / 3

Total

10

/

12

Passed

Description

100%

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 strong description: third-person voice, explicit "Use when" trigger, and a concrete enumeration of what the skill provides. It is specific, complete, and clearly differentiated with no over-claims or padding.

DimensionReasoningScore

Specificity

Lists multiple concrete components — "priority ordering (太子, eldest legitimate son, talented son, brother)", "resolution process with ministerial council", "external power assessment", and "rival neutralization protocols" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both: what it provides (priority ordering, resolution process, assessments, protocols) and when to use it via the "Use when resolving disputed succession…" trigger clause.

3 / 3

Trigger Term Quality

"resolving disputed succession with multiple claimants or absent heirs" uses natural domain phrasing a user would say, with good coverage of the main trigger variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (dynastic succession disputes) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.