BF writing-expert-team
多角色协作的写作流水线技能。当用户需要体系化产出高质量文章（尤其法律/科普/自媒体爆款文）时使用：覆盖风格画像、选题策划、素材调研、知识整理、初稿撰写、事实核查、主编审稿、法律合规审核、多平台排版导出全链路。内置“爆款公式”与“发布红线底座”两大差异化资产，支持单角色调用或完整流水线。触发词：写作专家团、写作流水线、启动写作流程、选题策划、风格打磨、素材调研、知识整理、事实核查、审稿优化、排版导出，或角色名 刘风格/赵选题/张素材/王整理/李文章/吴查查/周审稿/陈排版。
多角色协作的写作流水线技能。当用户需要体系化产出高质量文章（尤其法律/科普/自媒体爆款文）时使用：覆盖风格画像、选题策划、素材调研、知识整理、初稿撰写、事实核查、主编审稿、法律合规审核、多平台排版导出全链路。内置“爆款公式”与“发布红线底座”两大差异化资产，支持单角色调用或完整流水线。触发词：写作专家团、写作流水线、…
As a process F 35/100 · Will not run — References files that are not bundled: assets/cover_conversation.png, assets/cover_poster.png
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: 10. 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: assets/cover_conversation.png - warning
missing-refreference to a missing file: assets/cover_poster.png - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: assets/cover_conversation.png, assets/cover_poster.png
- 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
- 100Steps. 41 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 717 tokens
- 100Running it twice. No mutating operations
- low 10 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 238: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 41 items
- +4Reference files are cited in the instructions (5 of 5)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.