pipeline
Classical end-to-end empirical analysis workflow in the traditional Python econometric stack — pandas + numpy + scipy +…
Verify that every quantitative claim in the paper is traceable to an analysis output file, and that no important output was omitted. Make sure to use this skill whenever the user wants to check that the paper and analysis are consistent before submission. Triggers include: "run
Claude Code
$ npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill quality-gate --agent claude-code
Codex
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill quality-gate -a codex -y
Cursor
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill quality-gate -a cursor -y
Gemini CLI
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill quality-gate -a gemini-cli -y
GitHub Copilot
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill quality-gate -a github-copilot -y
OpenCode
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill quality-gate -a opencode -y
Windsurf
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill quality-gate -a windsurf -y
name: quality-gate description: >- Verify that every quantitative claim in the paper is traceable to an analysis output file, and that no important output was omitted. Make sure to use this skill whenever the user wants to check that the paper and analysis are consistent before submission. Triggers include: "run the quality gate", "check the paper matches the analysis", "verify consistency", "does the paper match my results", "check my numbers", "are my tables right", "quality check before submission", "verify my claims", "make sure everything is consistent", "double-check the paper against my output files", or any pre-submission integrity check between paper text and computed results. argument-hint: "[paper file path, or leave blank to auto-detect]" allowed-tools: ["Read", "Grep", "Glob", "Write", "Task", "AskUserQuestion"]
Cross-check every numerical claim in the paper against analysis output files. Reports only — never edits.
**Input:** `$ARGUMENTS` — path to the paper draft, or leave blank to auto-detect.
---
If `$ARGUMENTS` is provided, use that path. Otherwise glob for:
If multiple drafts found, use AskUserQuestion to let the user pick:
---
Read the full manuscript and extract every quantitative claim:
Record location (section, paragraph, line number if available) for each claim.
---
Glob for all output files:
Build an inventory with file paths and sizes.
---
Dispatch the `verifier` agent via Task to perform the heavy verification work. Pass it:
Task prompt: "You are the verifier agent. Paper draft: [path]. Bibliography: [bib path]. CLAIMS TO VERIFY: [paste the full claims list from Step 2] OUTPUT FILE INVENTORY: [paste the inventory from Step 3] Verify each claim against the output files. Then do a reverse check — find output files NOT referenced in the paper. Then check all citation keys against the bibliography. Follow the verifier agent instructions and return your full verification report."
After the verifier completes, collect its results:
---
Save to `quality_reports/quality_gate_[YYYY-MM-DD]_[paper-name].md`:
# Quality Gate Report: [Paper Name] **Date:** [YYYY-MM-DD] **Paper:** [file path] ## Verdict: PASS / CONDITIONAL PASS / FAIL PASS = all claims matched, no missing citations, no unexplained unreferenced outputs CONDITIONAL PASS = minor unverified claims or informational unreferenced outputs FAIL = unverified critical claims or missing citations --- ## Claim Verification | Claim | Location | Found in Output? | Source File | Status | |-------|----------|-----------------|-------------|--------| | β = 0.23 (SE = 0.04) | Section 4, para 2 | Yes | output/tables/main_regs.tex | MATCHED | | N = 4,521 | Table 2 note | Yes | output/tables/main_regs.tex | MATCHED | | 42% of firms | Intro, para 1 | No | — | UNVERIFIED | --- ## Unreferenced Outputs Files in output/ not referenced in the paper: | File | Size | Recommended Action | |------|------|-------------------| | output/tables/robustness_het.tex | 4.2 KB | Reference in Section 7 or explain exclusion | --- ## Missing Citations | Key | Used At | Status | |-----|---------|--------| | SmithJones2021 | Section 3, para 1 | NOT IN BIBLIOGRAPHY — CRITICAL | --- ## Summary - Claims verified: N / M total - Claims unverified: K (see table above) - Unreferenced outputs: J - Missing citations: L ## Recommended Actions (Priority Order) 1. [BLOCKING] ... 2. [RECOMMENDED] ...
---
## 🔥 力荐 · StatsPAI — Stata 与 R 的 Python 平替,为 AI Agent 而生 🔁 Stata / R 平替:reghdfe、csdid、rdrobust、synth、fixest、did 等常用命令在 Python 中一站式替代,一个 import statspai as sp 搞定 DID / RD / IV / SCM / DML / matching 🤖 面向 Agent 设计:结构化结果对象 + 内置 MCP Server,Claude / Codex
Classical end-to-end empirical analysis workflow in the traditional Python econometric stack — pandas + numpy + scipy +…
Use when the user asks to run a full empirical / causal analysis in Python — by default in the style of an applied economics…
Classical end-to-end empirical analysis workflow in the traditional Python econometric stack — pandas + numpy + scipy +…
Classical end-to-end empirical analysis workflow in the traditional Stata ecosystem — native Stata + reghdfe + ivreg2 + csdid +…
Classical end-to-end empirical analysis workflow in the modern tidyverse + econometrics R ecosystem — dplyr + tidyr + haven +…
Systematic writing framework for philosophy and interdisciplinary academic papers from optimized outline to submission-ready…
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…