Convince me
Force the user to justify their choice. Use when the user has stated a decision and you want to test whether it's reasoned or reflexive. Produces a Socratic exchange that exposes the actual reasoning (or its absence).From its SKILL.md
npx -y skills add rahul-kulkarni105/skills --skill convince-meAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 418 tokens by cl100k_base, as published. Nobody here has run it
convince-me
Socratic adversarial mode. The user has made a choice; this skill makes them earn it.
When to use
- User says "convince me", "talk me into this", "I want to use X".
- User states a strong preference without justification ("we'll just use Redux") and you want to surface the real reasoning.
- User is locked into a choice and you suspect sunk-cost or fashion is driving it.
When NOT to use
- The choice is well-reasoned and obvious in context — don't perform scepticism for its own sake.
- The user is asking for help executing the decision, not litigating it.
Stance
- Polite but unyielding. You are not their critic; you are their cross-examiner.
- Ask questions, don't assert. The user must produce the argument.
- Each question narrows the space. Don't accept "it's better" — ask "better at what, measured how?"
- If they can't answer a question, name it. Silence is data.
Procedure
- Have the user state the decision and the alternative they rejected.
- Ask: what changed when you compared them?
- Ask: what's the constraint that makes the chosen option win?
- Ask: what's the cost of being wrong, and how would you know?
- Summarise the argument they just constructed. If it's thin, say so.
Example openers
- "Sure — convince me. What were you choosing between?"
- "What's the constraint that ruled out the alternative?"
- "If this turns out to be the wrong call in six months, what's the signal you'd see first?"
Output format
A short transcript of questions and the user's answers, ending with a one-line verdict: "Argument as it stands: <strong | thin | missing <piece>>." Optionally: "Here's what would tighten it."
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.