A skill your agent uses when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, "convene the panel", get a brutal second opinion before building…

MITAuto-check passedTesting & QA

Install Roast

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill roast -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-skills roast --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/productivity/roast/skills/roast .claude/skills/roast && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
roast
GitHub stars
28k
Token cost
~2.6k tokens
SKILL.md length
1,271 words
Files
10 (incl. scripts, references, assets)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, "convene the panel", get a brutal second opinion before building…

  • Works in 3 steps: Frame the idea → Run the 5-angle panel (5 reviewers, in… → Call the verdict
  • Someone asks to roast an idea
  • SKILL.md covers What this does, Step 1 — Frame the idea, Step 2 — Run the 5-angle panel… and Step 3 — Call the verdict, plus 6 more sections
  • Runs Python scripts from its folder; calls python

What it does

Roast is an agent skill from alirezarezvani/claude-skills. Use when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, "convene the panel", get a brutal second opinion before building something, or says "/roast". Spins up a 5-angle panel (Critic, Champion, Analyst, Investigator, Customer) that attacks the idea from every angle, then a Judge returns one GO / RESHAPE / KILL verdict with the cheapest test to de-risk it.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `README.md`, `assets/example_roast_verdict.md` and `assets/roast_brief_worksheet.md`).

It sits in Testing & QA, covering Load testing. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • Someone asks to roast an idea
  • Stress-test an idea
  • Validate a business idea
  • Convene the panel

Example prompts

  • “convene the panel”
  • “/roast”
  • “/roast”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Frame the idea
  2. Run the 5-angle panel (5 reviewers, in parallel)
  3. Call the verdict

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Roast loads about 2.6k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 1,271 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,271 words, ~2,617 tokens.

Download SKILL.mdSave it as .claude/skills/roast/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
roast
description
Use when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, "convene the panel", get a brutal second opinion before building something, or says "/roast". Spins up a 5-angle panel (Critic, Champion, Analyst, Investigator, Customer) that attacks the idea from every angle, then a Judge returns one GO / RESHAPE / KILL verdict with the cheapest test to de-risk it.
argument-hint
[the idea to roast]
license
MIT
metadata.version
1.0.0
metadata.build_pattern
Path-B persona skill — adversarial panel + deterministic verdict tools
metadata.distinct_from
andreessen (single market-first lens, not a panel); c-level boardroom (enterprise C-suite pipeline requiring company-context onboarding); grill-me…

Roast — 5-Angle Idea Panel → One Verdict

Portability: Reasoning-led skill with 3 stdlib Python tools. No external APIs, no LLM calls in scripts. Works in Claude Code CLI and Claude.ai web. The panel does the depth; the Judge does the call.

What this does

Claude's default is to agree with you. /roast is the opposite. It convenes a panel of five independent reviewers — The Critic, The Champion, The Analyst, The Investigator, and The Customer — who tear an idea apart and build it up from every angle, then a Judge synthesizes everything into one honest verdict. Use it before you sink time and money into building the wrong thing.

The panel is adversarial on purpose. No reviewer is allowed to hedge or be polite. The point is to surface what you can't see because you're too close to it.

Step 1 — Frame the idea

If $ARGUMENTS contains the idea, start there. Then ask the user a tight set of clarifying questions so the panel has real context to work with. Ask only what hasn't already been provided. Keep it to 3-4 questions max, in one batch:

  1. The idea in one or two sentences (what it is, what it does).
  2. Who it's for and how it makes money (the buyer + the price/model).
  3. Your edge — relevant skills, audience, or assets you already have.
  4. Constraints — budget, timeline, how fast you need first dollar.

If the user says "just run it" or gives you enough already, skip the questions and proceed. Don't over-interrogate. One round, then run the panel.

Assemble the brief with scripts/brief_builder.py — it normalizes the four load-bearing inputs into one paragraph and tells you if anything critical is still missing before you spend five subagents:

bash
python scripts/brief_builder.py \
  --idea "AI that drafts grant applications for small nonprofits from a 10-min intake call" \
  --who "1-3 person nonprofits with no grant writer" \
  --money "$99/mo SaaS" --edge "I ran a nonprofit for 8 years" \
  --constraints "bootstrapped, first dollar in 30 days"

Paste the resulting brief verbatim into every panelist's prompt, so all five judge the same thing.

Step 2 — Run the 5-angle panel (5 reviewers, in parallel)

Spin up all five reviewers in parallel in a single message (one Task call each, subagent_type: general-purpose). Paste the same brief into each, then give each its mandate below.

Each panelist must return: a one-line stance, their 3-5 sharpest points, the single most important thing the user must hear, and a 1-10 score on their own dimension (1 = walk away, 10 = no-brainer).

1. The Critic — "What kills this?"

You are The Critic on an idea panel. Assume this idea fails. Your job is to find the fatal flaws, the fastest way it dies, and the load-bearing assumptions that are probably wrong. Be ruthless and specific. No hedging, no "but it could work." Attack the weakest points. THE BRIEF: [brief]

2. The Champion — "What's the 10x upside?"

You are The Champion on an idea panel. Make the strongest possible case FOR this idea. Find the biggest upside, the 10x version, the adjacent opportunities and unlock points the founder isn't seeing. Fight for the potential. Be specific about where the real money and leverage could be. THE BRIEF: [brief]

3. The Analyst — "Does the logic actually hold?"

You are The Analyst on an idea panel. Use NO outside research and NO web. Reason purely from first principles: does the core mechanism make sense, do the incentives line up, is the underlying logic sound, does the math even work in theory? Strip it to fundamentals and tell us if it holds together. THE BRIEF: [brief]

4. The Investigator — "What does the real market say?"

You are The Investigator on an idea panel. Use web search. Bring real-world evidence: who the existing competitors are, market size or demand signals, what comparable products charge, whether this is validated by what's already out there or contradicted by it. Cite what you find. Is the real world saying yes or no? THE BRIEF: [brief]

5. The Customer — "Would I actually pay?"

You are The Customer on an idea panel. Role-play the exact target customer described in the brief. React as them, in first person. Would you actually pay for this? What's your real objection? What would make you choose a competitor or just do nothing instead? What price feels right, and what would make you say yes today? Be the honest, slightly skeptical customer, not a cheerleader. THE BRIEF: [brief]

Show full SKILL.md (577 more words)Show less

Step 3 — Call the verdict

Once all five return, YOU act as the Judge. Read every panelist's findings, weigh them, and synthesize one decisive verdict. Do not just average the scores. Run the five scores through the synthesizer so the call is reproducible weighting, not vibes — then name the real tension between the reviewers and resolve it in prose:

bash
python scripts/verdict_synthesizer.py \
  --critic 4 --champion 8 --analyst 7 --investigator 5 --customer 6

The tool weights demand (Customer) and survival (Critic) heaviest and the bull (Champion) lightest, applies hard gates (a Customer who won't pay, or a fatal flaw the Critic landed, vetoes a GO), and flags the widest disagreement as the tension you must resolve. Use its verdict + confidence as your spine; write the prose yourself.

Fold in the economics lens yourself: rough pricing, realistic time-to-first-dollar, and whether the user can actually ship this fast given the edge they described. Then design the cheapest test from the riskiest assumption the panel surfaced:

bash
python scripts/cheapest_test_designer.py --risk price --price 99

Output the verdict in this exact shape:

## THE VERDICT: GO / RESHAPE / KILL
Confidence: [low / medium / high]

**The call in one line:** [the decision, plainly]

**Why:** [2-3 sentences resolving the panel's tension]

**Biggest risk:** [the single thing most likely to kill it]
**Biggest upside:** [the strongest reason to do it]

**Money read:** [rough price, time-to-first-dollar, can they ship fast]

**The cheapest 48-hour test:** [the smallest, fastest thing they can do
to validate the riskiest assumption BEFORE building anything]

**If RESHAPE:** [the specific pivot that fixes the fatal flaw while keeping the upside]

Then list the five panel scores in one line: Critic X/10 · Champion X/10 · Analyst X/10 · Investigator X/10 · Customer X/10.

Tooling

ScriptRole
scripts/brief_builder.pyNormalizes the 4 load-bearing inputs into one shared brief; flags missing/thin inputs before the panel convenes.
scripts/verdict_synthesizer.pyWeights the 5 panel scores (Customer + Critic heaviest, Champion lightest), applies veto gates, flags the real tension → GO / RESHAPE / KILL + confidence.
scripts/cheapest_test_designer.pyMaps the riskiest assumption (demand/price/feasibility/differentiation/channel/retention) to a concrete 48-hour test with pass/fail signals.

References

Assets

Rules

  • Every reviewer stays in character. None of them hedges or softens. The value is in the friction.
  • The Judge must make an actual call. "It depends" is not a verdict. Pick GO, RESHAPE, or KILL and own it.
  • Do not average the scores. A high mean can hide a fatal split or a vetoed dimension — run the synthesizer and resolve the tension it names.
  • The cheapest 48-hour test is the most important output. It's how the user finds out if they're right without building the whole thing.
  • Keep the final verdict skimmable. The panel does the depth; the Judge does the decision.

Anti-Patterns To Reject

  • Softening the verdict to spare feelings ("there's definitely something here…"). If it's a KILL, say KILL.
  • Averaging the five scores into a mushy 6/10 and calling it a day.
  • Letting the Champion's enthusiasm override a Customer who won't pay or a Critic who found the fatal flaw.
  • Ending on advice with no falsifiable test ("go validate it"). Name the test, the cost, and the pass/fail line.
  • Running the panel on a one-line brief so all five argue past each other.

Distinct From (don't reach for the wrong tool)

  • productivity/andreessen — a single market-first operator. roast is five independent lenses → a judge. Use andreessen when you specifically want the market-dominates thesis; use roast when you want 360° coverage.
  • c-level-advisor boardroom / /cs:boardroom — an enterprise C-suite pipeline that needs company-context.md onboarding and outputs a board memo. roast is a zero-setup, solo-founder, 90-second gut check.
  • engineering/grill-me — interrogates a plan one question at a time to reach shared understanding. It does not issue a GO/KILL verdict. Roast judges; grill-me clarifies.

Version: 1.0.0 Build pattern: Path-B persona skill — adversarial panel preserved + deterministic verdict tooling added.

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references, assets) in productivity/roast/skills/roast of alirezarezvani/claude-skills.

  • SKILL.md
  • README.md
  • assets/example_roast_verdict.md
  • assets/roast_brief_worksheet.md
  • references/adversarial_panel_canon.md
  • references/cheapest_test_canon.md
  • references/verdict_synthesis_method.md
  • scripts/brief_builder.py
  • scripts/cheapest_test_designer.py
  • scripts/verdict_synthesizer.py

Open the folder on GitHubat commit 19392f7

Compare with similar skills

Roast next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Roast compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Roast this skillalirezarezvani/claude-skills28k—~2.6kAutomated safety check: PassMIT
Writing Livekit Scenarioslivekit-examples/agent-starter-python2641 repos~2.5kAutomated safety check: PassMIT
Go Testingcxuu/golang-skills1701 repos~1.3kAutomated safety check: PassApache-2.0
Goalcraftgrp06/goalcraft102—~3.8kAutomated safety check: PassMIT
Thinking Partnermattnowdev/thinking-partner206—~4.4kAutomated safety check: PassMIT
Visionkunchenguid/vision329—~2.9kAutomated safety check: PassMIT

Similar skills

  • Writing Livekit Scenarios

    livekit-examples/agent-starter-python

    Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them.

    264 GitHub starsUsed in 1 repo~2.5k tokens
    Testing & QAAuto-check passed
  • Go Testing

    cxuu/golang-skills

    A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.

    170 GitHub starsUsed in 1 repo~1.3k tokens
    Testing & QAAuto-check passed
  • Goalcraft

    grp06/goalcraft

    Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work.

    102 GitHub stars~3.8k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Thinking Partner

    mattnowdev/thinking-partner

    A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.

    206 GitHub stars~4.4k tokensUpdated 6 mo ago
    Testing & QAAuto-check passed
  • Vision

    kunchenguid/vision

    Draft and stress-test a VISION.md for a repository, then iterate with the author on an interactive review board until approved.

    329 GitHub stars~2.9k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Volt Load Testing

    owenHochwald/volt

    Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons.

    141 GitHub stars~1.2k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo
  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed
  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Categories

Questions about Roast

What does Roast do?

A skill your agent uses when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, "convene the panel", get a brutal second opinion before building…. Roast is an agent skill from alirezarezvani/claude-skills. Use when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, "convene the panel", get a brutal second opinion before building something, or says "/roast".

When should I use Roast?

Roast fits situations like: someone asks to roast an idea; stress-test an idea; validate a business idea; convene the panel.

How do I install Roast in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill roast -a claude-code`. Or copy the skill folder (productivity/roast/skills/roast in alirezarezvani/claude-skills) into .claude/skills/roast in your project. Claude Code loads it when a task matches its description.

How do I install Roast in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill roast -a codex`. Or copy the skill folder (productivity/roast/skills/roast in alirezarezvani/claude-skills) into .agents/skills/roast in your project. Codex loads it when a task matches its description.

Can I use Roast in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill roast -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/roast, .gemini/skills/roast, .github/skills/roast and .opencode/skills/roast in your project.

What does Roast need to run?

Going by SKILL.md and its folder, Roast needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Roast access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Roast safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Roast use?

Roast is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Roast use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.

What are the alternatives to Roast?

Skills that share tags, products or a category with Roast: Writing Livekit Scenarios (livekit-examples/agent-starter-python, 264 stars), Go Testing (cxuu/golang-skills, 170 stars), Goalcraft (grp06/goalcraft, 102 stars) and Thinking Partner (mattnowdev/thinking-partner, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Roast?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,829 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.