brycewang-stanford/Auto-Empirical-Research-Skills / skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env
check-env
VerifiedVerifies required tools (Quarto, uv, Python, R, Stata, TeX) and Jupyter kernels are installed. Use when setting up or troubleshooting.
Check Environment
Verify that all required tools and dependencies are installed and correctly configured.
Steps
-
Check each required tool and report its version (or "not found"):
Tool Command Minimum Quarto quarto --version>= 1.4 uv uv --versionany Python python3 --version>= 3.12 R R --versionoptional Stata which stataoptional TeX Live pdflatex --versionoptional (for PDF) GitHub CLI gh --versionoptional -
Check Jupyter kernels by running
uv run jupyter kernelspec listand verify:python3— requiredir— optional (needed for R notebooks)nbstata— optional (needed for Stata notebooks)
-
Check the Python virtual environment:
- Verify
.venv/exists - Run
uv run python -c "import numpy; import pandas; import matplotlib; import jupytext; print('Core packages OK')"to confirm importability
- Verify
-
Check nbstata configuration (if nbstata kernel is present):
- Verify
~/.config/nbstata/nbstata.confexists - Read it and check that
stata_dirpoints to an existing directory
- Verify
-
Report a structured results table:
Tool/Check Status Version/Details ───────────────────────────────────────────────── Quarto PASS 1.6.x uv PASS 0.x.x Python PASS 3.12.x R PASS 4.x.x Stata SKIP not found (optional) TeX Live PASS 2024 GitHub CLI PASS 2.x.x Kernel: python3 PASS installed Kernel: ir PASS installed Kernel: nbstata SKIP not installed .venv/ PASS exists Core Python packages PASS importable nbstata.conf SKIP kernel not installedUse PASS / FAIL / SKIP (SKIP for optional tools that are absent).
-
If any required check fails, provide the installation command or link to fix it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |