Install
$ agentstack add skill-dennisle-lts-claude-skills-exec-pitch-generator ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Executive Pitch Generator
Produces two persuasion-focused documents in Markdown format:
- Investment Proposal (
InvestmentProposal_.md) — 1-2 page document making the case for funding, structured for easy copy-paste into Word or Google Docs - Pitch Deck (
PitchDeck_.md) — 6-8 slide content structured with clear page numbers, ready to copy-paste into PowerPoint, Google Slides, or Keynote slide by slide
Both files are plain Markdown — no dependencies, works in Claude.ai and Claude Code equally.
Context: Why This Skill Exists
This skill is designed for bottom-up project initiation — where the tech or ops team identifies an opportunity or problem and must pitch upward to get approval and funding, BEFORE any budget or deadline has been committed. The documents are deliberately persuasive, not just informational.
This is the opposite of the traditional flow where executives approve a project first, then ask teams to document it.
Workflow
Phase 1 — Source Document Discovery
- Ask the user for the folder path containing their SDLC documents (BRD, PRD, TDD, etc.) or any other project information they have.
- Read all files in the folder:
``bash ls -la /path/to/folder cat /path/to/folder/*.md ``
- Extract and map the following key information needed for the pitch:
- Problem — what pain, inefficiency, or risk exists today
- Proposed solution — what the project will build or change
- Business benefits — efficiency gains, cost savings, risk reduction, revenue impact
- Investment required — estimated cost, time, people, tools
- Timeline — how long it will take, key milestones
- Risks of inaction — what happens if the project is NOT approved
- Success metrics — how results will be measured
- Stakeholders — who benefits, who sponsors
Phase 2 — Gap-Filling Questions
After reading the source documents, identify missing information and ask only what is needed. Focus on:
- Any estimated numbers not in the docs (cost savings, time saved, headcount affected)
- The main audience — who specifically will receive this pitch (CEO, CTO, Board, etc.)
- The preferred tone — conservative/formal vs bold/visionary
- Any constraints — budget ceiling, preferred timeline, political sensitivities
Keep questions to a maximum of 8. Never ask for information already in the source files.
Phase 3 — Generate the Investment Proposal
Read references/investment-proposal-template.md before generating.
Key principles:
- Maximum 2 pages worth of content — executives will not read more
- Lead with the problem, not the solution
- Every section must answer "so what?" from a business perspective
- Use plain language — no technical jargon
- End with a single, unambiguous call-to-action
- Use Markdown tables for cost/benefit — executives scan, not read
Formatting rules for easy copy-paste into Word:
- Use
#for the document title - Use
##for each section heading - Use
>blockquotes for the call-to-action or key emphasis lines - Use tables for cost/benefit comparisons
- Use
-bullet lists for benefits and risks - Add a clear
---divider between each section - Add `` at the bottom
Save as: InvestmentProposal_.md
Phase 4 — Generate the Pitch Deck
Read references/pitch-deck-template.md before generating.
Key principles:
- 6-8 slides maximum — respect their time
- One message per slide
- Narrative arc: Pain → Possibility → Proposal → Payoff → Ask
- The final slide is THE ASK — make it impossible to misunderstand
- Write slide content as it should appear on the slide — concise, punchy, not paragraphs
Formatting rules for easy copy-paste into PowerPoint slide by slide:
- Start every slide with a divider and bold page label:
`` --- **[ PAGE 1 of 8 ]** ``
- Follow immediately with the slide title using
# - Use
**Label:**for any callout stats or key points - Use short
-bullet points (max 8 words each) - Use a
>blockquote for the single most important line on each slide (the headline message) - Use a table where a side-by-side comparison appears
- End every slide section with a
---divider - Add a `` comment after each slide for optional speaker notes
- Add `` at the bottom
Save as: PitchDeck_.md
Phase 5 — Present and Offer Refinement
- Save both files to
/mnt/user-data/outputs/(Claude.ai) or current working directory (Claude Code) - Present both files to the user
- Add a short note explaining:
- The Investment Proposal is ready to copy-paste section by section into Word or Google Docs
- The Pitch Deck is organised by page number — copy each page block into a new slide
- Ask: "Would you like to adjust the tone, rework any specific slide, or add more detail to any section?"
Tone & Language Guide
| Audience | Tone | Language | |---|---|---| | CEO / Board | Bold, concise, ROI-focused | Business outcomes only | | CTO / VP Eng | Balanced — business + technical | Light technical context OK | | CFO | Conservative, number-heavy | Cost/benefit, risk framing | | Mixed leadership | Outcome-first, accessible | Zero jargon |
When in doubt, write for the least technical person in the room.
Reference Files
references/investment-proposal-template.md— section-by-section structure and writing guide for the proposalreferences/pitch-deck-template.md— slide-by-slide structure, content guide, and copy tips for the deck
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dennisle-lts
- Source: dennisle-lts/claude_skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.