TypingMindTypingMindThe best frontend for AI
Deck All Hands logo

Deck All Hands

Organization
FluidForm-ai
deck-all-hands

Builds 15-slide all-hands decks for company-wide team meetings with balance of wins and candor. Trigger phrases: all-hands deck, town hall deck, monthly all-hands, company-wide meeting, team meeting deck, all-hands presentation. Type-specific: celebration and candor balance (only-wins hides problems), company-appropriate financials (not board-level detail), Q&A placeholder (live meeting owns Q&A not slides). Inherits 5-phase pipeline from deck-builder core.

Overview

PublisherFluidForm-ai
Repositoryfluiddocs-deck-builder
Skill namedeck-all-hands
Stars
33
Forks
2
Bundled files
3
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • 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 All Hands AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/FluidForm-ai/fluiddocs-deck-builder/tree/main/skills/deck-all-hands
  4. 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.
2

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-all-hands .claude/skills/deck-all-hands
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Deck All Hands 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 All Hands 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 All Hands 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 All-Hands, 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 15-slide all-hands decks for company-wide team meetings. 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 all-hands-specific.

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

References in references/:

  • content-spine.md, the canonical 15-slide all-hands spine
  • visual-components.md, per-slide brand-native patterns
  • demo-patterns.md, light demo recipes for product updates (optional; single moments only)

Declarations the brief locks in for all-hands builds:

  • deck_type: all-hands
  • Target slide count: 15
  • Catalog directory ($CATALOG): declared in the build brief (a folder the user picks for shipped examples)
  • Forbidden class-name leaks: (empty)
  • Demo: optional

What this type pack inherits from deck-builder core

Pipeline: deck-builder/SKILL.md, 5-phase Plan, Build, Review, Release, Learn; 3 reviewer gates (Brand, Copy, Layout).

Phase 1 artifact: deck-builder/references/build-brief-template.md, fill in deck_type: all-hands plus the other all-hands-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 when the user has no brand

Auto-preview (Phase 2, turn 1)

Before writing the full 15-slide deck, generate 3 first-slide HTML previews. 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 deck-builder/references/style-presets.md), save them to a .skill-temp/ folder, 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. The pattern matches the UX bar of a modern deck-builder skill. Show, don't ask.

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 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 = all-hands).

Output expectations (all-hands-specific)

Phase 4 deliverable:

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

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

Hard rules specific to all-hands decks

  • Balance of celebration and candor. An all-hands with only wins signals hiding something. Include at least one learning, challenge, or honest retrospective slide.
  • Financial slides stay appropriate for the audience. Company-wide numbers (ARR, headcount, burn) only, never board-level detail (detailed P&L, cap table, sensitive unit economics).
  • Q&A slide is placeholder. Slide 14 kickstarts the conversation. The live meeting is where Q&A happens, not the deck. Keep questions short and focus on engagement, not exhaustive slide coverage.

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 All Hands AI skill do?

Builds 15-slide all-hands decks for company-wide team meetings with balance of wins and candor. Trigger phrases: all-hands deck, town hall deck, monthly all-hands, company-wide meeting, team meeting deck, all-hands presentation. Type-specific: celebration and candor balance (only-wins hides problems), company-appropriate financials (not board-level detail), Q&A placeholder (live meeting owns Q&A not slides). Inherits 5-phase pipeline from deck-builder core.

Why use Deck All Hands on TypingMind?

Because you install it once and use it with any model. Deck All Hands 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 All Hands in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FluidForm-ai/fluiddocs-deck-builder/tree/main/skills/deck-all-hands. 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 All Hands?

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 All Hands?

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

Is the Deck All Hands 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.

Related AI Skills

View all
mattpocock logo

Teach

mattpocock
CommunityPopular

Teach the user a new skill or concept, within this workspace.

22.3K
264.4K
5 files
View
affaan-m logo

Api Design

affaan-m
CommunityPopular

Patrones de diseño REST API incluyendo nomenclatura de recursos, códigos de estado, paginación, filtrado, respuestas de error, versionado y rate limiting para APIs de producción.

39.1K
261.1K
Instructions
View
affaan-m logo

Accessibility

affaan-m
CommunityPopular

WCAG 2.2 レベル AA 標準を用いてインクルーシブなデジタルプロダクトを設計・実装・監査します。Web 用のセマンティック ARIA および Web・ネイティブプラットフォーム（iOS/Android）のアクセシビリティトレイトを生成するために使用します。

39.1K
261.1K
Instructions
View
NousResearch logo

Archify

NousResearch
OrganizationPopular

Validated interactive HTML diagrams, upstream-maintained.

53.5K
250.4K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇