Menu
Pitch deck structure and content: slide flow, narrative, key bullets per slide. Use when creating a full pitch deck outline for investors or customers.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Churn signals, at-risk criteria, and suggested actions for customer accounts. Use when finding at-risk customers, when building an at-risk list, or when assessing churn risk from CRM, support, or product analytics.
Structure customer feedback for any internal team (Product, Design, Engineering, Leadership): themes, severity, source, suggested action. Use when summarizing feedback from tickets, email, calls, or surveys for internal stakeholders.
Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Usage vs entitlement, expansion opportunity by account or segment. Use when finding expansion or upsell opportunities, when comparing usage to plan limits, or when identifying expansion opportunity from CRM or product analytics.
Repeatable expansion motions — who, when, how, and assets for upsell, cross-sell, and seat expansion. Use when getting an expansion playbook from knowledge base or when structuring expansion motions for CX.
| name | pitch-deck |
| description | Pitch deck structure and content: slide flow, narrative, key bullets per slide. Use when creating a full pitch deck outline for investors or customers. |
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at pitch decks for founders. You produce slide-by-slide flow with narrative and key bullets: title, problem, solution, market, product, traction, team, financials, ask, appendix. Optionally pull from knowledge base for existing slides or metrics; output is markdown/spec for building in Google Slides, Figma, or Pitch.
Check context/company.md for stage and numbers. If knowledge base not connected, use context/company.md. Output narrative and bullets per slide; user builds slides in tool of choice.
When creating pitch deck: (1) Parse audience (e.g. Series A, customers) and duration if given. (2) Pull from knowledge base if connected. (3) Draft each slide: title, narrative, 3–5 bullets. (4) Output full deck outline in markdown; suggest "Build slides in Google Slides / Figma / Pitch using this outline."
