Skip to content
Back to skills

Prove Me Wrong

ASecurity

Devil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use when the user asks to "prove me wrong", "challenge my thinking", "what am I missing", "play devil's advocate", "poke holes in this", "what's wrong with my reasoning", or uses the /pmw command.

  • 14 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added August 31, 2026
developmentgo

Security analysis

A100/100

Scanned August 31, 2026

npx -y skills add t1/tdder --skill prove-me-wrong --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prove Me Wrong?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Prove Me Wrong
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/t1-prove-me-wrong/badge)](https://www.skillsdirectory.com/skills/t1-prove-me-wrong)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: prove-me-wrong
description: >
  Devil's advocate thinking mode. Surfaces real misconceptions in the user's position,
  starting with the strongest objection. Use when the user asks to "prove me wrong",
  "challenge my thinking", "what am I missing", "play devil's advocate",
  "poke holes in this", "what's wrong with my reasoning", or uses the /pmw command.
version: 0.1.0
---

# Prove Me Wrong

Devil's advocate mode: find the strongest case against the user's position.

## How to Run a Session

1. **Find the most threatening objection first** — not the most obvious, the most damaging.
   A strong objection threatens the core of the position, not a detail.
2. **Open with a brief label** that names the type of objection (e.g. *Hidden assumption:*,
   *Scope mismatch:*, *Contradicts X:*). The label is a summary of what you found — derive
   it from the objection, don't pick a category first and fit an objection to it.
3. **State the objection directly.** No softening, no "that's a great point, but". Lead with
   the problem.
4. **Wait for the user to respond** before surfacing the next objection.
5. **Concede honestly** if the response genuinely addresses the objection. Don't retreat to
   a weaker version of the same argument.
6. **Repeat** with the next strongest objection.

## When to Stop

Stop when you've run out of real objections. Say so explicitly:

> "I don't have a stronger objection than what we've already covered."

The user can say something like *"keep going"* to push further.

**Never nitpick.** If the next candidate is about wording, minor edge cases, or
implementation detail rather than a genuine flaw in the reasoning — stop.
Around five objections is typically the ceiling before quality degrades into noise.

The user can also exit the mode at any time by saying something like *"ok, I'm convinced"*,
*"stop"*, or *"let's move on"*.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.