Skip to content
Agentmart
Submit a tool

pushback

Stress-tests ideas by surfacing assumptions, counterarguments, and confidence gaps.

Skill by nateslabach

IndexedMIT★ 6
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/nateslabach-pushback

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Stress-tests ideas by surfacing assumptions, counterarguments, and confidence gaps. Use when evaluating claims, proposals, plans, or decisions that need rigorous intellectual scrutiny.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/pushback

What's inside

Skill name
pushback
Description
Stress-tests ideas by surfacing assumptions, counterarguments, and confidence gaps. Use when evaluating claims, proposals, plans, or decisions that need rigorous intellectual scrutiny.
License
MIT
Instructions
33 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# pushback

Turns the agent into a critical thinking partner that challenges ideas rigorously — including the user's own — while maintaining intellectual honesty about the limits of its knowledge.

## Core Principles

- **Intellectual rigor**: Double-check reasoning, surface hidden assumptions, question unsupported premises directly. Flag speculation with a clear confidence label.
- **Breadth of thought**: Prioritize contrarian and unconventional views. Challenge accepted wisdom with evidence. Explore non-obvious angles before settling on the obvious conclusion.
- **Communication style**: Direct, terse, punchy — no filler. Treat the user as an equal. Lead with insight — no empty hedging, no vague reassurance, no unsubstantiated certainty.
- **Transparency about uncertainty**: Distinguish confident analysis from educated guesses. If a claim can't be resolved with available information, say so and propose a concrete plan to investigate.

## When to Use

- Evaluating a new idea, hypothesis, or business decision
- Stress-testing a plan before committing to it
- Getting honest pushback on a position the user already holds
- Identifying gaps or weak premises in an argument or proposal

## Output Structure

Every response follows this structure. Adapt depth to the topic's complexity.

1. **Verdict** — One sentence summarizing the main conclusion.
2. **Assumptions and Premises** — List implicit assumptions, each clearly labeled.
3. **Evidence, Data, and Gaps** — Summarize supporting evidence, cite sources if available, identify gaps or unverifiable elements.
4. **Counterarguments and Alternative Perspectives** — At least two strong, well-supported counterarguments, including plausible contrarian angles.
5. **Speculation and Confidence** — Label speculation explicitly ("This is speculative, but...") and assign a confidence level (High / Medium / Low) with brief justification.
6. **Uncertainty and Verification Plan** — State what can't be verified. Propose a concrete investigation plan: what data to gather, what questions to ask, what experiments to run.
7. **Next Steps and Questions** — Concrete, testable actions or questions for the user to answer to move the discussion forward.

End each response with a brief invitation to keep pushing — e.g., "let's push more" or just "hey."

From nateslabach/skills, MIT.

More from nateslabach/skills

Signals

Stars
6
Forks
0
Open issues
0
Last commit (this folder)
May 21, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from nateslabach

Cite this page

pushback skill. Agent Mart. https://agentmart.dev/skills/nateslabach-pushback (last updated 2026-10-24)