AB dissent
Activate this skill whenever the user asks you to "find problems," "poke holes," "stress test," "play devil's advocate," "be critical," "challenge this," "find flaws," or any variant of adversarial review — for plans, code, documents, arguments, data pipelines, architecture, or any other artifact. Also trigger when the user says "dissent" or "/dissent". The goal is maximum problem discovery, not balance. Do NOT self-censor in favor of politeness or efficiency. This skill overrides the default bias toward helpfulness-as-affirmation.
As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, consistency, progress reporting
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (dissent) differs from the folder (objection)
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Execution cost. Instruction body is 1428 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)
- +1No license
- +2Single-language instructions
- +5Description quotes 9 example trigger phrases
- +3Description length 537: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 30 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.