Deck Sales

Organization

FluidForm-ai

deck-sales

Builds 11-slide sales decks for B2B pitch-to-close flows. Trigger phrases, sales deck, customer deck, buyer deck, prospect deck, B2B sales deck. Inherits full pipeline from deck-builder core (Plan, Build, Review, Release, Learn). Sales-specific, every ROI claim sourced, pricing never hidden, Next Steps names specific humans and dates.

Overview

Publisher	FluidForm-ai
Repository	`fluiddocs-deck-builder`
Skill name	`deck-sales`
Stars	33
Forks	2
Bundled files	3
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by FluidForm-ai on GitHub. Read the source before you install it.

Installation

Install the Deck Sales AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/FluidForm-ai/fluiddocs-deck-builder/tree/main/skills/deck-sales
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/FluidForm-ai/fluiddocs-deck-builder.git /tmp/fluiddocs-deck-builder
mkdir -p .claude/skills
cp -r /tmp/fluiddocs-deck-builder/skills/deck-sales .claude/skills/deck-sales

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Deck Sales in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Deck Sales on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Deck Sales is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Deck Sales · a type pack for the `deck-builder` core

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.

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.

What's type-specific (defined in this pack)

References in references/:

content-spine.md, the canonical 11-slide sales spine
visual-components.md, per-slide brand-native patterns
demo-patterns.md, optional screenshot recipes for the How It Works slide

Declarations the brief locks in for sales builds:

deck_type: sales
Target slide count: 11
Catalog directory ($CATALOG): user-specified path (defaults to a decks/ folder next to the brief)
Forbidden class-name leaks: (empty)
Demo: optional, static-screenshot only in OSS

What this type pack inherits from `deck-builder` core

Pipeline: 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 module
deck-builder/references/icon-library.md, inline SVG icon set replacing every emoji
deck-builder/references/brand-methodology.md, source-verify brand tokens protocol, logo safety, nested-subpath rule
deck-builder/references/style-presets.md, named aesthetic presets for Mode B users with no brand

Phase 3 reviewer specs (all in deck-builder/reviewers/):

brand.md, copy.md, layout.md

Phase 5 learnings: deck-builder/references/learnings-log.md (shared; filter by Deck type = sales).

Auto-preview (Phase 2, turn 1)

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.

Output expectations (sales-specific)

Phase 4 deliverable:

The .html file at <CATALOG_DIR>/<Customer>-Deck.html (Mode A) or a user-specified path (Mode B).
The brief alongside it: <Customer>-Brief.md.
The absolute path to the file (or a tool-specific link such as computer://... when the agent runs in an environment that resolves it).
A one-paragraph design and content summary.
The compact audit report (3 reviewers, one line each).

Do not write walls of explanation. The file is the deliverable.

Universal constraints (from core)

The deck-builder/references/build-a-type-pack.md recipe includes three hardened anti-gaming rules enforced by the Layout Reviewer:

No hidden-content filler, zero 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.
No inline justify-content: center on <section class="slide">, use dedicated classes (.s-cover, .s-closing) to avoid overflow-behind-header failures.
Typography scale declared in CSS, first <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).

Hard rules specific to sales decks

Every ROI or value claim has a source (case study, benchmark, or quantified customer result). No unsourced numbers.
Pricing slide is NEVER hidden or skipped. Prospects hate mystery pricing. If pricing is TBD, say so explicitly on the slide.
Next Steps slide names specific humans and dates, not generic "we'll be in touch." Example, "Sarah's next review: Thursday 2pm with our CS lead, Mike."
If competition gets a slide, be honest. No invented weaknesses or strawman comparisons. Credibility beats aggressive positioning.
Proof slide must reference NAMED customers, not "a leading financial services firm." Include customer name, vertical or size, and specific quantified outcomes. If you have no customers, show beta results or respected advisor quotes instead.
Demo slide (optional) ships as a static screenshot. When a sales deck includes a How It Works demo on slide 6, use a high-quality static screenshot of the product with a small "Powered by FluidDocs" attribution mark (FluidDocs logo as inline SVG, ~20px tall, opacity ~0.7, linking to fluiddocs.ai) in the bottom-right. No upsell appears in the deck output.

Maintained by FluidDocs. Source: https://github.com/FluidForm-ai/fluiddocs-deck-builder. MIT licensed.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Deck Sales AI skill do?

Why use Deck Sales on TypingMind?

Because you install it once and use it with any model. Deck Sales is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Deck Sales in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FluidForm-ai/fluiddocs-deck-builder/tree/main/skills/deck-sales. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Deck Sales?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Deck Sales?

As many as you like. As long as a model supports skills, you can use Deck Sales with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Deck Sales AI skill free?

Yes. It is published on GitHub by FluidForm-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Frontend Slides

affaan-m

CommunityPopular

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a…

Plan Canvas

Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or…

Improve Codebase Architecture

mattpocock

CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Deck Sales · a type pack for the deck-builder core

What's type-specific (defined in this pack)

What this type pack inherits from deck-builder core

Auto-preview (Phase 2, turn 1)

Output expectations (sales-specific)

Universal constraints (from core)

Hard rules specific to sales decks

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

Deck Sales · a type pack for the `deck-builder` core

What this type pack inherits from `deck-builder` core