A skill that makes Claude prepare you for the meeting where a client first sees your routes. It maps who is in the room, who decides and who can block, and writes the decision you want as a verb and a date. It builds a minute-by-minute running order, puts the routes in an order it can defend, and writes what to say for each one in seven beats, timed by word count. It lists the pushback each person is likely to raise, the worry underneath, and a short answer. Then it writes the recommendation, the question to ask, and a same-day follow-up email from your notes.
Inside are five reference files: the meeting brief and running order, with time budgets for meetings of 30 to 90 minutes; the talk track and a one-page prep card; fifteen common objections with answers; the decision record and five follow-up emails; and a fully worked example for a fictional cidery. Claude never invents a client quote, a name, a cost or a result. It leaves a marked gap and asks you. Every route gets the same slides and the same time, and every comp is labelled. The US rules it quotes on recording meetings, who owns AI-made images, stock comps and attachment sizes were checked on 17 October 2026, each with its source.
Claude cannot sit in the meeting or send the email. It works from what you give it before and after: the brief, the deck as a PDF, and your notes or a transcript. With code execution switched on it counts words to time the talk, checks contrast from your colour codes, and makes a prep card as a PDF or speaker notes as a Word file. It does not design the slides; the Pitch deck design skill builds them from the same slide list. Its notes on recordings and image rights are pointers, not legal advice. Rehearse the talk track out loud once with a timer, and rewrite any line you would never say.
Claude skill · version 1.0
Concept presentation
Checking your access.
In the download · 7 files
- SKILL.mdThe method Claude follows: meeting brief, storyline and order, talk track, objections, the recommendation and the ask, and the follow-up, one stage at a time.
- README.mdHow to install it in claude.ai or Claude Code, how to start, and the licence.
- references/meeting-brief-and-storyline.mdThe meeting brief, mapping the room, the decision sentence, time budgets for 30 to 90 minute meetings, how to order the routes, the reveal, and what changes by format and kind of work.
- references/talk-track.mdWriting for the ear, the opening two minutes, the seven beats of a route, word budgets, lines to cut, labelling comps, rehearsal, and the one-page prep card.
- references/objections-and-the-ask.mdThe five worries under most objections, the four moves in the room, fifteen objections with answers, the recommendation, the decision menu, merging routes, and what to do when no decision comes.
- references/follow-up-and-rules.mdThe decision record, feedback list, scope check and five follow-up emails, plus US rules on recording meetings, AI image ownership, stock comps, attachment sizes and contrast, checked 17 October 2026.
Install it and begin
01Install it in Claude CodeTerminal mkdir -p ~/.claude/skillsunzip ~/Downloads/concept-presentation.zip -d ~/.claude/skills/# Start it with /concept-presentation. If this is your first skill, type /reload-skills once.On claude.ai there is nothing to unzip: upload the zip as it is. Every step is on Install and use a Claude skill.
02Your first message to ClaudeText Use the concept presentation skill. I'm presenting [NUMBER] routes for [CLIENT OR PROJECT] on [DATE], for [MINUTES] minutes, [IN PERSON OR ON VIDEO]. [WHO DECIDES] decides and [WHO CAN BLOCK] can block. I'd recommend [ROUTE NAME] because [ONE REASON]. Here are the brief and the deck: [ATTACH BOTH AS PDF]. Start with the meeting brief and tell me what is missing.Attach the creative brief and your deck exported as a PDF. Kickoff notes, the number of rounds in your contract and a past email in your own voice make the talk track sharper.
Common mistakes
Where concept meetings go wrong
Instead ofPutting the first route on screen within a minute of sitting down.
Do thisPlay the brief back in the client's words, ask "Is that still right?", and agree three criteria before the first reveal, so the room judges the work against the brief rather than taste.
Instead ofAsking "What do you think?" after each route.
Do thisAsk the room to hold reactions until every route is shown. Then ask for the decision first and reactions on the chosen route second.
Instead ofAdding a weak route to make the favourite look good, or giving the favourite more slides and polish.
Do thisShow only routes you would be glad to make, each with the same slide count, finish and time. Make your case openly in the recommendation.
Instead ofEnding with "Thoughts?" or "Any questions?"
Do thisEnd with a closed ask, "Can we agree today to take this route into round two?", then stop talking. Read the decision back before anyone leaves.
Instead ofAgreeing to changes in the room to keep the mood up.
Do thisRestate the worry, ask one question, answer against the criteria, and say "Let us take that away" for anything bigger. Name the cost of extras in the follow-up.
Instead ofSending the deck ahead so the client can have a look.
Do thisPresent first and send the PDF afterwards. If you must send it ahead, send a narrated version with the brief and criteria at the front.
Instead ofLetting AI-made or stock comps pass as finished work.
Do thisLabel every comp on the slide, say once in the opening what the finals will be, and never show a generated person or product as real.
Instead ofA follow-up three days later that retells the whole meeting.
Do thisA same-day email under 250 words: the decision as agreed, the numbered feedback, what is out of scope, and a reply-by date.
What to do it with
- ClaudeFree tier, paid above it
A language model that writes, edits, reads long documents and runs tools, including agents that work inside a codebase.
Bad at It is agreeable by default, so it will improve a bad idea instead of telling you it is bad. Ask it to argue against you and the quality of the answer changes.
- Claude CodeSubscription
An agent that reads a whole repository, edits files, runs the tests and explains what it changed.
Bad at It is fast enough to make a large mistake quickly. Work on a branch, read the diff, and never let it push. Watch the starting mode: on Pro, Max and Team plans it opens in auto mode, which Anthropic's own list says may read a .env file and send the key in it to the API that key belongs to. Switch it off.
Why it matters
Concept rounds are often lost in the meeting itself. The work goes up before the brief is agreed, the room judges on taste, someone asks for reactions after the first route, and everyone leaves with edits to three routes and no decision. This skill makes Claude agree the criteria before the first reveal, give every route the same time, prepare answers to the likely pushback, and end on one closed question that gets written down.
- Type
- technique
- Period
- ongoing