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.

68

Quality

86%

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

78%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.

A concise, well-structured instruction skill with a clear sequenced workflow and explicit verification steps. The main gap is the absence of a feedback/retry loop, which keeps workflow clarity at 4 rather than 5.

Suggestions

Add a brief feedback loop in the Verification section: if a consensus check fails, re-consult the dissenting source before finalizing the decision.

Tighten Step 1 lines (e.g., merge 'Clearly articulate the major question' and 'Ensure the matter is significant enough') to reduce minor verbosity.

Optionally include a one-line concrete example of applying the three-agree rule to make the interpretation table immediately actionable.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with minimal padding, though a few lines ('Clearly articulate the major question', 'Ensure the matter is significant enough') are slightly verbose and could be tightened.

4 / 5

Actionability

Provides concrete, specific guidance — ordered consultation sources, named consensus scenarios (Great Harmony, three-agree, divination-disagrees), and explicit decision rules — though it is instruction-only with no executable code, which is acceptable here.

4 / 5

Workflow Clarity

Clear three-step sequence with a dedicated Verification section containing explicit checkpoints; falls just short of 5 because it lacks a true validate-fix-retry feedback loop for error recovery.

4 / 5

Progressive Disclosure

A short (<60 line), single-purpose skill with no external references and well-organized section headers, meeting the simple-skill exception for full marks.

5 / 5

Total

17

/

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.

A well-crafted description that clearly answers both 'what' and 'when' in third person with concrete, domain-specific language. It is specific, distinct, and uses an explicit trigger clause.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete components (turtle shell, milfoil divination, ruler deliberation, ministerial advice, popular sentiment, consensus-ranked decisions); minor gaps keep it just below the fully comprehensive anchor.

4 / 5

Completeness

Explicitly states both what it does ('Combines turtle shell and milfoil divination with ruler deliberation... to reach decisions ranked by consensus level') and when to use it ('Use when resolving major governance doubts through multi-source consultation').

5 / 5

Trigger Term Quality

Includes natural trigger phrases like 'Use when resolving major governance doubts through multi-source consultation' and domain terms (divination, consultation, consensus), though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a very specific niche (ancient divination-based governance) with distinct triggers, making conflict with other skills minimal.

5 / 5

Total

18

/

20

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.

Validation — 16 / 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.