quarto-style

Enforce Quarto style and authoring conventions for .qmd files.

1|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/estebandegetau/Fiscal-shocks --skill quarto-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quarto-style
Source: https://github.com/estebandegetau/Fiscal-shocks/tree/main/.claude/skills/quarto-style
Command: npx skills add https://github.com/estebandegetau/Fiscal-shocks --skill quarto-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent, reproducible, and project-compliant Quarto document authoring across directories so authors do not duplicate inherited settings or break rendering and cross-references.

Core Features & Use Cases

  • Configuration inheritance: Read and respect project-level _quarto.yml and directory _metadata.yml to avoid redundant overrides.
  • Setup and pipeline integration: Guidance for including a setup chunk only when reading pipeline data and for setting themes and data-loading conventions.
  • Tables and plots: Enforce gt-based tables with gt_theme_report(), fig-/tbl- chunk labels, and fig-cap/tbl-cap usage for cross-references.
  • Markdown and citation rules: Require blank lines before block elements, forbid trailing horizontal rules, standardize citation placement and the References section.
  • Code chunk conventions: Standardize chunk labels, execute/cache options, and dynamic markdown patterns to maintain reproducibility and readability.
  • Use case: Preparing a reproducible project report that reads target pipeline data, produces labeled figures and tables, and renders consistently across team members.

Quick Start

When creating or editing a .qmd file, read the project _quarto.yml and the directory _metadata.yml first, then apply the guide's chunk, labeling, table, plot, markdown, and citation conventions.

Frequently Asked Questions about quarto-style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain consistent Quarto document style across multiple project directories?

To maintain consistent Quarto document style, read project-level _quarto.yml and directory-level _metadata.yml first. This ensures configuration inheritance is respected and prevents redundant overrides when authoring .qmd files across directories.

What markdown formatting rules are needed for reproducible Quarto rendering?

Reproducible Quarto rendering requires blank lines before block elements, forbidding trailing horizontal rules, and standardizing citation placement with a formatted References section to ensure consistent output.

How do I set up code chunks and cross-references in Quarto reports?

Setting up Quarto code chunks requires standardized chunk labels, execute and cache options, and using fig-/tbl- labels with fig-cap and tbl-cap fields to ensure reproducible rendering and consistent cross-references.

Can I use gt tables with Quarto for reproducible analysis reports?

Yes, you can use gt tables with Quarto by applying gt_theme_report() and enforcing fig-/tbl- chunk labels with fig-cap and tbl-cap usage. This ensures tables render consistently and support cross-referencing.

When do I need a setup chunk in a Quarto notebook?

You need a setup chunk in a Quarto notebook only when reading pipeline data. This setup chunk establishes data-loading conventions and sets themes before the main analysis runs.

Why do my Quarto cross-references break when rendering team reports?

Quarto cross-references break when chunk labels are non-standard or fig-cap and tbl-cap fields are missing. Standardizing chunk labels and applying proper caption conventions ensures cross-references render consistently across team members.