AC tech-debate
针对技术话题，模拟正方与反方两派进行多阶段、多轮结构化辩论，阶段之间用户可干预（支持某方/补充论点/提出新视角），最终由 Judge 提炼全局共识、分歧与实践建议。当用户说【对XXX进行技术辩论】、【debate: XXX】、【正反两方讨论XXX】、【辩论一下XXX】、【tech debate】时触发。支持用户设置最大轮数（默认5轮/阶段），Judge 根据辩论情况动态决定阶段内是否提前收敛。
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 the model run — optional
- 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: 4. 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 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. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 452 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
- +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
- +1No license
- +2Single-language instructions
- +3Description length 198: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.
External checks
ClawHub: clean
This is a markdown-only skill that structures technical debates and does not request file access, commands, credentials, network use, or persistence.
LLM: benign (high) · VirusTotal: · 29 May 2026