BC menstrual-health-tracker
经期健康追踪与多维分析系统。当用户需要记录经期、查看周期规律、分析症状模式、获取健康建议时触发。支持全生命阶段（初潮前→经期→备孕→孕期→产后→围绝经期→绝经后），提供数据可视化仪表盘和科学建议。English trigger: period/menstrual cycle/ovulation/TTC/pregnant/postpartum/menopause/perimenopause. 中英双语支持。
经期健康追踪与多维分析系统。当用户需要记录经期、查看周期规律、分析症状模式、获取健康建议时触发。支持全生命阶段（初潮前→经期→备孕→孕期→产后→围绝经期→绝经后），提供数据可视化仪表盘和科学建议。English trigger: period/menstrual…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: 经期健康追踪与多维分析系统。当用户需要记录经期、查看周期规律、分析症状模式、获取健康建议时触发。支持全生命阶段（初潮前→经期→备孕→… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 51/100
- 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 149 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3364 tokens
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
- -216 emoji in the instructions: noise for the model
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 204: enough signal without eating the budget
- +4Structure: 54 headings
- +3Step-by-step instructions: 149 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.