CD qingtian-buddhism
原始佛教/上座部修学助手：每日一故事、经典阅读、核心教义库、禅修引导、巴利小课堂、佛陀与圣弟子、修行打卡、问答检索、每日偈语。当用户提到佛陀、佛法、四圣谛、八正道、三法印、无我、禅修、内观、巴利三藏、阿含、上座部、法句经、念处、慈心禅、本生故事、缘起、五蕴、苦、涅槃时使用。
原始佛教/上座部修学助手：每日一故事、经典阅读、核心教义库、禅修引导、巴利小课堂、佛陀与圣弟子、修行打卡、问答检索、每日偈语。当用户提到佛陀、佛法、四圣谛、八正道、三法印、无我、禅修、内观、巴利三藏、阿含、上座部、法句经、念处、慈心禅、本生故事、缘起、五蕴、苦、涅槃时使用。
As a process D 35/100 · Unfinished process — References files that are not bundled: references/stories.md, references/suttas/, references/teachings/
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/stories.md - warning
missing-refreference to a missing file: references/suttas/ - warning
missing-refreference to a missing file: references/teachings/ - warning
missing-refreference to a missing file: references/practice-log.md - warning
missing-refreference to a missing file: references/_sources.md - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary"
Process rating: all ten parameters 35/100
- 0Tools and files. 5 referenced file(s) missing: references/stories.md, references/suttas/, references/teachings/
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 85Steps. 55 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2144 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 137: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 55 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.