Stats
Actions
Tags
Builds 11-slide B2B sales decks for pitch-to-close flows. Every ROI claim sourced, pricing never hidden, Next Steps names specific humans and dates. Inherits deck-builder core pipeline.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fluiddocs-deck-builder:deck-salesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Keep your process invisible.** Do not narrate the skill architecture (the "type pack" and "core" split) or announce which files you are reading. Skip preambles like "I'll start by reading...". Gather what you need, then build the deck.
deck-builder coreKeep your process invisible. Do not narrate the skill architecture (the "type pack" and "core" split) or announce which files you are reading. Skip preambles like "I'll start by reading...". Gather what you need, then build the deck.
This skill builds B2B sales decks for prospect conversations: discovery, problem framing, solution fit, proof, pricing, and close. It is a thin type pack that inherits the full pipeline from the deck-builder core skill. Read deck-builder/SKILL.md first for the 5-phase pipeline, 3-reviewer gate, fixed-canvas shell, brand-tokens methodology, and learnings log. This file only declares what's sales-specific.
References in references/:
content-spine.md, the canonical 11-slide sales spinevisual-components.md, per-slide brand-native patternsdemo-patterns.md, optional screenshot recipes for the How It Works slideDeclarations the brief locks in for sales builds:
deck_type: salesTarget slide count: 11Catalog directory ($CATALOG): user-specified path (defaults to a decks/ folder next to the brief)Forbidden class-name leaks: (empty)deck-builder corePipeline: deck-builder/SKILL.md, 5-phase Plan, Build, Review, Release, Learn; 3 reviewer gates.
Phase 1 artifact: deck-builder/references/build-brief-template.md, fill in deck_type: sales plus the other sales-specific fields listed above.
Phase 2 implementation:
deck-builder/references/shell-pattern.md, chrome-free nav shell, 1440x810 canvas scale, inline-edit moduledeck-builder/references/icon-library.md, inline SVG icon set replacing every emojideck-builder/references/brand-methodology.md, source-verify brand tokens protocol, logo safety, nested-subpath ruledeck-builder/references/style-presets.md, named aesthetic presets for Mode B users with no brandPhase 3 reviewer specs (all in deck-builder/reviewers/):
brand.md, copy.md, layout.mdPhase 5 learnings: deck-builder/references/learnings-log.md (shared; filter by Deck type = sales).
Before writing the full deck, auto-generate 3 first-slide HTML previews based on what Phase 1 captured. Do not ask the user how to choose a style. Just generate three distinct visual directions (one safe preset, one bold preset, one wildcard from style-presets.md), save them to a .skill-temp/ folder next to the brief, and open all 3 in the user's browser. Then ask "Which style do you want? A, B, C, or mix elements?" Only after the user picks does the full Phase 2 build begin.
Show, don't ask. This is the UX bar users expect from a modern deck-builder.
Autonomous run exception: for autonomous runs without a user browser to open previews in, skip the visual preview step. Instead, document the preset choice (palette, typography, character) as a code block in the brief and proceed directly to full build. The user can iterate on the preset post-build via the inline-edit module if needed.
Phase 4 deliverable:
.html file at <CATALOG_DIR>/<Customer>-Deck.html (Mode A) or a user-specified path (Mode B).<Customer>-Brief.md.computer://... when the agent runs in an environment that resolves it).Do not write walls of explanation. The file is the deliverable.
The deck-builder/references/build-a-type-pack.md recipe includes three hardened anti-gaming rules enforced by the Layout Reviewer:
display: none, visibility: hidden, opacity: 0, or height: 0 outside base .slide rules. If short of 60K bytes, add real visible content, not hidden blocks.justify-content: center on <section class="slide">, use dedicated classes (.s-cover, .s-closing) to avoid overflow-behind-header failures.<style> line must comment the scale (e.g., /* Typography scale (7 sizes): ... */). The Layout Reviewer enforces all font-sizes match the declared set, max 7 sizes.See content-spine.md § Hard Constraints for the full list (these three are universal across all type packs; sales adds the rules below).
Maintained by FluidDocs. Source: https://github.com/FluidForm-ai/fluiddocs-deck-builder. MIT licensed.
npx claudepluginhub fluidform-ai/fluiddocs-deck-builder --plugin fluiddocs-deck-builderCreates investor pitch decks, partnership presentations, and business proposals via interactive workflow, outputting structured slide content, talking points, and optional visuals. Triggers on 'pitch deck' etc.
Create sales collateral like decks, one-pagers, objection docs, demo scripts, playbooks, and proposal templates.
Creates B2B sales collateral: pitch decks, one-pagers, objection docs, demo scripts, and playbooks. Includes a 10-12 slide framework and checks for existing product-marketing context.