Save Research Notebook
napjon/krisk
Convert a completed data-analysis conversation into evidence-backed, reproducible living research through the Krisk MCP server.
Verifies required tools (Quarto, uv, Python, R, Stata, TeX) and Jupyter kernels are installed.
Install Check Env
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills check-env --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env .claude/skills/check-env && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "check-env" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env into .claude/skills/check-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-env", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-envType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills check-env --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env .agents/skills/check-env && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "check-env" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env into .agents/skills/check-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-env", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills check-env --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env .cursor/skills/check-env && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "check-env" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env into .cursor/skills/check-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-env", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git --path skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills check-env --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env .gemini/skills/check-env && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "check-env" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env into .gemini/skills/check-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-env", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills check-envInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env .github/skills/check-env && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "check-env" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env into .github/skills/check-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-env", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills check-env --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env .opencode/skills/check-env && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "check-env" agent skill from https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/main/skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env into .opencode/skills/check-env/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-env", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
check-env- GitHub stars
- 4.5k
- Token cost
- ~578 tokens
- SKILL.md length
- 172 words
- Files
- 1
- Skills in repo
- 383
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Verifies required tools (Quarto, uv, Python, R, Stata, TeX) and Jupyter kernels are installed.
- Works in 6 steps: Check each required tool and report its… → Check Jupyter kernels by running uv run… → Check the Python virtual environment → …
- Troubleshooting
- Calls uv, python and python3
- Tasks that involve Econometrics and empirical research
What it does
Check Env is an agent skill from brycewang-stanford/Auto-Empirical-Research-Skills. Verifies required tools (Quarto, uv, Python, R, Stata, TeX) and Jupyter kernels are installed. Use when setting up or troubleshooting.
Its SKILL.md is about 580 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Data & Analytics, covering Econometrics and empirical research, Jupyter notebooks and LaTeX. It works with Python and Jupyter. The repository describes itself as: 🔬 A curated collection of 23,000+ agent skills for empirical research across 8 social science disciplines. | 精选 23,000+ AI Agent 技能库，覆盖8大社会科学学科的实证研究。CoPaper.AI…
When your agent uses it
- Troubleshooting
- Tasks that involve Econometrics and empirical research
- Tasks that involve Jupyter notebooks
Example prompts
- “Use the check-env skill to verify required tools (Quarto, uv, Python, R, Stata, TeX) and Jupyter kernels are installed”
- “/check-env”
Requirements
- Python 3
- Pre-approved tools (allowed-tools): Bash, Read, Glob, Grep
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Check each required tool and report its version (or "not found")
- Check Jupyter kernels by running uv run jupyter kernelspec list and verify
- Check the Python virtual environment
- Check nbstata configuration (if nbstata kernel is present)
- Report a structured results table
- If any required check fails, provide the installation command or link to fix it.
What it can do on your machine
Read from SKILL.md and the folder at commit 9fa87d8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
uvpythonpython3gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Check Env loads about 578 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 172 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Glob, Grep
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 172 words (~578 tokens).
“Verify that all required tools and dependencies are installed and correctly configured.”
- name
- check-env
- allowed-tools
- Bash, Read, Glob, Grep
Files
Just SKILL.md in skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env of brycewang-stanford/Auto-Empirical-Research-Skills.
Open the folder on GitHubat commit 9fa87d8
Compare with similar skills
Check Env next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Check Env this skillbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~578 | Automated safety check: Notes | Custom licence | |
| Save Research Notebooknapjon/krisk | 117 | — | ~702 | Automated safety check: Pass | BSD-3-Clause | |
| Export ML Notebookprobabl-ai/skills | 138 | — | ~1k | Automated safety check: Pass | BSD-3-Clause | |
| Jupyter Live KernelRedWoodOG/Hermes-Desktop | 177 | 5 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Jupyter Live Kerneltaracodlabs/aiden | 851 | — | ~949 | Automated safety check: Pass | Apache-2.0 | |
| Bio Reporting Quarto ReportsGPTomics/bioSkills | 1.2k | 1 repos | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Export ML Notebook
probabl-ai/skills
Convert a jupytext percent %% Python file into an executed .ipynb with cell outputs.
Jupyter Live Kernel
RedWoodOG/Hermes-Desktop
Use a live Jupyter kernel for stateful, iterative Python execution via hamelnb.
Jupyter Live Kernel
taracodlabs/aiden
Stateful Jupyter kernel — variables persist across cells (hamelnb)
Bio Reporting Quarto Reports
GPTomics/bioSkills
Builds reproducible Quarto reports, presentations, and websites across R, Python, and Julia, with correct engine selection, cache-vs-freeze semantics, native cross-references, parameters, and…
Jupytext
ninehills/skills
Jupyter Notebook 创建与格式转换技能。当用户提到以下任何请求时必须使用：新建/创建 notebook、Jupyter notebook、.ipynb、jupytext、py:percent、 %% cell 格式、notebook 版本控制、paired notebook、notebook 转 Python、Python 转 notebook、用纯文本写…
More from brycewang-stanford/Auto-Empirical-Research-Skills
All 383 skills in this repoAer Consistency
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when auditing a finished or near-finished AER, AER:Insights, or AEJ manuscript for internal consistency: headline numbers across abstract, introduction, results, and tables…
Latex Paper En
brycewang-stanford/Auto-Empirical-Research-Skills
English LaTeX academic paper assistant for existing .tex projects.
Bayesian Workflow
brycewang-stanford/Auto-Empirical-Research-Skills
Opinionated Bayesian modeling workflow with PyMC and ArviZ. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.
Daily Paper Generator
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when the user asks to "generate daily paper", "search arXiv for EEG papers", "find EEG decoding papers", "review brain-computer interface papers", or wants to create paper…
Five Questions
brycewang-stanford/Auto-Empirical-Research-Skills
Deeply analyze any empirical economics PDF using the five-question framework (五问框架): research question, identification strategy, core estimand, robustness logic, and scholarly contribution.
Kaggle Research
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when a research task needs reproducible Kaggle discovery, metadata inspection, bounded public-data downloads, competition or kernel discovery, model discovery, or an…
Related
Categories
Questions about Check Env
What does Check Env do?
Verifies required tools (Quarto, uv, Python, R, Stata, TeX) and Jupyter kernels are installed. Check Env is an agent skill from brycewang-stanford/Auto-Empirical-Research-Skills. Verifies required tools (Quarto, uv, Python, R, Stata, TeX) and Jupyter kernels are installed.
When should I use Check Env?
Check Env fits situations like: troubleshooting; tasks that involve Econometrics and empirical research; tasks that involve Jupyter notebooks.
How do I install Check Env in Claude Code?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env -a claude-code`. Or copy the skill folder (skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env in brycewang-stanford/Auto-Empirical-Research-Skills) into .claude/skills/check-env in your project. Claude Code loads it when a task matches its description.
How do I install Check Env in Codex?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env -a codex`. Or copy the skill folder (skills/29-quarcs-lab-project20XXy/dot-claude/skills/check-env in brycewang-stanford/Auto-Empirical-Research-Skills) into .agents/skills/check-env in your project. Codex loads it when a task matches its description.
Can I use Check Env in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill check-env -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check-env, .gemini/skills/check-env, .github/skills/check-env and .opencode/skills/check-env in your project.
What does Check Env need to run?
Going by SKILL.md and its folder, Check Env needs the command-line tools its instructions call (uv, python, python3 and gh). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash, Read, Glob, Grep.
Does Check Env access the network?
SKILL.md contains no URLs. Its commands use uv and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Check Env safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Check Env use?
Check Env has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Check Env use?
About 578 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Check Env?
Skills that share tags, products or a category with Check Env: Save Research Notebook (napjon/krisk, 117 stars), Export ML Notebook (probabl-ai/skills, 138 stars), Jupyter Live Kernel (RedWoodOG/Hermes-Desktop, 177 stars) and Jupyter Live Kernel (taracodlabs/aiden, 851 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Check Env?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Auto-Empirical-Research-Skills, which has 4,542 GitHub stars. The repository holds 383 skills in this directory. The repository was last updated on October 5, 2026.
Source: brycewang-stanford/Auto-Empirical-Research-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.