presentation-deck – skill Tài liệu & Office cho agent AI

Presentation Deck

What it is: the content of a business presentation - what each slide says, why it is

there, what evidence backs it and what the speaker says while it is on screen.

Overview

Works out the smallest useful deck for the business in front of it, then builds it only

when asked. The default output is a short recommendation, not a slide register. The slide

register - CSV, SQL DDL, JSON Schema, Notion mapping - is produced on request, from one

field list and check field names, nullability and constraints across the requested formats before delivery.

Layer: Layer 6: Engage. Fits: Growth stage. Table code: n/a.

The rule this table exists to enforce: a slide has one job, and the register names that

job. Key Message is a sentence a listener could repeat afterwards, and Bullets is at

most three supporting points - a slide with six bullets and no key message is a document

being read out. Data Source is required for every slide carrying a number, because a

figure with no source is the single most common way a business loses a room.

The second rule: the deck is a derivative of everything else in this pack. The brand

tokens are in design-theme-guide, the proof in gbp-local-seo-intent, the offer in

business-website-setup. A deck built before those exist is a deck of opinions.

When to Use This Skill

• presentation, deck, slides, pitch, pitch deck
• "we have to present to a bank", "investor deck", "client pitch"
• what should our slides say, story structure, narrative
• sales deck, proposal deck, board update, team briefing
• speaker notes, timing, rehearsal
• turning a report into a presentation

Do not use it for: the printed leave-behind (brand-kit-print-collateral), a written

proposal document, a website page, or the brand identity itself

(design-theme-guide, logo-image-design).

How It Works

Use the self-contained intake and validation steps below. Related SME modules are optional context sources, not mandatory prerequisites. Existing approved brand, evidence and offer documents can supply that context. Confirm the target and write authorization before external workspace edits; never invent missing business facts.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "make" / "build" / "we have to present" -> artifacts wanted; go to Step 2.
• "review" / "check" / "does this work" -> a check, not a build.
• "help me structure" / "what should I say" -> a decision question; answer, then offer the

build.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

> Q: Who is this presentation for, and what do you want them to decide or do

> afterwards?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

Skip anything already answered. Ask the rest one at a time, and stop as soon as the

remaining answers would not change the slide list.

• Audience - Who is in the room - customers, a bank, investors, a board, a partner,

the team? / What do they already believe about the business? / How many people, and how

long is the slot?

• Ask - What exactly must happen after the presentation - a decision, a signature, a

payment, an introduction, an internal approval? / What is the one sentence that, if they

remember nothing else, should they remember?

• Evidence - What can be shown - revenue, customers, reviews, photos, a process, a

team, a track record? / Is any of it confidential? / Where does each number come from?

• Constraints - Any template, brand tokens or house format to follow? / Any content

that must not appear? / Is the presenter comfortable with the numbers, or should those

be in an appendix?

• Setup - Who presents, and is there a second presenter? / Will it be in person, on a

call, or recorded? / How much rehearsal time is there?

Never invent an answer. Figures, revenue, growth rates, customer names, dates, market

sizes and outcomes the user has not supplied are Unknown. A business case with invented

projections is worse than no deck.

Step 3 - Hold the internal context

module: presentation-deck
intent: null            # set up | review | report | import
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Audience": null
  "Ask": null
  "Evidence": null
  "Constraints": null
  "Setup": null
requested_outputs: []
confirmed_facts: []
open_questions: []

Step 4 - Recommend the smallest workflow

Build an already requested artifact without asking again. For advice-only requests, give a short recommendation and offer the relevant artifact.

Recommended approach: Ten slides, one job each, and one slide per answer to the

audience's real question rather than one per topic. The opening earns attention with

something true about the customer, the middle is evidence, and the last two are the ask

and the next step. Anything that would only matter to someone who already agrees goes in an

appendix. Numbers carry a source on the slide.

Why this one: Ten slides is what a 15-minute slot actually holds, and a deck that runs

over loses the ask at the end - which is the only part anyone acted on. The reason a

founder's 40-slide deck fails is not length, it is that no single slide changes what the

listener believes.

Workflow: Audience and the ask agreed → Ten jobs listed, one per slide → Evidence

mapped to each job → Numbers sourced or removed → Speaker notes written as spoken

sentences → Tokens and layouts applied → Rehearsed to time → Appendix built → One page of

"if they ask about X" prepared for the five hardest questions

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the

requested artifacts. For machine-readable text, keep prose outside the data; for files,

provide a usable link. Report material validation failures or limitations separately.

**If installed and selected, notion-manual-import can render the

Notion step. Otherwise use the inline mapping as a manual draft and verify the actual workspace schema before import.** When the user selects Notion, hand that step to

@notion-manual-import: it holds the CSV, the property

mapping, the import steps and the verification checklist, and it renders the Field

Reference below instead of defining a table of its own. Do not restate the mapping

here and do not improvise the import steps. Manual CSV and mapping outputs need no

connection. For requested workspace changes, follow the shared contract: verify actual

tool access and the target before writing. A user saying "connected" is not tool evidence.

Never ask for a Notion password or token.

Slide ID,Slide Number,Section,Slide Title,Key Message,Bullets,Visual,Speaker Notes,Data Source,Duration Minutes,Sensitivity,Audience,Template Layout,Brand Token Applied,Version,Status,Owner,Notes
,1,Open,We started from one customer complaint,"Three customers asked the same thing in one month, and we built the service for it","The same request, three times; What we built; Who it is for",One photograph of the real premises,"This is the only slide that needs to be remembered if the rest is forgotten. Say it in a sentence, then stop talking.",Not applicable,1.5,Public,Bank and prospective partner,Title and single image,color.brand.primary on color.surface.page,1.0,Draft,Unknown,Example row - replace every value before use.

-- Engine assumption: PostgreSQL. For another engine use the engine's auto-increment
-- equivalent and keep the rest portable.
CREATE TABLE deck_slide (
  slide_id BIGINT PRIMARY KEY,
  slide_number INTEGER NOT NULL,
  section VARCHAR(100) NOT NULL,
  slide_title VARCHAR(255) NOT NULL,
  key_message TEXT NOT NULL,
  bullets TEXT,
  visual VARCHAR(255) NOT NULL,
  speaker_notes TEXT,
  data_source VARCHAR(255) NOT NULL,
  duration_minutes NUMERIC(4,1),
  sensitivity VARCHAR(50) NOT NULL,
  audience VARCHAR(100) NOT NULL,
  template_layout VARCHAR(100) NOT NULL,
  brand_token_applied VARCHAR(255) NOT NULL,
  version VARCHAR(50) NOT NULL,
  status VARCHAR(50) NOT NULL,
  owner VARCHAR(255),
  notes TEXT,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW(),
  CONSTRAINT deck_slide_number_positive CHECK (slide_number > 0),
  CONSTRAINT deck_slide_duration_non_negative CHECK (duration_minutes IS NULL OR duration_minutes >= 0)
);

CREATE INDEX idx_deck_slide_status ON deck_slide (status);
CREATE INDEX idx_deck_slide_section ON deck_slide (section);
CREATE UNIQUE INDEX idx_deck_slide_number_version ON deck_slide (slide_number, version);

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Presentation Deck",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Slide

… (nội dung đầy đủ có trong gói tải về)