Snapshot the computational environment for a replication package — detects the analysis stack (R / Stata / Python) and emits the right lockfiles (renv.lock + sessionInfo.txt, requirements.txt / environment.yml / uv.lock, Stata version + ado package list), records seeds and RNG kind, optionally writes a pinning Dockerfile, and produces a paste-ready "Computational requirements" block. Use when user says "capture the environment", "snapshot my dependencies", "pin the versions", "make a renv.lock / requirements.txt", "make this byte-reproducible", or before releasing a replication package to openICPSR / the AEA Data Editor.
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/capture-environment/SKILL.mdThis skill's instructions live in .claude/skills/capture-environment/SKILL.md.
Read that file now and follow it, with the files it points to. Read AGENTS.md
first if you have not already.
It was written for Claude Code. Running it from Codex, Antigravity or another agent:
$ARGUMENTS, use what the user asked for..claude/agents/ (through the
Agent or Task tool), do that step where it appears in the procedure: never later, and never
skip it. A step that gates what follows still gates it (/commit runs its verifier before it
commits). Read the agent's file for what the step checks./verify-claims for citations) before
relying on it.allowed-tools, model, effort, argument-hint and
disable-model-invocation in the source's frontmatter configure Claude Code. Ignore them.AGENTS.md
yourself; the git pre-commit gate and CI still apply to your commits.pedrohcgs/claude-code-my-workflow
fe70774
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.