From quarto-publishing
Use when designing or reviewing shared Quarto project configuration, including _quarto.yml, _metadata.yml, shared metadata, project profiles, parameters, render targets, project types, engine-aware execution settings, and document-vs-project YAML placement. Do not use for single-document authoring, format-specific output styling, deployment, CI, custom extensions, performance architecture, or deep render troubleshooting.
How this skill is triggered — by the user, by Claude, or both
Slash command
/quarto-publishing:quarto-project-configurationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for the project layer of a Quarto workflow, especially `_quarto.yml`, `_metadata.yml`, shared YAML defaults, project profiles, project type, render targets, parameters, bibliography or citation defaults, and organization across multiple `.qmd` files.
Use this skill for the project layer of a Quarto workflow, especially _quarto.yml, _metadata.yml, shared YAML defaults, project profiles, project type, render targets, parameters, bibliography or citation defaults, and organization across multiple .qmd files.
_quarto.yml as the shared project configuration layer, not as a dumping ground for every document preference..qmd files when the option is truly local to one document._quarto.yml or directory-level _metadata.yml when it improves maintainability._metadata.yml for directory-specific defaults, such as defaults for reports, posts, slides, or notebooks in one folder.execute, freeze, render, output-dir, resources, and execute-dir as high-impact settings that require conservative review.jupyter, engine: julia, .ipynb, .py, .jl, .r, or .qmd files before recommending execution, cache, or environment settings.quarto-format-configuration.When reviewing Quarto project configuration, check:
default, website, book, manuscript, or no project._quarto.yml exists when project-level behavior is needed and its project: block is appropriate._metadata.yml when they apply to one folder.output-dir, resources, and ignored files are consistent with the repository layout.execute, freeze, and working-directory settings are safe for collaboration.quarto-format-configuration.For compact examples for _quarto.yml, _metadata.yml, metadata precedence, profiles, parameters, render targets, output directories, and project-level freeze, read references/quarto-project-configuration.md when editing or reviewing concrete project configuration.
Do not redesign .qmd prose or authoring syntax unless needed to explain configuration placement.
Do not deeply tune output formats, templates, themes, CSS, LaTeX, Typst, DOCX reference documents, revealjs, PowerPoint, Beamer, or custom formats.
Do not design deployment, hosting, GitHub Pages, Netlify, Posit Connect, CI, or publishing pipelines.
Do not use this skill as the primary guide for Quarto extensions, Lua filters, brand extensions, project templates, scripts, assets, or validators. Route those requests to the relevant format, authoring, troubleshooting, or future extension/template scope unless they are only being classified as project-configuration boundaries.
Do not solve long-running computation architecture beyond conservative project-level freeze guidance.
Do not perform deep render troubleshooting after failures.
npx claudepluginhub brianmsm/r-workflow-plugins --plugin quarto-publishingGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.