AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Pushback

skill-nateslabach-skills-pushback · by nateslabach

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
0 installs
28 views
0.0% view→install

Install

$ agentstack add skill-nateslabach-skills-pushback

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-nateslabach-skills-pushback)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Pushback? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.