New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

GAIA Technical Presentation

by amd in amd/gaia

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

MITAuto-check passedDocuments & Office

Install GAIA Technical Presentation

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

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

GitHub CLI
$ gh skill install amd/gaia gaia-technical-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-technical-presentation .claude/skills/gaia-technical-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-technical-presentation
GitHub stars
1.6k
Token cost
~1.6k tokens
SKILL.md length
738 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 a technical slide deck for engineers, as one self-contained HTML file that prints to PDF with 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 or design doc into engineering slides
  • 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

The skill takes a path to a repo file (.md, .mdx, .json, .html or .txt, with pasted text as a fallback) and writes a `.technical.html` file into a `presentations/` folder at the repo root, named from the source path with slashes replaced by dashes. It never writes next to the source, because decks are local scratch and the root folder is gitignored. Re-runs overwrite the output, which is never hand-edited. The deck is for engineers and covers architecture, methodology, request and response contracts and metrics with their method, and allows code blocks and diagrams.

Look, fonts, slide patterns and the print profile come from a shared assets folder and are inlined unchanged, so the file works offline and prints through an `@media print` profile. The pipeline starts by reading the whole source and listing every real artifact in it, such as metrics, tables, charts, snippets, screenshots and dated milestones, each with its source location. That inventory is the only source of slide facts. Output is HTML only, with no PPTX, Keynote or Google Slides, and leadership decks go to a sibling skill.

When your agent uses it

  • Turning a README or design doc into engineering slides
  • Preparing an architecture or deep-dive deck as printable HTML
  • Presenting methodology, contracts and metrics to engineers

Example prompts

  • “Create a technical presentation from docs/architecture.md.”
  • “Turn hub/agents/chat/python/README.md into engineering slides.”
  • “Make a deep-dive deck from this design spec that prints cleanly to PDF.”

Requirements

  • The shared gaia-presentation-assets folder with the deck CSS, fonts and slide patterns

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 evaluation/benchmark results the source does not
  4. Select the technical 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 6c3bb5c. 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

GAIA Technical Presentation loads about 1.6k tokens when it runs. Until then it costs about 155 tokens; SKILL.md has 738 words of instructions outside code blocks.

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

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 6c3bb5c, republished under its MIT licence (© amd). 738 words, ~1,606 tokens.

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

GAIA Technical Presentation

Turn one source document into a credible technical slide presentation for an engineering audience — architecture, methodology, contracts, and metrics — as a single self-contained HTML file that exports cleanly to PDF, one slide per printed page.

This skill produces the technical tier only. For a leadership / decision-maker version of the same source, use the gaia-executive-presentation skill.

Invocation

gaia-technical-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>.technical.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.technical.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: metrics, tables, charts, code/contract snippets, screenshots, version strings, dated milestones — 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 evaluation/benchmark results the source does not contain (accuracy, latency, throughput, cost). One concise prompt; proceed with whatever they give.
  4. Select the technical 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.

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

Technical tier — what belongs here

  • Engineering audience: architecture, methodology, the request/response contract, metrics with their method.
  • Code blocks and inline-SVG diagrams are allowed and encouraged where they carry real source content.
  • Typically 8–14 slides — enough to preserve precision and depth.
  • This is not the executive tier: keep the depth; do not strip methodology to chase brevity. (A leadership-facing cut is the gaia-executive-presentation skill's job.)

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-technical.html — generated from the GAIA email agent hub package (hub/agents/email/python/): 12 slides covering architecture, the request/response contract, the packaging table, the token-usage schema, and code blocks. Its benchmark slide intentionally shows labeled ⚠ PLACEHOLDER values because no eval results 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, at engineering depth, so the audience leaves with what the user intended? If not, revise before reporting done.
  • 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-technical-presentation of amd/gaia.

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

Open the folder on GitHubat commit 6c3bb5c

Compare with similar skills

GAIA Technical Presentation 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.

GAIA Technical Presentation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GAIA Technical Presentation this skillamd/gaia1.6k—~1.6kAutomated safety check: PassMIT
Visual Explainernicobailon/visual-explainer10k—~3.3kAutomated safety check: PassMIT
Plain Writingdocwriter-org/plain-writing-skill461—~3.6kAutomated safety check: PassMIT
Lc Pythonyennanliu/CS_basics142—~4.4kAutomated safety check: NotesNone
Diagrammerdavila7/claude-code-templates32k—~494Automated safety check: PassMIT
PPTXrvdbreemen/OTGW-firmware20734 repos~2.3kAutomated safety check: PassProprietary

Similar skills

  • Visual Explainer

    nicobailon/visual-explainer

    Turns systems, code changes, plans and data into self-contained HTML pages where figures carry the explanation, with options for slide decks and narrated MP4 videos.

    10k GitHub stars~3.3k tokensUpdated today
    Media & CreativeAuto-check passed

  • Plain Writing

    docwriter-org/plain-writing-skill

    Writes and edits prose in a plain and boring style: simple everyday words, complete sentences, no dashes, no jargon, and no analogies.

    461 GitHub stars~3.6k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Lc Python

    yennanliu/CS_basics

    File a LeetCode Python solution into this repo the way the existing ones are filed — find the problem's real slug, write the Python file in the house layout (problem docstring, V0 with an IDEA block…

    142 GitHub stars~4.4k tokensUpdated today
    DevelopmentAuto-check: notes

  • Diagrammer

    davila7/claude-code-templates

    Render clean blueprint-style SVG diagrams from JSON specs. An agent skill from davila7/claude-code-templates.

    32k GitHub stars~494 tokensUpdated today
    DevelopmentAuto-check passed

  • PPTX

    rvdbreemen/OTGW-firmware

    Use this skill any time a .pptx file is involved in any way — as input, output, or both.

    207 GitHub starsUsed in 34 repos~2.3k tokens
    Documents & OfficeAuto-check passed

  • Open Kimi Ppt

    jinwyp/open-ppt-skill

    Create, edit, replicate, read, and export presentations. An agent skill from jinwyp/open-ppt-skill.

    156 GitHub starsUsed in 2 repos~5.1k tokens
    Documents & OfficeAuto-check passed

More from amd/gaia

All 44 skills in this repo

  • GAIA Agent Eval Scorecard

    amd/gaia

    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

  • GAIA Sidecar Agent Release

    amd/gaia

    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

  • Analyzing Claude Code Sessions

    amd/gaia

    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

  • GAIA Agent Benchmarking

    amd/gaia

    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

  • Verified Coding Workflow

    amd/gaia

    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

  • GAIA Agent Builder

    amd/gaia

    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

Categories

Questions about GAIA Technical Presentation

What does GAIA Technical Presentation do?

Turns a source document such as a README or spec into a technical slide deck for engineers, as one self-contained HTML file that prints to PDF with one slide per page. html` file into a `presentations/` folder at the repo root, named from the source path with slashes replaced by dashes. It never writes next to the source, because decks are local scratch and the root folder is gitignored.

When should I use GAIA Technical Presentation?

GAIA Technical Presentation fits situations like: turning a README or design doc into engineering slides; preparing an architecture or deep-dive deck as printable HTML; presenting methodology, contracts and metrics to engineers.

How do I install GAIA Technical Presentation in Claude Code?

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

How do I install GAIA Technical Presentation in Codex?

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

Can I use GAIA Technical Presentation 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-technical-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-technical-presentation, .gemini/skills/gaia-technical-presentation, .github/skills/gaia-technical-presentation and .opencode/skills/gaia-technical-presentation in your project.

What does GAIA Technical Presentation need to run?

SKILL.md names no scripts, command-line tools or credentials: GAIA Technical Presentation is instructions for the agent only. Our summary lists: The shared gaia-presentation-assets folder with the deck CSS, fonts and slide patterns.

Does GAIA Technical Presentation 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 GAIA Technical Presentation 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 GAIA Technical Presentation use?

GAIA Technical Presentation 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 GAIA Technical Presentation use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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 GAIA Technical Presentation?

Skills that share tags, products or a category with GAIA Technical Presentation: Visual Explainer (nicobailon/visual-explainer, 10k stars), Plain Writing (docwriter-org/plain-writing-skill, 461 stars), Lc Python (yennanliu/CS_basics, 142 stars) and Diagrammer (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GAIA Technical Presentation?

amd (a GitHub organization) maintains it in amd/gaia, which has 1,580 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 6, 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.