AI agent skill / Agency pitches
Marketing Pitch Deck Skill
I've worked on more than 20 pitches, and some review comments kept coming back. This skill turns a brand website and a brief into a researched, story-led pitch deck, with those lessons built in before handoff.
- My contribution
- Pitch method, slide-writing rules, checks and build
- Timeframe / scope
- Open-source skill for Codex and Claude Code. Published September 2026.
- Current stage
- Passed its package checks and 15 utility tests. Trialled on a fictional launch brief; not yet run through both standalone command-line tools.
At a glance
- Pitches behind the lessons it encodes
- 20+
- Utility tests passed in this release
- 15
- Pitch types it adapts to, from awareness to partnerships
- 6
Where the idea started
After more than 20 pitches, a lot of the feedback stops being a surprise. A header that names the slide instead of making the point. A media plan that doesn't quite add up to the budget. An idea with no real link to the product.
None of it is hard to fix. It's just easy to miss the night before a pitch. So I wrote the lessons down in a form an AI agent can follow.
The approach
The deck starts with the brand's website and the brief, not a template. Research, audience, competitors and the strategic choice come first. Slides come after there's a story to tell.
It adapts to the kind of pitch: awareness, a launch, acquisition, B2B, a portfolio or a partnership. It doesn't force the same chapter list or the same platforms into every deck. Forecasts are labelled as forecasts, and missing data stays missing.
How I built it
The skill is a folder an agent can read: a main workflow, detailed references for research, narrative, media and economics, and templates for the brief, the source ledger and the media plan.
Small Python utilities handle the mechanical checks. One validates the deck plan and the media arithmetic. Another opens the finished PowerPoint file and inspects the real slide order, text and layout bounds.
Revisions are supported too, including visual-only changes that keep approved copy and slide order intact.
Where it stands
This release passed its package checks and 15 utility tests. A trial on a fictional launch brief produced an eight-slide editable deck, a PDF preview and a formula-driven budget model.
It hasn't been run through both standalone Codex and Claude Code command-line tools yet. And a clean check doesn't prove the strategy is good. The workflow still asks a person to review every rendered slide.
What I learned
A lot of what makes a pitch feel sharp can be checked: does each header make a point, does the plan add up, is every number sourced. Handing those checks to a script leaves more time for the part nobody can check, which is the idea.
Tools used
- Python
- Codex
- Claude Code
- PowerPoint
- GitHub Actions