check-env
Verifies required tools (Quarto, uv, Python, R, Stata, TeX) and Jupyter kernels are installed. Use when setting up or troubleshooting.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env --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.
# Check Environment Verify that all required tools and dependencies are installed and correctly configured. ## Steps 1. Check each required tool and report its version (or "not found"): | Tool | Command | Minimum | | ---- | ------- | ------- | | Quarto | `quarto --version` | >= 1.4 | | uv | `uv --version` | any | | Python | `python3 --version` | >= 3.12 | | R | `R --version` | optional | | Stata |
What does the check-env skill do?
Verifies required tools (Quarto, uv, Python, R, Stata, TeX) and Jupyter kernels are installed. Use when setting up or troubleshooting.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env --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.