AC critical-writing
多角色辩论写作工作流。通过"前置三问 → 规划 → 分步写作 → 辩论法庭 → 综合改写" 的闭环流程，让多个批评者角色互相对抗，在争论中打磨出高质量内容。 核心差异：不是单个名人单向批评，而是 2-3 个批评者就同一篇稿子展开辩论—— 一方指出问题，另一方反驳或补充，最终从争论中提炼出真正有价值的改写方向。 触发场景（必须使用本 skill）： - 用户说"帮我写一篇 / 起草一份 / 我想写关于..." - 用户需要写文章、报告、分析、方案、帖子、邮件等任何正式或半正式内容 - 用户提到"批判性写作 / 多角色审稿 / 辩论改写 / debate writing" - 用户希望 AI 协作写作而非一次性生成 不要跳过任何步骤，即使用户说"直接写就好"，也必须完成前置三问再动笔。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 349 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "difficulty"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1233 tokens
- 100Running it twice. No mutating operations
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
- +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
- +5Description quotes 3 example trigger phrases
- +3Description length 348: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.