Pitch skills for your agent
Two skills that turn the coding agent you already use into a pitch coach and a deck reviewer for Colosseum. Drop them into your project folder and they read your repo before they ask you anything.
Most teams write the pitch last, in a hurry, in a tool that has never seen their code. These skills run where the code already is.
The pitch coach writes your one-liner and your two-minute script. The deck coach shapes your slide flow, or reviews the deck you've already made, in your own design and branding. Each comes in English and in Turkish.
What you get
Pitch Coach
Your one-liner and your two-minute pitch script, in natural spoken English, timed. On request, a separate script for the demo video.
- Reads your README, docs, landing copy and git history first, so it only asks what it can't find.
- Counts the seconds and cuts instead of asking you to talk faster.
- Keeps pitch and demo apart: up to 2 minutes and up to 3 minutes, two uploads.
Deck Coach
The slide order and the one sentence each slide must carry, or a review of the deck you have, ranked by what to fix first.
- Works with your own design and branding. It never restyles anything.
- Counts the words on every slide and flags what a judge reads on a phone and skips.
- Checks the deck against the red flags judges reject on, and tells you what to leave alone.
The fastest route to a pitch
A reviewed first version takes about ninety minutes. The rest is iteration, and the order matters more than the polish.
- 01The one-liner, first. Five words or fewer, clear enough that ten people picture the same product. Say it to three people and ask what they imagine. If the answers differ, rewrite it.
- 02The story, in six sentences. Who the people are, how they cope today, your product, why it's better, your proof, where it goes. Email it to a few people and ask who the customer is, why current solutions fail, what's better, and what's unclear.
- 03The script, in one sitting. Run the pitch coach. It reads your repo, writes the two-minute English script and counts the seconds. You learn the flow. You don't read it.
- 04The deck, from the script. One slide per group of sentences, a takeaway for every title, eight to thirteen slides. The deck follows the script, not the other way round.
- 05The review, then a human. Run the deck coach, fix the first three things, then share it somewhere people can comment, with one short ask.
- 06Two recordings, not one. The pitch is up to two minutes: one take, no cuts, no music, talking to a person. The demo is up to three minutes and a separate upload: the live product, with your face in a corner.
- 07Iterate early, with one main mentor. Don't wait for the last days. If you have an old deck, start from a blank page. Ask many people to look, but follow one.
Install
The files are plain markdown, so any agent that can read a file can use them. Pick the one you work in.
Claude Code
Project skills live in .claude/skills. Claude uses a skill when your request matches its description, or when you ask for it by name.
for s in colosseum-pitch-coach colosseum-deck-coach; do mkdir -p .claude/skills/$s && curl -fsSL https://tr.superteam.fun/colosseum/skills/$s/SKILL.md -o .claude/skills/$s/SKILL.md; donefor s in colosseum-pitch-coach-tr colosseum-deck-coach-tr; do mkdir -p .claude/skills/$s && curl -fsSL https://tr.superteam.fun/colosseum/skills/$s/SKILL.md -o .claude/skills/$s/SKILL.md; doneTo have them in every project, use ~/.claude/skills instead of .claude/skills. Then ask: “use the colosseum-pitch-coach skill on this repo”.
Cursor
Saved as a project rule. Mention it in a chat, or attach it, when you work on your pitch.
mkdir -p .cursor/rules && curl -fsSL https://tr.superteam.fun/colosseum/skills/colosseum-pitch-coach/SKILL.md -o .cursor/rules/colosseum-pitch-coach.mdc && curl -fsSL https://tr.superteam.fun/colosseum/skills/colosseum-deck-coach/SKILL.md -o .cursor/rules/colosseum-deck-coach.mdcmkdir -p .cursor/rules && curl -fsSL https://tr.superteam.fun/colosseum/skills/colosseum-pitch-coach-tr/SKILL.md -o .cursor/rules/colosseum-pitch-coach-tr.mdc && curl -fsSL https://tr.superteam.fun/colosseum/skills/colosseum-deck-coach-tr/SKILL.md -o .cursor/rules/colosseum-deck-coach-tr.mdcCodex and other agents
Save the files in your repo, then point your agent at them from AGENTS.md.
mkdir -p docs/colosseum && curl -fsSL https://tr.superteam.fun/colosseum/skills/colosseum-pitch-coach/SKILL.md -o docs/colosseum/colosseum-pitch-coach.md && curl -fsSL https://tr.superteam.fun/colosseum/skills/colosseum-deck-coach/SKILL.md -o docs/colosseum/colosseum-deck-coach.mdFor Colosseum pitch work, follow docs/colosseum/colosseum-pitch-coach.md for the script and docs/colosseum/colosseum-deck-coach.md for the deck.ChatGPT, Claude.ai, Gemini
Copy a skill with the button above, and paste it as your first message or into a project's instructions. A chat app can't read your repo, so paste your README and the text of your deck as well.
No install: one URL
If your assistant can open a link, give it this and ask it to follow the pitch coach or the deck coach. All four skills are in the one file.
https://tr.superteam.fun/colosseum/pitch-coach/llms-full.txtWhat they read, and what they won't do
They read
- Your README, docs folder and package manifests.
- Your landing page copy and any deck export: PDF, PPTX, a Google Slides export, images or a markdown outline.
- Your git history: commit count, contributors and cadence, which is the evidence of speed Colosseum scores.
- Any script you've already written.
They won't
- Invent a number, a user, a quote, a partner or a bit of team experience. A gap gets named, not filled.
- Pretend to have opened a file or link they can't read.
- Restyle or rebrand your deck.
- Tell you how to film or edit. They write what to say.
- Promise you a win.
Stuck on this?
Superteam Türkiye reads every message from a Türkiye team.