quarto-slides
Skill0 starsChanged 45 days agoMITView on GitHub
Generate presentation slide decks from content with Quarto (open source, bundled with RStudio). Outputs reveal.js HTML, PowerPoint (.pptx) or PDF (Beamer/Typst). Use when user says "create slides", "make a presentation", "build a deck", "fais-moi une présentation", or asks to turn content into slides. Run with /quarto-slides.
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analystSkill
- build-appSkill
- build-websiteSkill
- business-setupSkill
- content-pipelineSkill
- content-writerSkill
- email-assistantSkill
- email-digestSkill
- ksuite-setupSkill
- meeting-prepSkill
- memorySkill
- odooSkill
- plugin-builderSkill
- qfieldcloudSkill
- qgisSkill
- research-leadSkill
- researchSkill
- r-sessionSkill
- schedulerSkill
- scrum-masterSkill
- skill-creatorSkill
- task-managerSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Check Quarto first: quarto --version.
- Very specific: line 28
Read context/my-voice.md and context/my-business.md for tone and offers.
- Very specific: line 42
Do not use the em-dash character in slides (see .claude/rules/output-style.md).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Quarto Slides
Replaces the Gamma skill of the original template. Everything stays local and open source: Quarto (MIT/GPL) ships with RStudio, so no account and no API key are needed.
Formats
| Format | Command | When |
| reveal.js (HTML) | quarto render deck.qmd --to revealjs | Default. Opens in any browser, self-contained with embed-resources: true |
| PowerPoint | quarto render deck.qmd --to pptx | The user must edit it in PowerPoint / LibreOffice Impress / kSuite (OnlyOffice in kDrive) |
quarto render deck.qmd --to beamer (needs TinyTeX) or --to typst | Print or send as attachment |
Check Quarto first: quarto --version. If missing, RStudio's bundled Quarto may
not be on the terminal PATH: tell the user to install it from https://quarto.org/docs/get-started/.
Steps
- Structure the content: one idea per slide, 8 to 15 slides, a hook, a clear close.
Read
context/my-voice.mdandcontext/my-business.mdfor tone and offers. - Write the deck to
.tmp/slides/<slug>-<date>/deck.qmd, starting from.claude/skills/quarto-slides/assets/template.qmd. Slides are##headings. R code chunks are allowed (charts from the user's data render directly). - Render:
quarto render deck.qmd --to revealjs(and/orpptx). - Deliver: give the output path; offer to upload it to kDrive
(
mcp__ksuite-kdrive__kdrive_upload_file) if kSuite is connected.
Tips
- Speaker notes:
::: {.notes}blocks. - Two columns:
:::: {.columns}/::: {.column width="50%"}. - Incremental bullets:
::: {.incremental}. - Brand colors: set them in the YAML (
theme, or a smallcustom.scss). - Do not use the em-dash character in slides (see
.claude/rules/output-style.md).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

