From startup-skills
(startup-skills) Use when the founder needs a polished external-facing deliverable. Fires on "create a pitch deck," "build a landing page," "draft a one-pager," "investor email," or "demo day deck." All artifacts are pulled from the current state document. Refuses to produce a pitch deck pre-signal. Flags every thin section so the founder knows what is substantiated vs filled-in.
How this skill is triggered — by the user, by Claude, or both
Slash command
/startup-skills:artifact-builderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produces polished external-facing deliverables — pitch decks, landing pages, one-pagers, investor emails, demo day scripts — pulled from the current state document. Refuses to produce a pitch deck pre-signal. Marks thin sections so the founder knows what's substantiated vs filled-in.
Produces polished external-facing deliverables — pitch decks, landing pages, one-pagers, investor emails, demo day scripts — pulled from the current state document. Refuses to produce a pitch deck pre-signal. Marks thin sections so the founder knows what's substantiated vs filled-in.
Only on explicit request. The system never auto-generates artifacts; the founder must ask.
${CLAUDE_PLUGIN_ROOT}/references/state-document-protocol.md${CLAUDE_PLUGIN_ROOT}/references/pitch-deck-structure.md — 10–12 slide YC format; what never to include.${CLAUDE_PLUGIN_ROOT}/references/landing-page-patterns.md — Fake Door / signup page anatomy.${CLAUDE_PLUGIN_ROOT}/references/one-pager-structure.md — async one-page format.${CLAUDE_PLUGIN_ROOT}/references/email-templates.md — outreach patterns including investor email shapes.${CLAUDE_PLUGIN_ROOT}/references/case-studies.md — for anchor examples.${CLAUDE_PLUGIN_ROOT}/references/bias-sentinel.md — pitch-deck-as-fiction, false traction claims, vanity metrics.Read STARTUP-STATE.md thoroughly — this skill consumes the state to produce artifacts. Update Session Log noting the artifact produced: - [YYYY-MM-DD] artifact-builder — produced <type> for <purpose>, marked <N> thin sections. Do NOT write to other sections; this skill outputs, it does not change strategy.
Read state. All sections.
Detect requested artifact type. Confirm with the user if ambiguous: "Pitch deck, landing page, one-pager, investor email, or something else?"
Routing per request type:
Pitch deck:
discovery-coach to lift the evidence quality. I can produce a one-pager instead — that's appropriate at this stage. Or I can produce a deck flagged with thin-section warnings, if you understand the trade-off."${CLAUDE_PLUGIN_ROOT}/references/pitch-deck-structure.md. If a pptx skill (Anthropic's official PowerPoint skill) is available in this environment, use it for native pptx output. Otherwise produce as markdown the user can paste into Google Slides or Keynote.Landing page: build as React or static HTML per ${CLAUDE_PLUGIN_ROOT}/references/landing-page-patterns.md. Single-page, clear value prop, single CTA. Mobile-responsive. Tailwind for styling. The headline uses customer vocabulary from market-intel; the value prop is the One-Liner from state.
One-pager: markdown per ${CLAUDE_PLUGIN_ROOT}/references/one-pager-structure.md. Problem, solution, traction (or validation-to-date for pre-signal), ask, contact. Single page, ~400–500 words.
Investor email / cold email: draft to a specific named recipient using ${CLAUDE_PLUGIN_ROOT}/references/email-templates.md. Customize the credibility line and value prop. 50–100 words, plain text, single CTA. Refuse generic blasts — investor emails specifically must be personalized per recipient.
Demo day script: 2-minute spoken script with slide cues. Pulls from the pitch deck content; reformatted for spoken delivery (no full sentences in slides; full sentences in script). Practice runtime ≤120 seconds.
Interview script (if requested standalone): route to discovery-coach PREPARE mode — that's the canonical source.
Outreach email batch (if requested standalone): route to outreach-engine — that's the canonical source.
MVP spec (if requested standalone): route to mvp-architect.
Logo / brand: route to Claude Design if available in the environment, otherwise produce a brand brief markdown the user can take to a designer (positioning, tone, color directions, typography directions, what to avoid).
Mark thin sections explicitly. Wherever the state document is sparse, insert a callout in the artifact:
This is non-negotiable. Founders will use the artifact externally; the markings keep them honest about what is substantiated vs aspirational.
Apply YC's pitch deck conventions when producing decks:
Bias sentinel pass. Especially:
Produce the artifact. As a markdown artifact in claude.ai, or a file in Claude Code. For pitch decks specifically: if pptx skill is available, use it for native PowerPoint; otherwise produce markdown.
Log the artifact in STARTUP-STATE.md Session Log: what type, what purpose, what thin sections were flagged.
Whichever skill the founder was in before invoking this one. Artifact-builder is a sidecar; it doesn't drive the journey forward by itself. If a pitch deck was produced and the founder is preparing to raise, recommend a signal-audit first to ensure the traction story is honest.
Per ${CLAUDE_PLUGIN_ROOT}/references/tone-and-stance.md. Direct on refusals (pre-signal pitch decks, vanity metrics). When marking thin sections, do not soften — the marks are the value. A polished artifact with unmarked thin sections is worse than a rougher artifact that's honest about what's missing.
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub quinnhall07/startup-skills --plugin startup-skills