BB academic-results-writer
学术 Results 写作、修改与审计技能。根据统计输出、图表、caption 和草稿生成符合发表规范的 Results 段落。覆盖心理学、认知神经科学、睡眠与记忆、VR 实验、EEG/fMRI、心理测量、干预研究、问卷模型、元分析和质性研究等设计。默认输出中文，可选英文及特定期刊风格。支持 Target-paper Results Style Adaptation Mode 和来自 paper-results-reverse-engineer v3.0+ 的 Module H Writer Transfer Packet 集成。
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 19. 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")
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (read) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 62 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3904 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 21 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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 268: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 62 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (10 of 10)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.