Skip to main content
skill CX Codex

executive-deck — Claude Code skill: presentations and setup

executive-deck is a Claude Code skill that builds executive presentations with a conclusion in each slide title. It activates for management updates, board decks, business reviews, and documents turned into slides.

Apache-2.0 ★ 12,746 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add genspark-ai/genoffice --skill executive-deck -a claude-code
Open on GitHub

What executive-deck does

executive-deck shapes a request or source document into an answer-first presentation. It identifies the main conclusion and three supporting points, then gives each point its own slide. Recommendations become numbered actions with owners and dates when the source provides them.

A business review defaults to 8–12 slides; a status update to 5–7. Content slides include speaker notes, and each slide keeps to five short bullets at most. Figures and facts come from attached or referenced files. When a needed number is missing from a source, the skill calls for that gap to appear on the slide instead of filling it with an estimate.

What it helps with

  • build a business review around its main conclusion
  • turn a document into a board presentation
  • organize a status update into claims and supporting evidence
  • present recommendations as actions with owners

Example prompts for the agent

  • Turn the attached report into a presentation for the board.
  • Make an executive deck from this document, with the main answer up front.
  • Create a status update and add speaker notes to each content slide.

How to install executive-deck

1Skills CLI (Vercel)

npx skills add genspark-ai/genoffice --skill executive-deck -a claude-code

2Manually: put the files in place

~/.claude/skills/executive-deck/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/executive-deck/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about executive-deck

How do I install executive-deck in Claude Code?

Run npx skills add genspark-ai/genoffice --skill executive-deck -a claude-code. The skill file is at ~/.claude/skills/executive-deck/SKILL.md.

What does executive-deck do?

It creates presentations whose slide titles form an argument, with slide content serving as evidence. It also sets rules for recommendations, charts, and speaker notes.

How does executive-deck turn a document into slides?

It extracts the conclusion and three strongest supporting points first; remaining material goes into an appendix or is dropped. Figures should retain the source document’s precision.

Source text

SKILL.md · Apache-2.0
---
name: executive-deck
description: Build a reporting or executive presentation where every slide title states a conclusion and the deck follows a pyramid, answer-first structure. Use when the user asks for a management update, board deck, status report, business review or a presentation that argues for a decision, including turning a document into slides.
category: business
metadata:
  version: 1.0.0
---

# Executive deck

A reporting deck is read, not performed. The reader should get the whole
argument from the slide titles alone; the body of each slide is the proof.

## Before building

1. Decide the single answer the deck gives. Write it as one sentence. That
   sentence is the title of slide 2 and the backbone of the whole deck.
2. Read every attached or referenced file fully. Figures, names and dates
   come only from there. If the source lacks a number the story needs, say
   so on the slide rather than estimating.
3. Fix the length from the request: default 8-12 slides for a business
   review, 5-7 for a status update. Fewer slides with a clear line beat
   more slides with everything.

## Structure (pyramid, answer first)

1. **Title slide** — Deck title that names the decision or question, date,
   presenter or team.
2. **Answer slide** — The one-sentence conclusion as the title; three
   supporting points as the body, each one line. Nothing else.
3. **One slide per supporting point** — Title = the point as a full
   sentence with a verb ("Churn rose because onboarding slipped in Q2", not
   "Churn"). Body = the evidence: one chart or one table or 3-5 bullets,
   never all three. Order the slides in the same order as the three points
   on the answer slide.
4. **Recommendation / next steps** — Numbered actions, each with an owner
   and a date where the source allows. Title states what is being asked
   ("Approve the Q4 onboarding rebuild").
5. **Risks or open questions** — Only if real. Short.
6. **Appendix** — Detail tables, methodology, backup charts. Nothing in the
   appendix may be needed to follow the main story.

## Slide rules

- Every title is a complete sentence stating a conclusion. If a title could
  sit on any deck ("Overview", "Results"), rewrite it.
- One message per slide. If a slide needs an "and", split it.
- Bullets: at most 5, each at most 12 words, parallel grammar, no
  sub-bullets. A bullet that needs a second line is a sentence for the
  notes, not a bullet.
- Numbers on slides carry unit and period. The source goes in a small
  footer line on that slide, not in a bullet.
- Charts: one series highlighted, the rest muted; title the chart with its
  takeaway, not its subject. Prefer bar for comparison, line for trend; no
  pie with more than 4 slices.
- Speaker notes hold the narration and the caveats, in full sentences.
  Write them for every content slide.
- Keep the deck's language consistent with the request and sources.

## Turning a document into a deck

- Extract the document's conclusion first, then its three strongest
  supports; everything else is appendix or dropped.
- Never paste paragraphs onto slides. Each paragraph becomes at most one
  bullet, or a figure.
- Preserve the document's figures exactly; do not round further than the
  source does.

## Design

Stay inside the app's default theme and layouts. Do not set custom fonts,
colors or sizes unless the user asks for a specific look. Consistency across
slides matters more than any single slide looking rich.

## Before you say done

- Read only the titles, top to bottom: they must form a coherent argument
  that ends in the recommendation.
- The three points on the answer slide match the following slide titles in
  wording and order.
- No slide has more than one chart/table, or more than 5 bullets.
- Every content slide has notes.
- Tell the user the storyline in three lines and list anything you could
  not source.

© genspark-ai · Apache-2.0 · genspark-ai/genoffice

Similar skills

All skills for Office documents →

From the same set65

The whole set →
proposal-writer proposal-writer turns a requirement or a rough idea into a Word proposal with goals, a recommended option, milestones, budget and risks. CX Codex +1 ★ 12,746repo stars financial-statement-analysis financial-statement-analysis analyses balance sheets, income statements, and cash flows, computes four financial ratio groups, and writes an interpretation report in Word. CX Codex +1 ★ 12,746repo stars study-plan study-plan builds a weekly and daily learning schedule from a goal and available time, then delivers it as an Excel workbook. Useful for exam prep and skill learning. CX Codex +1 ★ 12,746repo stars product-launch product-launch turns notes about a new product or feature into a launch plan: timeline, channel checklist, press release and FAQ, delivered as a Word document. CX Codex +1 ★ 12,746repo stars performance-review The performance-review skill turns period goals and results into an evidence-based self-assessment or manager review in a Word document. Use it for goal retrospectives. CX Codex +1 ★ 12,746repo stars data-cleaning data-cleaning audits a messy spreadsheet, agrees cleaning rules with you, then returns an Excel workbook with the clean table, a row-by-row log and the duplicates it would not merge on its own. CX Codex +1 ★ 12,746repo stars onboarding-plan onboarding-plan generates structured 30/60/90-day onboarding spreadsheets with milestones, resources, and manager checkpoints in Excel. CX Codex +1 ★ 12,746repo stars sales-forecast sales-forecast turns historical sales data into an Excel forecast with scenarios and sensitivity analysis. Use it to examine seasonality or plan sales for a chosen horizon. CX Codex +1 ★ 12,746repo stars

Project sponsors

Companies that keep this analytics open