quarto-authoring
This skill provides comprehensive guidance for authoring Quarto documents (.qmd files), configuring projects via _quarto.yml, and implementing Quarto-specific features like cross-references, citations, callouts, diagrams, and extensions. Use this skill when users explicitly mention Quarto, work with Quarto files or projects, or need to migrate existing R Markdown, bookdown, blogdown, xaringan, distill, or Jupyter projects to Quarto.
git clone --depth 1 https://github.com/posit-dev/skills /tmp/quarto-authoring && cp -r /tmp/quarto-authoring/quarto/quarto-authoring ~/.claude/skills/quarto-authoringSKILL.md
# Quarto Authoring
> This skill is based on Quarto CLI v1.9.36 (2026-03-24).
## When to Use What
Task: Write a new Quarto document
Use: Follow "QMD Essentials" below, then see specific reference files
Task: Add cross-references
Use: [references/cross-references.md](references/cross-references.md)
Task: Configure code cells
Use: [references/code-cells.md](references/code-cells.md)
Task: Add figures with captions
Use: [references/figures.md](references/figures.md)
Task: Create tables
Use: [references/tables.md](references/tables.md)
Task: Add citations and bibliography
Use: [references/citations.md](references/citations.md)
Task: Add callout blocks
Use: [references/callouts.md](references/callouts.md)
Task: Add diagrams (Mermaid, Graphviz)
Use: [references/diagrams.md](references/diagrams.md)
Task: Control page layout
Use: [references/layout.md](references/layout.md)
Task: Use shortcodes
Use: [references/shortcodes.md](references/shortcodes.md)
Task: Add conditional content
Use: [references/conditional-content.md](references/conditional-content.md)
Task: Use divs and spans
Use: [references/divs-and-spans.md](references/divs-and-spans.md)
Task: Configure YAML front matter
Use: [references/yaml-front-matter.md](references/yaml-front-matter.md)
Task: Find and use extensions
Use: [references/extensions.md](references/extensions.md)
Task: Apply markdown linting rules
Use: [references/markdown-linting.md](references/markdown-linting.md)
Task: Choose or configure a compute engine (knitr, jupyter, julia)
Use: [references/engines.md](references/engines.md)
### Migration (only when converting an existing project)
Do NOT read these references when writing new Quarto documents.
Only read the one matching the source format when the user explicitly asks to convert or migrate an existing project.
- R Markdown (.Rmd) to Quarto: [references/conversion-rmarkdown.md](references/conversion-rmarkdown.md)
- bookdown project: [references/conversion-bookdown.md](references/conversion-bookdown.md)
- xaringan slides: [references/conversion-xaringan.md](references/conversion-xaringan.md)
- distill article: [references/conversion-distill.md](references/conversion-distill.md)
- blogdown site: [references/conversion-blogdown.md](references/conversion-blogdown.md)
- Jupyter notebook (.ipynb) to/from Quarto: [references/conversion-jupyter.md](references/conversion-jupyter.md)
## QMD Essentials
### Basic Document Structure
```markdown
---
title: "Document Title"
author: "Author Name"
date: today
format: html
---
Content goes here.
```
A Quarto document consists of two main parts:
1. **YAML Front Matter**: Metadata and configuration at the top, enclosed by `---`.
2. **Markdown Content**: Main body using standard markdown syntax.
### Divs and Spans
Divs use fenced syntax with three colons:
```markdown
::: {.class-name}
Content inside the div.
:::
```
Spans use bracketed syntax:
```markdown
This is [important text]{.highlight}.
```
Details: [references/divs-and-spans.md](references/divs-and-spans.md)
### Code Cell Options Syntax
A code cell starts with triple backticks and a language identifier between curly braces.
Code cells are code blocks that can be executed to produce output.
Quarto uses the language's comment symbol + `|` for cell options. Options use **dashes, not dots** (e.g., `fig-cap` not `fig.cap`).
- R, Python, Julia: `#|`
- Mermaid: `%%|`
- Graphviz/DOT: `//|`
````markdown
```{language}
#| label: fig-example
#| echo: false
#| fig-cap: "A scatter plot example."
# code that produces a figure
```
````
Set document-level defaults in YAML front matter:
```yaml
execute:
echo: false
warning: false
```
**Caching — critical engine difference:** Only suggest `#| cache: true` for R code cells (knitr engine).
Never suggest it for other language cells — it does not work and will be silently ignored.
The only correct approach is `execute: cache: true` in the top-level YAML front matter when using engines other than `knitr`.
Python/Jupyter requires `jupyter-cache` (`pip install jupyter-cache`):
```yaml
execute:
cache: true
```
Details: [references/code-cells.md](references/code-cells.md)
### Cross-References
Labels must start with a type prefix. Reference with `@`:
- Figure: `fig-` prefix, e.g., `#| label: fig-plot` → `@fig-plot`
- Table: `tbl-` prefix, e.g., `#| label: tbl-data` → `@tbl-data`
- Section: `sec-` prefix, e.g., `{#sec-intro}` → `@sec-intro`
- Equation: `eq-` prefix, e.g., `{#eq-model}` → `@eq-model`
````markdown
```{language}
#| label: fig-plot
#| fig-cap: "A caption for the plot."
# code that produces a figure
```
See @fig-plot for the results.
````
Details: [references/cross-references.md](references/cross-references.md)
### Callout Blocks
Five types: `note`, `warning`, `important`, `tip`, `caution`.
```markdown
::: {.callout-note}
This is a note callout.
:::
::: {.callout-warning}
## Custom Title
This is a warning with a custom title.
:::
```
Details: [references/callouts.md](references/callouts.md)
### Figures
```markdown
{#fig-name fig-alt="Alt text"}
```
Subfigures:
```markdown
::: {#fig-group layout-ncol=2}
{#fig-sub1}
{#fig-sub2}
Main caption for the group.
:::
```
Details: [references/figures.md](references/figures.md)
### Tables
```markdown
::: {#tbl-example}
| Column 1 | Column 2 |
| -------- | -------- |
| Data 1 | Data 2 |
Table caption.
:::
```
Details: [references/tables.md](references/tables.md)
### Citations
```markdown
According to @smith2020, the results show...
Multiple citations [@smith2020; @jones2021].
```
Configure in YAML:
```yaml
bibliography: references.bib
csl: apa.csl
```
Details: [references/citations.md](references/citations.md)
## Common Workflows
### Creating an HTML Document
```yaml
title: "My Report"
author: "Your Name"
date: today
format:
html:
toc: true
code-fold: true
theme: cosmo
```
### Cr>
Create and use brand.yml files for consistent branding across Shiny apps and Quarto documents. Covers: (1) Creating new _brand.yml files, (2) Applying to Shiny (R and Python), (3) Using in Quarto, (4) Modifying existing files, and (5) Troubleshooting. Includes complete specifications and integration guides.
Write ggsql queries — a grammar of graphics for SQL. Use when the user wants to create, modify, or understand a ggsql visualization query.
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Activate when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on GitHub, and has GitHub Actions CI with automated checks (lint, build, tests, etc.). Does NOT merge - stops when CI passes and provides the PR link.
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
Bulk resolve unresolved PR review threads on the current branch’s PR — typically after threads have been addressed manually or via /pr-threads-address
>
Guide for drafting issue closure and decline responses as an open-source package maintainer. Use when helping compose a reply that says \"no\" to a feature request, closes an issue as won't-fix, redirects a user to a different package, explains why a design choice is intentional, or otherwise declines or closes a community contribution. Also use when the maintainer needs to explain a deprecation, point out a user misunderstanding, or communicate an effort/scope tradeoff to a contributor.