From quarto-publishing
Use when diagnosing, fixing, or verifying Quarto render failures or rendered-output problems, including failed quarto render commands, YAML parse errors, cell or chunk execution errors, missing packages or files, working-directory and path issues, LaTeX or Typst failures, bibliography/CSL/citation problems, cross-reference failures, image/assets issues, extension/theme/CSS problems that break rendering, generated HTML inspection, screenshot or browser review, link/anchor/navigation checks, logs, local-vs-CI render differences, and honest verification claims. Do not use as the primary skill for ordinary .qmd authoring, planned project architecture, output-format design, cache/freeze/performance strategy, report structure/design, deployment automation, accessibility review, or broad refactoring unless the main task is to fix or verify a render/output failure.
How this skill is triggered — by the user, by Claude, or both
Slash command
/quarto-publishing:quarto-render-troubleshootingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to diagnose, fix, and verify Quarto render failures or rendered-output defects.
Use this skill to diagnose, fix, and verify Quarto render failures or rendered-output defects.
Start from the observed failure or questionable output, isolate the smallest likely cause, apply a targeted fix when tools are available, and verify only what was actually checked.
Never claim that a render, screenshot, browser path, link, anchor, or output was checked unless it was actually checked.
Classify the problem before changing files:
When tools are available:
quarto check, quarto check all, quarto render <file>, quarto render <file> --to <format>, quarto render <file> --log-level debug, quarto render <file> --log <path>, quarto render <file> --execute-debug, and quarto render <file> --debug when intermediate files are needed.Check, as applicable:
execute-dir, relative paths, here, getwd(), and QUARTO_PROJECT_DIR..libPaths(), sessionInfo(), and environment mismatch.jupyter, kernels, virtual environments, quarto check jupyter, Python path issues, and notebook execution settings.engine: julia or Jupyter/IJulia, Julia installation, package environments, and kernel availability.keep-tex, and intermediate .tex.Use other skills when the main task is not troubleshooting:
quarto-authoring-core: writing or reviewing ordinary .qmd content.quarto-project-configuration: designing _quarto.yml, _metadata.yml, profiles, render targets, or project structure.quarto-format-configuration: choosing or configuring output formats before a failure occurs.quarto-computation-performance: reducing expensive recomputation, cache/freeze strategy, precomputed artifacts, or pipeline escalation.quarto-report-design: report structure, audience, and communication design.quarto-publishing-deployment: publishing targets, hosting, and CI/CD setup.quarto-accessibility-quality: accessibility and publication-readiness review beyond failure verification.Say "verified" only for checks actually performed.
Acceptable wording:
report.qmd to HTML successfully."report.html and confirmed the figure appears."#sec-methods."Do not say:
For compact diagnosis patterns for render failures, YAML errors, execution errors, paths/assets, LaTeX/Typst failures, citations, cross-references, HTML verification, and local-vs-CI differences, read references/render-troubleshooting.md when fixing or verifying concrete Quarto render/output problems.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub brianmsm/r-workflow-plugins --plugin quarto-publishing