code-exec-skills
7 code execution skills. Trigger: running code, interactive notebooks, Jupyter, Colab, sandboxed execution. Design: execution environment guides with setup instructions and best practices.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill code-exec --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.
# Code Execution — 7 Skills Select the skill matching the user's need, then `read` its SKILL.md. | Skill | Description | |-------|-------------| | [google-colab-guide](./google-colab-guide/SKILL.md) | Run and manage Google Colab notebooks for Python and ML research | | [jupyter-notebook-guide](./jupyter-notebook-guide/SKILL.md) | Best practices for computational research notebooks with reproducibl
What does the code-exec-skills skill do?
7 code execution skills. Trigger: running code, interactive notebooks, Jupyter, Colab, sandboxed execution. Design: execution environment guides with setup instructions and best practices.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill code-exec --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.