Agent skill

Executive Presentation Builder

by amd in amd/gaia

Turns a source document such as a README or spec into an executive slide deck as one self-contained HTML file that prints to PDF, one slide per page.

MITAuto-check passedDocuments & Office

Install Executive Presentation Builder

skills CLI
$ npx skills add amd/gaia --skill gaia-executive-presentation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install amd/gaia gaia-executive-presentation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/amd/gaia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/gaia-executive-presentation .claude/skills/gaia-executive-presentation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gaia-executive-presentation
GitHub stars
1.6k
Token cost
~1.7k tokens
SKILL.md length
815 words
Files
2
Skills in repo
44
Repo updated
First seen
Licence
MIT

At a glance

Turns a source document such as a README or spec into an executive slide deck as one self-contained HTML file that prints to PDF, one slide per page.

  • Works in 6 steps: Read the source document in full, and… → Build a real-artifact inventory. List… → Ask the user upfront for any known… → …
  • Turning a README, spec or design doc into a leadership briefing
  • SKILL.md covers Invocation, Shared design system, Pipeline (follow in order,… and Credibility contract…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

You give the skill a path to a repo file (.md, .mdx, .json, .html or .txt), or pasted text when no file exists, and it writes a single offline HTML deck for a leadership audience. The deck leads with outcome, impact, timeline, risk and cost, and leaves out code blocks, architecture diagrams and methodology. It selects different facts from the source than an engineering deck would, rather than shortening one.

The pipeline reads the source in full, builds an inventory of the real artifacts it contains, such as outcomes, metrics, dated milestones and cost facts, then composes slides from shared patterns. Fonts, the deck stylesheet, a screen-only viewer script and slide blocks come from a shared assets folder and are inlined into the output, along with a print profile. The file lands in a presentations folder at the repo root, named from the source path with slashes turned into hyphens and ending in .executive.html, and a re-run overwrites it. PPTX, Keynote and Google Slides are not produced.

When your agent uses it

  • Turning a README, spec or design doc into a leadership briefing
  • Preparing an exec deck that covers outcome, timeline, risk and cost
  • Producing a slide deck that exports to PDF without a presentation app

Example prompts

  • “Make an executive presentation from docs/payments-migration.md.”
  • “Turn the README in hub/agents/chat into a deck for our leadership review.”
  • “I need a pitch deck for decision-makers based on the design doc in specs/search-v2.md.”

Requirements

  • A source document in the repo, or pasted text

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read the source document in full, and re-read the user's request so you know the goal
  2. Build a real-artifact inventory. List every concrete artifact that *actually exists in
  3. Ask the user upfront for any known impact figures the source does not contain
  4. Select the executive slides (rules below), drawing values only from the inventory or
  5. Emit the presentation: inline fonts.css, deck.css, and deck-viewer.js from the
  6. Self-check against the checklist, then report the placeholder list to the user

What it can do on your machine

Read from SKILL.md and the folder at commit 05fb50b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Executive Presentation Builder loads about 1.7k tokens when it runs. Until then it costs about 153 tokens; SKILL.md has 815 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~153
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from amd/gaia at commit 05fb50b, republished under its MIT licence (© amd). 815 words, ~1,738 tokens.

Download SKILL.mdSave it as .claude/skills/gaia-executive-presentation/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
gaia-executive-presentation
description
Generate an EXECUTIVE slide presentation (leadership / decision-maker audience) from a source document as self-contained HTML that prints cleanly to PDF, one slide per page. Use when the user asks for an executive presentation, a leadership briefing, a pitch or exec deck, or to turn a README/spec/design doc into executive slides. Leads with outcome, impact, timeline, risk, and cost; no code blocks, no architecture diagrams, no methodology. Offline HTML with an @media print profile; no PPTX/Keynote/Google Slides. For an engineering-facing version, use gaia-technical-presentation.

GAIA Executive Presentation

Turn one source document into a credible executive slide presentation for a leadership / decision-maker audience — outcome, impact, timeline, risk, and cost — as a single self-contained HTML file that exports cleanly to PDF, one slide per printed page.

This skill produces the executive tier only. For an engineering-facing version of the same source (architecture, methodology, contracts), use the gaia-technical-presentation skill. The executive presentation is not a shortened technical one: it selects different facts for a different audience.

Invocation

gaia-executive-presentation <source-path>

  • Input: a path to a repo file (.md, .mdx, .json, .html, .txt) — the primary form. Pasted text is accepted as a fallback when no file exists.
  • Output: presentations/<source-path-slug>.executive.html at the repo root, where the slug is the source path with / replaced by - (so hub/agents/chat/python/README.md → presentations/hub-agents-chat-python-README.executive.html). Deterministic; re-runs overwrite in place — never hand-edit the output.
  • Never write next to the source. Decks are local scratch, and many sources live in directories that ship (hub/agents/*/python/, src/). The root presentations/ dir is gitignored; a presentations/ dir dropped next to a package is not, and would land in the published artifact. The path slug keeps two same-named sources (two README.mds) apart.

Shared design system

The look, fonts, slide patterns, and print profile live in the shared assets directory and are inlined verbatim into the output (do not duplicate or hand-edit them per run):

  • .claude/skills/gaia-presentation-assets/assets/fonts.css — base64 brand fonts (offline)
  • .claude/skills/gaia-presentation-assets/assets/deck.css — design system + @media print
  • .claude/skills/gaia-presentation-assets/assets/deck-viewer.js — screen-only viewer
  • .claude/skills/gaia-presentation-assets/assets/slide-blocks.html — slide patterns to compose from

Pipeline (follow in order, every run)

  1. Read the source document in full, and re-read the user's request so you know the goal the presentation must serve.
  2. Build a real-artifact inventory. List every concrete artifact that actually exists in the source: outcomes, metrics, dated milestones, cost/footprint facts, adoption — each with its source location (file:line or section). This inventory is the ONLY content source for slide facts.
  3. Ask the user upfront for any known impact figures the source does not contain (accuracy, time saved, adoption, cost). One concise prompt; proceed with whatever they give.
  4. Select the executive slides (rules below), drawing values only from the inventory or the user's answers. Any quantitative point with neither becomes a loud, labeled placeholder — never an invented value.
  5. Emit the presentation: inline fonts.css, deck.css, and deck-viewer.js from the shared assets directory into one HTML file, compose slides from slide-blocks.html, populate from the inventory. Write to the output path.
  6. Self-check against the checklist, then report the placeholder list to the user (every ⚠ PLACEHOLDER with what value it needs).

Credibility contract (non-negotiable)

Resolve every slide value in this order: cite-from-source → else ask the user → else insert a loud, labeled placeholder. The one forbidden act is silent fabrication: an invented number presented as if it came from the source. Placeholders are fine because they are visually unmistakable as not-yet-real and are reported back. Where the source supports no real artifact for a slide and the slide is not load-bearing, omit it rather than pad with generic prose. Executive does not mean vague — every claim must still be concrete and credible.

Show full SKILL.md (308 more words)Show less

Executive tier — what belongs here (and what must not)

  • Leadership audience: lead with outcome, impact, timeline, risk, and cost. Distilled but still concrete (real numbers/outcomes only).
  • Forbidden: code blocks, architecture diagrams, methodology sections. (The header chevron glyph is fine; do not add a pipeline/architecture diagram.)
  • Materially fewer slides than a technical deck would use — typically 5–7.
  • Select different facts for this audience, not the technical deck truncated or renamed. If you find yourself copying technical slides and deleting detail, stop and re-select for impact.

Self-contained + print (enforced by the shared assets — do not weaken)

  • Inline everything. No http(s)://, no CDN, no external file refs.
  • deck.css carries the @media print profile: @page { size: landscape; margin:0 }, one slide per page (break-after: page; break-inside: avoid), height:auto; min-height:100vh in print, all chrome hidden. Do not edit these rules per-presentation.
  • The viewer JS is screen-only; it is disabled under @media print.

Worked example

reference/example-executive.html — generated from the GAIA email agent hub package (hub/agents/email/python/): 7 leadership-framed slides (problem/compliance risk, business value, deployment footprint, timeline, KPIs, close) — no code, no architecture diagrams, no methodology. Its KPI and timeline-date values intentionally show labeled ⚠ PLACEHOLDER because no benchmark/date data existed in the source at generation time — a demonstration of the credibility contract.

Checklist before reporting done

  • Does the presentation satisfy the user's goal? Re-read the user's request: do the slides cover what they asked to present, framed for leadership (impact/decision), so the audience can act on it? If not, revise before reporting done.
  • No <pre>/code blocks, no architecture diagram, no methodology slide.
  • Materially fewer slides than a technical deck of the same source would be.
  • One self-contained HTML file; no external refs (grep -c 'https\?://' is 0).
  • Every quantitative value is sourced, user-supplied, or a labeled placeholder — no fabricated numbers.
  • Placeholder list reported to the user.
  • (If a browser is available) printed-page count == slide count, nothing clipped.

© amd, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .claude/skills/gaia-executive-presentation of amd/gaia.

  • SKILL.md
  • reference/example-executive.html

Open the folder on GitHubat commit 05fb50b

Compare with similar skills

Executive Presentation Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Executive Presentation Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Executive Presentation Builder this skillamd/gaia1.6k—~1.7kAutomated safety check: PassMIT
Document Designjamditis/claude-skills-journalism417—~1.9kAutomated safety check: PassMIT
Paper Deckzsyggg/paper-craft-skills1.3k—~1.4kAutomated safety check: PassNone
Documentszhongkaifu/TensorSharp559—~4.2kAutomated safety check: PassBSD-3-Clause
Paper2slidesQuZhan51496/paper2anything469—~3.8kAutomated safety check: NotesApache-2.0
Li CarouselJakeschincariol/linkedin-agent-skill1.6k—~715Automated safety check: PassMIT

Similar skills

  • Document Design

    jamditis/claude-skills-journalism

    Creates print-ready HTML that exports to PDF. An agent skill from jamditis/claude-skills-journalism.

    417 GitHub stars~1.9k tokensUpdated 4 days ago
    Documents & OfficeAuto-check passed
  • Paper Deck

    zsyggg/paper-craft-skills

    将论文、技术文章或知识内容制作成高真实感的 AIGC 幻灯片。先做叙事结构和逐页视觉导演,再调用生图模型生成每一页 16:9 slide image,最后合成为 PPTX/PDF。适合论文汇报、组会、公开课、技术分享、商业化研究展示;当用户提到“论文PPT”“AI生成PPT”“不像AI的PPT”“高质感幻灯片”“逐页生图PPT”时使用。

    1.3k GitHub stars~1.4k tokensUpdated 4 mo ago
    Documents & OfficeAuto-check passed
  • Documents

    zhongkaifu/TensorSharp

    Read and write real documents on the device - PDF, XLSX, DOCX, PPTX and CSV.

    559 GitHub stars~4.2k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Paper2slides

    QuZhan51496/paper2anything

    Turn an academic paper PDF into a presentation deck (.pptx) end-to-end.

    469 GitHub stars~3.8k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check: notes
  • Li Carousel

    Jakeschincariol/linkedin-agent-skill

    Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload.

    1.6k GitHub stars~715 tokensUpdated 22 days ago
    Documents & OfficeAuto-check passed
  • Ky Markdown Rebuilder

    KyrieCheungYep/ky-markdown-rebuilder

    Rebuild visual documents into reliable Markdown by combining text extraction with page or screenshot alignment.

    117 GitHub stars~5.7k tokensUpdated 3 mo ago
    Documents & OfficeAuto-check passed

More from amd/gaia

All 44 skills in this repo
  • Adds a release eval scorecard to a GAIA hub agent by writing a harness adapter, running a real eval, and wiring the result into the agent's README and release gate.

    1.6k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Walks through releasing a GAIA sidecar agent as a frozen binary plus npm client through the tag-triggered Agent Hub CI pipeline, with a human gate before publishing.

    1.6k GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Mines local Claude Code session transcripts with a deterministic Python pipeline to show what the agent is actually used for, how often it fails and what it costs.

    1.6k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Benchmarks AMD's GAIA agent against Claude Code and across models on quality, honesty, steps, tokens, time and real cost, using gaia eval tasks.

    1.6k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Guides safe code changes by finding the right file with grep or semantic search, reading before editing, reproducing bugs first, and proving a fix with a real test run.

    1.6k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Walks through scaffolding, writing and testing a new GAIA agent as a Python class with the SDK, from the base Agent subclass to registered tool methods.

    1.6k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Questions about Executive Presentation Builder

What does Executive Presentation Builder do?

Turns a source document such as a README or spec into an executive slide deck as one self-contained HTML file that prints to PDF, one slide per page. txt), or pasted text when no file exists, and it writes a single offline HTML deck for a leadership audience. The deck leads with outcome, impact, timeline, risk and cost, and leaves out code blocks, architecture diagrams and methodology.

When should I use Executive Presentation Builder?

Executive Presentation Builder fits situations like: turning a README, spec or design doc into a leadership briefing; preparing an exec deck that covers outcome, timeline, risk and cost; producing a slide deck that exports to PDF without a presentation app.

How do I install Executive Presentation Builder in Claude Code?

Run `npx skills add amd/gaia --skill gaia-executive-presentation -a claude-code`. Or copy the skill folder (.claude/skills/gaia-executive-presentation in amd/gaia) into .claude/skills/gaia-executive-presentation in your project. Claude Code loads it when a task matches its description.

How do I install Executive Presentation Builder in Codex?

Run `npx skills add amd/gaia --skill gaia-executive-presentation -a codex`. Or copy the skill folder (.claude/skills/gaia-executive-presentation in amd/gaia) into .agents/skills/gaia-executive-presentation in your project. Codex loads it when a task matches its description.

Can I use Executive Presentation Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amd/gaia --skill gaia-executive-presentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gaia-executive-presentation, .gemini/skills/gaia-executive-presentation, .github/skills/gaia-executive-presentation and .opencode/skills/gaia-executive-presentation in your project.

What does Executive Presentation Builder need to run?

SKILL.md names no scripts, command-line tools or credentials: Executive Presentation Builder is instructions for the agent only. Our summary lists: A source document in the repo, or pasted text.

Does Executive Presentation Builder access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Executive Presentation Builder safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Executive Presentation Builder use?

Executive Presentation Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Executive Presentation Builder use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Executive Presentation Builder?

Skills that share tags, products or a category with Executive Presentation Builder: Document Design (jamditis/claude-skills-journalism, 417 stars), Paper Deck (zsyggg/paper-craft-skills, 1.3k stars), Documents (zhongkaifu/TensorSharp, 559 stars) and Paper2slides (QuZhan51496/paper2anything, 469 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Executive Presentation Builder?

amd (a GitHub organization) maintains it in amd/gaia, which has 1,579 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 8, 2026.

Source: amd/gaia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.