render-report

Render Quarto Stata reports after verifying engine, freshness, citations, and numerical claims.

220|358|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/maxwell2732/codex-stata-for-economists --skill render-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-report
Source: https://github.com/maxwell2732/codex-stata-for-economists/tree/main/.claude/skills/render-report
Command: npx skills add https://github.com/maxwell2732/codex-stata-for-economists --skill render-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents you from publishing reports that are incomplete, out of date, or numerically unverified by enforcing pre-flight checks before Quarto rendering.

Core Features & Use Cases

  • Quarto + Stata engine verification: Ensures the Quarto Stata engine is available (e.g., reports won't fail mid-render for avoidable setup issues).
  • Freshness and single-source-of-truth enforcement: Detects stale figures/tables referenced by the .qmd by comparing artifact and producing do-file modification times, then triggers re-runs when needed.
  • Citation completeness and numerical-claim validation: Verifies all @key citations exist in references.bib and blocks rendering if any number-bearing claims cannot be verified from logs/*.log.
  • Use case: After running Stata analyses that generate output/tables/ and output/figures/, you can compile them into a Quarto .qmd report that is guaranteed to match the latest artifacts and verified claims.

Quick Start

Use the render-report skill to render the report by telling it: Render the Quarto Stata report at reports/your_report.qmd and let it verify engine availability, artifact freshness, citations, and numerical claims before producing the final HTML/PDF/DOCX.

Frequently Asked Questions about render-report

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

FAQPage Schema
How do I render a Quarto report with Stata and ensure reproducibility?

Rendering a Quarto Stata report requires resolving the .qmd path, verifying the Quarto Stata engine, checking artifact freshness against do-files, and validating numerical claims from logs before producing final output.

Why does my Quarto Stata report fail mid-render with avoidable setup issues?

Quarto Stata reports often fail mid-render due to missing engine availability, stale output tables and figures, or unverified numerical claims in logs. Pre-flight checks validate these dependencies before rendering begins.

How do I verify numerical claims and citations before rendering a Quarto report?

Numerical claim verification checks that every number-bearing claim in the .qmd matches entries in logs/*.log, and citation integrity ensures all @key citations exist in references.bib before rendering proceeds.

Can I use this skill if my Stata do-files produce outdated figures and tables?

Yes, the skill detects stale figures and tables by comparing artifact modification times against the producing do-file modification times, then triggers re-runs to enforce a single source of truth before rendering.

What are the limitations of enforcing pre-flight checks for Quarto Stata reports?

Pre-flight checks block rendering if the Quarto Stata engine is unavailable, if citations are missing from references.bib, or if numerical claims cannot be verified from artifact logs, preventing incomplete or unverified reports from publishing.

What's the best way to automate reproducible econometrics reporting with Quarto and Stata?

Automating reproducible econometrics reporting involves running Stata do-files to generate output/tables and output/figures, then compiling them into a .qmd report with enforced freshness checks and verified numerical claims for final rendering.