Skill

public-onepager

Generate a public-facing one-pager PDF for a business idea — designed for sharing with potential cofounders, advisors, or early customers. Strips internal-only analysis (council dissent, raw assumptions, kill criteria) and presents a clean, persuasive summary. Use when the user wants a shareable artifact for an idea.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin business-idea-eval

Tool Access

This skill uses the workspace's default tool permissions.

Preview

External-facing single-page summary. Different audience, different rules: this is marketing, not analysis.

SKILL.md

Similar Skills

skill-lookup

159.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

next-compile

139.2k

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

1 file

vercel-next-js-2

angular-new-app

100.1k

Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.

angular-angular-1

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

public-onepager

Public One-Pager

External-facing single-page summary. Different audience, different rules: this is marketing, not analysis.

Steps

Read the idea, the latest synthesis, and any explicit "elevator pitch" / "executive summary" variants from versions/.

Compose the one-pager content:

Headline — one sentence that an outsider can repeat after reading once
Problem — three sentences max, framed in customer language not industry jargon
Solution — what we're building and the wedge
Why now — the structural shift that makes this the right time
Market — pulled from tam-analysis.md if present (round numbers, no false precision)
Team — one paragraph drawn from user-context.md, calibrated for outside reader
Traction or next milestone — what's been validated, what's next
Ask — what is the user asking the reader for (advice / introductions / capital / pilot customer)

Strip aggressively — no lens labels, no internal council debate, no "we don't know yet" hedging in copy (those go into internal-pdf not here).

Render via Typst. Prefer typst-document-generator:public-doc if installed; otherwise use this plugin's templates/public/onepager.typ.

Output to <workspace_path>/ideas/<slug>/exports/onepager-<YYYYMMDD>.pdf.

Notes

The user's "ask" is critical and often missing. Push for it explicitly before generating.

Show the user the markdown copy before compiling — the words matter more than the layout.

Public outputs deserve a different visual identity than internal ones. Don't reuse the internal template.

Surface social-impact-lens findings only if they support the pitch. If they're problematic, that's a real consideration but not for the one-pager.

Public One-Pager

External-facing single-page summary. Different audience, different rules: this is marketing, not analysis.

Steps

Read the idea, the latest synthesis, and any explicit "elevator pitch" / "executive summary" variants from versions/.
Compose the one-pager content:
- Headline — one sentence that an outsider can repeat after reading once
- Problem — three sentences max, framed in customer language not industry jargon
- Solution — what we're building and the wedge
- Why now — the structural shift that makes this the right time
- Market — pulled from tam-analysis.md if present (round numbers, no false precision)
- Team — one paragraph drawn from user-context.md, calibrated for outside reader
- Traction or next milestone — what's been validated, what's next
- Ask — what is the user asking the reader for (advice / introductions / capital / pilot customer)
Strip aggressively — no lens labels, no internal council debate, no "we don't know yet" hedging in copy (those go into internal-pdf not here).
Render via Typst. Prefer typst-document-generator:public-doc if installed; otherwise use this plugin's templates/public/onepager.typ.
Output to <workspace_path>/ideas/<slug>/exports/onepager-<YYYYMMDD>.pdf.

Notes

The user's "ask" is critical and often missing. Push for it explicitly before generating.
Show the user the markdown copy before compiling — the words matter more than the layout.
Public outputs deserve a different visual identity than internal ones. Don't reuse the internal template.
Surface social-impact-lens findings only if they support the pitch. If they're problematic, that's a real consideration but not for the one-pager.