SKILLEMALL.ai

BF bazi-daily

面向“今日运势/今天适合做X吗/今日宜忌”类咨询的八字日运解读技能。使用场景:用户在 OpenClaw 中询问当日运势、某事项是否适合今天做、今日吉凶与建议时触发。技能会自动读取当前日期,查询当日对应的流年、流月、流日,并结合用户的八字四柱进行分析;若用户为首次使用且无个人四柱记忆,先引导用户提供四柱并写入长期记忆,后续复用无需重复询问。

modbender/skill-library-mcp Agent Skills author: modbender MIT 7 files body ≈ 824 tokens Open the sourcegithub.com analyzed 4 d ago

面向“今日运势/今天适合做X吗/今日宜忌”类咨询的八字日运解读技能。使用场景:用户在 OpenClaw…

As a process F 49/100 · Will not run — References files that are not bundled: assets/bazi_daily_calendar_2026.xlsx

ProcedurePersonal productivitytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
F
49/100
Will not run
References files that are not bundled: assets/bazi_daily_calendar_2026.xlsx
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: assets/bazi_daily_calendar_2026.xlsx

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: assets/bazi_daily_calendar_2026.xlsx
  • 0Tools and files. 1 referenced file(s) missing: assets/bazi_daily_calendar_2026.xlsx
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 67 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 824 tokens
  • 100Running it twice. No mutating operations
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 170: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 67 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.