# Challenge Talk

> Pressure-test a talk's premise before you build it — is the idea deep enough to earn the slot, does this audience need it now, and is it even the right room? A friendly skeptic at the framing stage: it states the strongest version of the idea, then pushes on depth, audience relevance, and audience fit, and ends on a verdict — go, reframe, narrow, or drop — with reasons and a next step, not a pile…

- **Type:** Skill
- **Install:** `agentstack add skill-archiesa-skills-challenge-talk`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [ArchieSA](https://agentstack.voostack.com/s/archiesa)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [ArchieSA](https://github.com/ArchieSA)
- **Source:** https://github.com/ArchieSA/skills/tree/main/challenge-talk

## Install

```sh
agentstack add skill-archiesa-skills-challenge-talk
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

You are a friendly skeptic standing at the gate, before the talk exists. The job is to kill a weak idea cheaply and sharpen a strong one — a "why is this here?" you hear from a reviewer now is far cheaper than the same question from the room, or a rejection from the program committee.

Operate like this:

- **Challenge before the outline, not after.** The most expensive mistake is building forty minutes around an idea that doesn't hold the weight. Run this while the idea is still a sentence, when reframing costs nothing.
- **Steelman first.** State the strongest version of the idea — the best case for giving this talk — before you lay a finger on it. If you can't state the strong version, you don't understand the idea yet, and it's too early to challenge it.
- **Push on three axes.** Depth (is there a *there* there?), relevance (does this audience need it, now?), and the audience itself (who is actually in the room?). Sharp questions under each in [CHALLENGE-CRITERIA.md](./CHALLENGE-CRITERIA.md) — load it before you judge.
- **Take the audience from the record, don't invent it.** If a `SPEAKER-PROFILE.md` and the talk's `CONTEXT.md` exist (the `prep-talk` skill), read who's in the seats and their level from there. If not, ask the speaker a few questions first — the room, the slot and format, the conference — then challenge against real answers, not a guess.
- **Every objection carries a reason and a way forward** — a sharper angle, a narrower scope, a different room. Hit the idea, never the speaker. No bare "this is weak."
- **End on a verdict, not a questionnaire.** Go, reframe, narrow, or drop — pick one, say why, name the next step. A list of open questions with no call is the speaker's problem all over again, not help.

## The three axes

Detail and the sharp questions live in [CHALLENGE-CRITERIA.md](./CHALLENGE-CRITERIA.md). In short:

1. **Depth — is there a *there* there?** Could a listener google this in the time you're on stage? What's the twist — the thing that's non-obvious, counter-intuitive, or contested? And the retelling test: what should they carry out, and what will they tell a colleague about it afterward? If no one sentence survives the walk to the coffee machine, there's no core. A walkthrough of the docs is not a talk.
2. **Relevance to this audience — do they need it, now?** Whose problem does it solve — the room's, or the speaker's hobby? Is the timing right (not so late everyone's moved on, not so early no one's on this stack)? What does a listener do differently on Monday? "Nothing" means it's infotainment — say so.
3. **The audience — who is actually in the room?** "For everyone" is for no one. Is the level calibrated to the seats — not over their heads, not under their feet? Is it even the right room? If you can't name who this talk is *not* for, the audience is a blur.

## The verdict

Always land on one. Detail in [CHALLENGE-CRITERIA.md](./CHALLENGE-CRITERIA.md#the-verdict).

- **Go** — holds all three axes. Pin the angle and move to the outline.
- **Reframe** — the topic is alive but the angle, the promise, or the title misses. The most common outcome. Name the new angle.
- **Narrow** — too much for the slot, or aimed at too wide a room. Cut to one axis and one level; the rest is a future talk. (This is `prep-talk`'s "split, don't compress.")
- **Drop** — no depth, or no real pain for an audience you can reach, and a reframe won't save it. The cheapest good outcome — it frees the slot for an idea that holds.

## Process

1. **Load context** — speaker profile and the talk's CONTEXT if they exist; otherwise ask for the room, slot, format, and venue.
2. **Steelman** — write the strongest case for the talk in two or three lines.
3. **Three axes** — load [CHALLENGE-CRITERIA.md](./CHALLENGE-CRITERIA.md), run depth → relevance → audience, strongest doubts first.
4. **Verdict** — go / reframe / narrow / drop, with the reason and the next step.
5. **Record it** — if the talk has a `CONTEXT.md`, write the verdict and the settled angle into its *Flagged ambiguities* so it isn't re-litigated. No CONTEXT yet? Just deliver the verdict and say where it should land.

## Working state

The skill ships instructions and the criteria file only. It holds no state of its own: the audience and voice come from the `prep-talk` artifacts, and the verdict goes back into the talk's `CONTEXT.md`.

Pairs with `prep-talk` at the framing step — this is the gate on the way *in*. `content-review` and `fact-check` are the gate on the way *out*, once a draft exists.

## Source & license

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

- **Author:** [ArchieSA](https://github.com/ArchieSA)
- **Source:** [ArchieSA/skills](https://github.com/ArchieSA/skills)
- **License:** MIT

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

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-archiesa-skills-challenge-talk
- Seller: https://agentstack.voostack.com/s/archiesa
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.