CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

liuyao

六爻纳甲单事分析:已有六组三币记录时直接排盘,只有问题时先选择时间或随机起卦,再按对象和目标取用神。解读统一纳甲规则,不混入八字、紫微或梅花体用断法。

Quality

83%

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

81%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 well-structured, highly actionable body with genuine validation gates and checklists, and a clean one-level-deep reference layout that keeps deep algorithmic detail out of SKILL.md. The one concrete defect is the dangling examples/job_offer.json reference in the command example; minor rule repetition could also be consolidated.

Suggestions

Add the missing examples/job_offer.json to the bundle (or change the example command to pipe a sample via stdin, e.g. '... --input -'), so the documented invocation is runnable as written.

Consolidate the 'awaiting casting method / never auto-cast' rule, which is currently stated in the 输入入口 section, repeated under the casting_method field, and again in references/casting.md.

DimensionReasoningScore

Conciseness

The body is dense and rule-driven with no generic-concept padding — it assumes Claude's competence and only teaches skill-specific conventions (coin scoring, 爻 ordering, najia invariants). Anchor 4 fits: minor trimming possible, e.g. the 'awaiting method / no auto-casting' rule is restated in the 输入入口 section, again under casting_method, and again in casting.md, which keeps it short of anchor 5's 'every token earns its place'.

4 / 5

Actionability

Concrete and executable: exact CLI invocations ('python scripts/casting_cli.py --input examples/job_offer.json --output output.json'), a complete coin-encoding table, an inline JSON example with its expected outcome (泽水困,初爻、四爻动,变水泽节), and exact field enums and ISO time format. Anchor 4 rather than 5 because the example command cites examples/job_offer.json, which does not exist in the bundle, so it is not copy-paste runnable as written.

4 / 5

Workflow Clarity

The multi-step process is clearly sequenced with explicit validation gates: entry branching (coins present vs. question-only), '仅当 status=ready 才继续解读', a pre-reading 核对 checklist (coins、coin_score、爻序和明动位置), error handling '按具体缺项处理' rather than guessing, and a worked example with a known answer for self-verification. This matches anchor 5's explicit validation steps, error-recovery loops, and checklists; this is a read-only analysis skill so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Structure is good: four reference files (casting.md, yongshen.md, rules.md, interpretation.md) all exist, are one level deep, and are clearly signaled with inline links at the point of need; scripts and tests are appropriately placed. Anchor 4 rather than 5 because the body references examples/job_offer.json, a path absent from the actual bundle — a minor organization gap in the referenced-path structure the rubric says to score against.

4 / 5

Total

17

/

20

Passed

Description

78%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 strong, domain-anchored description that states concrete actions for both entry modes (existing coin records vs. question-only) and explicitly fences off adjacent divination systems. The main improvement opportunities are adding common user synonyms (摇卦, 解卦, 占卜) and a more explicit overall 'use when' trigger phrase.

Suggestions

Add a 'Use when...' style trigger phrase naming common user requests, e.g. '当用户提出六爻、摇卦、排盘或解卦占问时使用'.

Include the common synonyms 摇卦 / 解卦 / 占卜 as trigger terms so the description matches how users naturally phrase the request.

DimensionReasoningScore

Specificity

The description lists several concrete actions — '直接排盘', '先选择时间或随机起卦', '按对象和目标取用神', '解读统一纳甲规则' — plus explicit exclusions ('不混入八字、紫微或梅花体用断法'). It matches anchor 4 (several specific actions, minor gaps): output/interpretation format for the user is not covered, so it falls short of anchor 5's comprehensive coverage.

4 / 5

Completeness

The 'what' is clear (排盘, 起卦, 取用神, 纳甲解读) and the 'when' is present as explicit entry conditions ('已有六组三币记录时直接排盘,只有问题时先选择时间或随机起卦'). This is anchor 4: both present, but the overall invocation trigger (e.g. '当用户要求六爻排盘或解卦时使用') could be more explicit — it stops short of anchor 5's concrete 'Use when...' trigger phrases.

4 / 5

Trigger Term Quality

Good coverage of natural domain terms a Chinese user would say: '六爻纳甲', '排盘', '起卦', '用神', '解读'. A few common variations are missing ('摇卦', '解卦', '占卜'), fitting anchor 4 rather than anchor 5's comprehensive synonym coverage, but well above anchor 3's 'missing common variations' since the core invocation terms are all present.

4 / 5

Distinctiveness Conflict Risk

The domain is a highly specific divination school (六爻纳甲) and the description explicitly demarcates boundaries against the nearest neighboring skills ('不混入八字、紫微或梅花体用断法'). This is anchor 5: a clear niche with distinct triggers and minimal conflict risk; no neighboring anchor fits better.

5 / 5

Total

17

/

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

shanruoyu/liuyao-skill

Path

SKILL.md

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.