CtrlK
BlogDocsLog inGet started
Tessl Logo

divination-decision-procedure

Use when resolving major governance doubts through multi-source consultation. Combines turtle shell (卜) and milfoil (筮) divination with ruler deliberation, ministerial advice, and popular sentiment to reach decisions ranked by consensus level.

69

Quality

85%

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

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is a well-structured, single-file procedural workflow with a clear sequence and verification checklist. Its weak spots are a partly redundant/soft Overview-Expected-Outcomes pair and a gap where the seven signs are listed but never wired into the interpretation step.

Suggestions

Tie the seven signs (rain/clearing/obscure/cloudy/overcoming/steadfast/changing) into Step 3 interpretation, or move them to a reference if they are not needed for the decision matrix.

Trim the Overview (it duplicates the description) and replace 'Expected Outcomes' benefit statements with concrete post-decision guidance or remove it.

Add a one-line recovery action to the Verification section (e.g., 'if a source was skipped or the consensus level is ambiguous, re-consult before deciding') to close the feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the Overview restates the frontmatter description and 'Expected Outcomes' lists benefits ('Clearer resolution', 'Legitimacy through comprehensive consultation') rather than instructions, so it could be tightened.

2 / 3

Actionability

The ordered consultation list and the consensus interpretation matrix are concrete, but the seven signs (rain/clearing/obscure/etc.) are introduced as a prerequisite yet never integrated into Step 3, and the divination mechanics themselves are unspecified.

2 / 3

Workflow Clarity

A clearly sequenced Step 1→2→3 process closes with an explicit three-item Verification checklist of confirm/validate/check steps, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

A single well-organized SKILL.md with clean sections and no need for external references fits the simple-skill exception for a top progressive-disclosure 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.

The description is well-crafted: it opens with an explicit 'Use when…' trigger, enumerates concrete consultation sources, and occupies a clearly distinct niche. Trigger and completeness are explicit rather than implied.

DimensionReasoningScore

Specificity

Lists multiple concrete components — 'turtle shell (卜) and milfoil (筮) divination with ruler deliberation, ministerial advice, and popular sentiment' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicit 'Use when…' trigger answers when, and 'Combines…divination with ruler deliberation, ministerial advice, and popular sentiment to reach decisions' answers what.

3 / 3

Trigger Term Quality

'Use when resolving major governance doubts' plus 'divination' and 'consultation' are natural terms a user would say for this domain; the technical 'consensus level' phrasing is minor.

3 / 3

Distinctiveness Conflict Risk

Ancient divination-based governance procedure is a clear, narrow niche with distinct triggers unlikely to overlap with other 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.