audit-replication
Validate the replication package for the sewage-house-prices project. Runs 10 checks covering script execution, file integrity, output freshness, dependency verification, data provenance, and README completeness (AEA format). This skill should be used when asked to "audit replication", "check the package", or "verify reproducibility".
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill audit-replication --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Audit Replication Package Run end-to-end validation of the replication package for the sewage-house-prices project. **Input:** `$ARGUMENTS` — directory containing the replication package (`Replication/` by default), or `here` for the current project root. --- ## Project-Specific Context ### Expected Structure - Pipeline scripts: `scripts/R/01_data_ingestion/` through `scripts/R/06_analysis_datas
What does the audit-replication skill do?
Validate the replication package for the sewage-house-prices project. Runs 10 checks covering script execution, file integrity, output freshness, dependency verification, data provenance, and README completeness (AEA format). This skill should be used when asked to "audit replication", "check the package", or "verify reproducibility".
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill audit-replication --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.