Skip to content
Skills Library
Management & product · Review & audit

pushback

/pushback

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

Repository
skills ↗
Licence
MIT
Last repository change
29.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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

Original author description

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

How it works

  1. Core Principles
  2. When to Use
  3. Output Structure
Original SKILL.md headings · 33 lines, 334 words
SKILL.md preview
---
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.
---

# 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."

Versions

RepositoryScoreLicence
This page · nateslabach/skills90MIT
Ovid/paad100MIT
Ovid/paad100MIT
Ovid/paad100MIT

Database snapshot: 13.11.2026 · package version 01e31b0e92c9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100stress-test
    Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this…
  • 100constructive-dissent
    Structured disagreement protocols that expose weaknesses, test assumptions, and generate alternatives. Use when stress-testing proposals, playing devil's advocate, challenging architectural decisions, or auditing assumptions before finalizing plans.
  • 100interview
    USE WHEN spec, requirements, interview, flesh out idea, plan feature, business idea, design review, ideation, document draft, devil's advocate, stress test, brainstorm, clarify, quick spec, scope this, help me think through, what am I missing. Crystallize ideas into actionable…
  • 100discernment-nudge
    Append critical epistemic scrutiny, assumption checks, and missing context prompts before finalizing high-stakes plans, architecture decisions, cost estimates, or security claims. Use when delivering consequential recommendations or actionable strategies where unstated…
  • 90think-and-decide
    Pressure-test ideas, plans and decisions before anything is built or changed. Use for "grill me", "grill this plan", "stress-test", "poke holes", "think this through", "deep think", "should we", "go/no-go", "ship now or wait", "tradeoff", "which option", "second opinion",…
  • 100critical-intuition
    Stress-test, critique, and challenge existing ideas through pattern recognition, bias detection, Bayesian reasoning, blind-spot exposure, and red-flag identification. Use when the user asks to stress-test a plan, challenge assumptions, find flaws, identify risks in an idea,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.