plugins/market-research/skills/generating-slide-deck/SKILL.md
Generate an investor or stakeholder presentation from Phase 5 synthesis; produces a structured slide outline with headlines, talking points, and data citations. Run after `synthesizing-research` (Phase 6).
npx skillsauth add qte77/claude-code-plugins generating-slide-deckInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Target: $ARGUMENTS
Phase 6 of the GTM pipeline. Depends on Phase 5. Generates a structured investor or stakeholder presentation from the synthesized GTM research.
Read config/mode.md before starting:
concise — 8-10 slides, one data point per slide, minimal textdetailed — 12-15 slides, supporting evidence slides, appendix sectionconservative — Data-led narrative, proof-before-vision structureambitious — Vision-first narrative, bold claims with supporting data, moonshot framingresults/phase-5/synthesis.md — Integrated GTM narrative (primary source)config/comments_gtm.md — Audience type, deck length, format preferencesconfig/mode.md — Style and approach settingsAdapt based on audience from config/comments_gtm.md:
config/comments_gtm.md for audience preferenceconfig/validation_criteria.md Phase 6 gatesWrite to results/phase-6/:
slide-deck.md# [Product Name] — [Audience Type] Deck
---
## Slide 1: [Title]
**Headline**: [Insight-driven headline, not a topic label]
Key points:
- [bullet]
- [bullet]
- [bullet]
Speaker notes: [Optional: key talking point]
---
## Slide 2: [Title]
**Headline**: [Insight-driven headline]
[Data point] — Source: [citation]
Key points:
- [bullet]
---
[Continue for all slides]
---
## Appendix (detailed mode only)
### A1: [Supporting Data Slide Title]
[Data table or extended evidence]
config/comments_gtm.md; do not exceed itdevelopment
Verify an external or AI-generated security report against the actual codebase before acting on it. Use when handed a scanner PDF, automated teardown, audit report, or bug-bounty submission — classifies every finding CONFIRMED / OVERSTATED / FALSE-POSITIVE / FABRICATED and salvages the real work items.
development
Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability.
documentation
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
development
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.