--- name: one-pager description: Personalized one-pager / leave-behind generator rendered as self-contained HTML. Use when user says "one-pager for [company]", "leave-behind", "follow-up doc", "demo summary", or asks for a concise customer-facing document. --- # /octave:one-pager - Personalized One-Pager Builder Generate personalized, self-contained HTML one-pager documents (leave-behinds) powered by your Octave GTM knowledge base. Unlike generic templates, this skill enriches every section with real account intelligence -- company signals, persona pain points, playbook messaging, and proof points -- to create a document that feels written specifically for the recipient. One-pagers are single scrollable pages designed to be sent after a demo, meeting, or call. They summarize why your product is a fit for this specific account. Think of it as the document you email or print, not present. ## Usage ``` /octave:one-pager [--for ] [--style ] ``` ## Examples ``` /octave:one-pager acme.com # General one-pager for Acme /octave:one-pager jane@acme.com --for demo-followup # Post-demo leave-behind /octave:one-pager acme.com --for discovery # Post-discovery summary /octave:one-pager "enterprise healthcare segment" # Segment-level one-pager /octave:one-pager acme.com --for renewal --style soft-light # Renewal doc with specific style /octave:one-pager jane@acme.com --for event-followup # Post-conference/event follow-up ``` ## Occasions | Occasion | Output Focus | |----------|--------------| | `demo-followup` | Recap what was shown, reinforce value, clear next steps | | `discovery` | Summarize pain points heard, position solution fit | | `intro` | General company intro tailored to the account (default) | | `event-followup` | Post-conference/event personalized summary | | `renewal` | Reinforce value delivered, expansion opportunities | ## Instructions When the user runs `/octave:one-pager`: ### Step 1: Understand the Context If not provided via flags, ask the user interactively: **Target -- "Who is this for?"** ``` Who is this one-pager for? Provide any of the following: - Company domain (e.g., acme.com) - Person email (e.g., jane@acme.com) - Segment description (e.g., "enterprise healthcare") Target: ``` **Occasion -- "What's the context?"** ``` What's the occasion for this one-pager? 1. Demo follow-up - Sent after a product demo 2. Discovery follow-up - Sent after a discovery call 3. General intro - First touch or general positioning 4. Event follow-up - Sent after a conference/event meeting 5. Renewal - Reinforcing value for an existing customer Your choice: ``` **Tone -- "What tone should it strike?"** ``` What tone fits best? 1. Formal executive - Polished, concise, boardroom-ready 2. Conversational - Warm, approachable, peer-to-peer 3. Technical - Data-driven, detailed, practitioner-focused Your choice: ``` ### Step 2: Octave Context Gathering Based on target, occasion, and tone, use Octave MCP tools to build rich context for the one-pager. **Always tell the user what you're researching and why.** **Call as many tools as needed to build a complete picture.** The best one-pagers come from layering multiple sources -- company enrichment + playbook messaging + proof points + conversation intel all combine to create a document that feels genuinely personalized. Don't stop at one tool when three would give you a stronger narrative. That said, not every tool applies to every one-pager. Use your judgment about which are relevant to *this specific* situation. The tables below show what's available -- pick the combination that gives you the richest context for the occasion and target. See [tool-reference.md](references/tool-reference.md) for list-vs-search guidance, follow-up grounding tools, and the tool reference tables for account-specific and segment-level one-pagers. **Output of this step:** Present a content outline to the user for approval. See [outline-template.md](references/outline-template.md) for the outline template. **Wait for user approval before proceeding.** ### Step 3: Style Selection One-pagers use the same 12 style presets and brand extraction system as the deck skill. See [style-presets.md](../deck/references/style-presets.md) for full CSS variable definitions. Ask the user: ``` How would you like to style the one-pager? 1. Pick from presets — 12 styles from dark executive to light minimal 2. Use my brand — extract from my website or provide brand assets 3. Auto-pick — I'll choose based on the occasion and tone 4. Surprise me Your choice: ``` **Option 1: Preset Picker** -- Show the same preset table from the deck skill (see `/octave:deck` Step 4, Option 2). **Option 2: Brand Extraction** -- Follow the same brand discovery flow from the deck skill (see `/octave:deck` Step 3). Supports browser-use tier, WebFetch tier, and manual fallback. Confirm brand config with user before proceeding. **Option 3: Auto-Pick** -- Map occasion + tone to recommended presets: | Occasion + Tone | Recommended Preset | |------------------|--------------------| | Demo follow-up, formal | `midnight-pro` | | Demo follow-up, conversational | `soft-light` | | Discovery, formal | `executive-dark` | | Discovery, conversational | `swiss-modern` | | Intro, formal | `midnight-pro` | | Intro, conversational | `soft-light` | | Intro, technical | `electric-studio` | | Event follow-up | `aurora-gradient` | | Renewal, formal | `executive-dark` | | Renewal, conversational | `soft-light` | Tell the user what you picked and why. Let them override. ### Step 4: Generate HTML Build a single, self-contained HTML file. **No external dependencies** except Google Fonts. This is a single scrollable document -- NOT slides. #### Output Directory Every one-pager gets its own folder under `.octave-one-pagers/`: ``` .octave-one-pagers/ └── -/ └── .html ``` Example: `/octave:one-pager acme.com` produces `.octave-one-pagers/acme-one-pager-2026-02-11/acme-one-pager.html` The entire `.octave-one-pagers/` directory is in `.gitignore` -- nothing here gets committed. #### HTML Architecture See [html-architecture.md](references/html-architecture.md) for the HTML/CSS scaffold and key differences from the deck skill's HTML. #### Document Sections See [document-sections.md](references/document-sections.md) for per-section HTML templates (Header, The Challenge, Our Approach, Key Differentiators, Proof Points, Next Steps). #### Content Density Rules Keep it tight. A one-pager should be scannable in under 2 minutes: | Section | Max Content | |---------|------------| | Header | Company name + title + date + "Prepared for" | | The Challenge | 2-3 sentences max | | Our Approach | 3-4 value props, each 1-2 sentences | | Key Differentiators | 3 cards max, each heading + 1-2 sentences | | Proof Points | 2-3 metrics or quotes | | Next Steps | 1 CTA + contact info | If content exceeds these limits, prioritize ruthlessly. The one-pager is a teaser, not a whitepaper. ### Step 5: Delivery After generating the HTML file: 1. **Open the one-pager** in the default browser 2. **Present a summary:** ``` ONE-PAGER READY ================ Folder: .octave-one-pagers/-/ File: .octave-one-pagers/-/.html Style: [Preset name or "Custom Brand"] Size: [file size] Viewing: - Open in any browser -- single scrollable page - Print-friendly -- Cmd+P / Ctrl+P for clean printout - Email as attachment or save as PDF Customization tips: - Colors: Edit the :root CSS variables at the top of the file - Content: Each
is one block - Fonts: Change the Google Fonts and font-family values - Layout: Adjust max-width in .page for wider/narrower output --- Want me to: 1. Adjust content or messaging 2. Change the style/colors 3. Export as PDF (print dialog) 4. Create a version for a different contact at the same company 5. Create a full presentation deck for this account (/octave:deck) 6. Done ``` ## MCP Tools Used ### Research & Enrichment - `enrich_company` - Full company intelligence profile - `enrich_person` - Full person intelligence report - `find_person` - Find contacts at a company by title/role - `qualify_company` - ICP fit scoring for a company - `qualify_person` - ICP fit scoring for a person - `find_company` - Find companies matching criteria ### Library -- Fetching Entities - `list_all_entities` - Quick scan of all entities of a type (minimal fields, no pagination) - `list_entities` - Fetch entities with full data and pagination (proof points, references, personas, etc.) - `get_entity` - Deep dive on one specific entity - `get_playbook` - Retrieve a playbook with full content and value props - `list_value_props` - Value propositions for a specific playbook ### Library -- Searching - `search_knowledge_base` - Semantic search across library entities and resources - `list_resources` - Browse uploaded docs, URLs, and Google Drive files - `search_resources` - Semantic search across uploaded resources ### Intelligence & Signals - `list_findings` - Recent conversation findings and insights - `list_events` - Deal events (won, lost, created, etc.) - `get_event_detail` - Full details for a specific event ### Content Generation - `generate_call_prep` - Synthesized prep brief for accounts - `generate_content` - Generate positioning or messaging content ### Brand & Style - `list_all_entities` (entityType: "brand_voice") - Available brand voices in workspace - `list_writing_styles` - Available writing styles in workspace ## Error Handling **Octave Connection Failed:** > Could not connect to your Octave workspace. > > The one-pager builder can still work without Octave -- you'll provide the content manually, and I'll handle structure, style, and HTML generation. > > To reconnect: check your MCP configuration or run `/octave:workspace status` **Company/Person Not Found:** > I couldn't find detailed intelligence for [target]. > > Options: > 1. Proceed with what we have -- I'll use general positioning from your library > 2. Try a different domain or email > 3. Provide the content manually and I'll build the one-pager **No Matching Playbook:** > No playbook matches this audience profile directly. > > I'll use your general value props and positioning. After the one-pager is built, consider creating a playbook for this segment: `/octave:library create playbook` **No Proof Points Available:** > No proof points found matching this account's industry or segment. > > Options: > 1. Proceed without the proof points section > 2. Use general proof points from your library > 3. Provide customer results manually and I'll format them **No Findings for Follow-Up:** > No conversation findings found for [target] in the recent period. > > This means I'll build the one-pager from enrichment data and library content rather than grounding it in specific past conversations. You can provide meeting notes or context manually if you have them. ## Related Skills - `/octave:deck` - Full presentation deck (when one page isn't enough) - `/octave:research` - Deeper research on the account - `/octave:brief` - Internal account dossier (vs external leave-behind) - `/octave:proposal` - Formal business case - `/octave:microsite` - Personalized web page for ABM