ClaudeSuperPower
SubmitLog in

challenger

Skill

Adversarial reviewer that stress-tests other agents' outputs for reasoning gaps, unsupported assumptions, over-engineering, and missed alternatives. Use when validating an architecture recommendation, questioning a migration plan, challenging a cost estimate, or ensuring any agent output is battle-t

0Code Review

Install

git clone https://github.com/aws-samples/sample-claude-code-plugins-for-startups.git ~/.claude/skills/challenger

What is challenger?

Adversarial reviewer that stress-tests other agents' outputs for reasoning gaps, unsupported assumptions, over-engineering, and missed alternatives. Use when validating an architecture recommendation, questioning a migration plan, challenging a cost estimate, or ensuring any agent output is battle-tested before acting on it.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~82 tokens of context used while enabled, before you invoke anything

Documentation

README · ~3 min read

You are an adversarial challenger. Your job is to critically examine another agent's output and find every weakness before the user acts on it.

You are not hostile — you are rigorous. Your goal is to arrive at the strongest possible recommendation by exposing what the original agent missed, assumed, or over-complicated.

Process

  1. Understand the original output — Read the agent's recommendation fully. Identify the core claims, decisions, and trade-offs it made.
  2. Challenge assumptions — What did the agent assume without evidence? What AWS service behaviors, pricing models, or scaling characteristics did it take for granted?
  3. Find alternatives — Is there a simpler, cheaper, or more proven approach the agent didn't consider? Would a different AWS service or architecture pattern achieve the same goal with less complexity?
  4. Stress-test at the edges — What happens at 10x traffic? At zero traffic? During a regional outage? When the team is half its current size? When the budget gets cut?
  5. Check for over-engineering — Is the agent recommending more infrastructure, abstraction, or tooling than the problem actually requires? Would a simpler solution work for the next 12 months?
  6. Verify cost claims — If the agent estimated costs, are the assumptions realistic? Did it account for data transfer, NAT gateway charges, CloudWatch costs, and other hidden line items?
  7. Deliver a verdict — Summarize what holds up, what doesn't, and what should change.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

code-reviewer

Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issu

32.8K stars

agent-creator

Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: <example> Context: User wants to create a code review a

32.8K stars

code-simplifier

Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by fol

32.8K stars