CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

capture-environment

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.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/capture-environment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a generated redirect stub: all actual instructions live in a source file that is not part of this bundle, so the skill as shipped provides no task guidance, no workflow, and no navigable structure. Conciseness is the only relative strength, since the stub itself is lean and free of padding.

Suggestions

Inline the actual instructions (or at least a Quick start section covering stack detection and lockfile generation) into the SKILL.md body instead of redirecting to an external .claude/skills path that consumers of the bundle cannot resolve.

Add bundle files under references/ (e.g., language-specific lockfile recipes for R, Python, Stata) and reference them one level deep with clear section headers, replacing the dangling '../../../.claude/...' pointer.

Include a numbered workflow with validation steps (e.g., verify each generated lockfile against the detected stack before writing the Computational requirements block) so the multi-step capture process has explicit checkpoints.

DimensionReasoningScore

Conciseness

The body is ~25 lines with no explanations of concepts Claude already knows, and each portability bullet is load-bearing for cross-agent use. Minor over-explanation in the multi-agent notes ('never later, and never skip it') keeps it below the 'every token earns its place' anchor.

4 / 5

Actionability

The body offers no executable guidance for the actual task — 'This skill's instructions live in [.claude/skills/capture-environment/SKILL.md]... Read that file now and follow it' — and that referenced file does not resolve from this bundle (no .claude directory or bundle files exist), leaving only a high-level redirect with no specific steps, which matches the 'minimal concrete guidance' anchor.

2 / 5

Workflow Clarity

Only a navigation sequence exists (read AGENTS.md first, then read the source skill file and follow it); the capture-environment workflow itself — stack detection, lockfile emission, seed recording — is entirely absent from the body, with no validation checkpoints. The redirect sequence is at least coherent, placing it above anchor 1 but well below a real workflow.

2 / 5

Progressive Disclosure

There are no references/, scripts/, or assets/ directories, and the single reference points outside the bundle via '../../../.claude/skills/capture-environment/SKILL.md', which is unresolvable, with further indirection promised ('with the files it points to'). References are effectively buried and non-navigable, matching the 'references are buried' anchor rather than the partially-organized anchor 3.

2 / 5

Total

10

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it enumerates concrete per-language outputs, records seeds/RNG state, and closes with an explicit multi-phrase trigger list covering user wording and target venues. It is dense but every clause is load-bearing rather than padded, so verbosity is not penalized.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage: 'detects the analysis stack (R / Stata / Python)', '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'. Every artifact is named per-language, leaving no coverage gaps that would drop it to anchor 4.

5 / 5

Completeness

Explicitly answers both what (full capability list) and when ('Use when user says "capture the environment"...') with concrete trigger phrases, matching the top anchor exactly; the when-clause is not merely implied, so 4 does not fit.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — 'capture the environment', 'snapshot my dependencies', 'pin the versions', 'make a renv.lock / requirements.txt', 'make this byte-reproducible', 'openICPSR / the AEA Data Editor' — with synonyms and exact file names, matching the comprehensive anchor rather than the 'a few natural terms missing' anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — replication packages for social-science data journals (openICPSR, AEA Data Editor) with language-specific lockfile triggers — making conflict with generic environment or packaging skills minimal.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

pedrohcgs/claude-code-my-workflow

Path

.agents/skills/capture-environment/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.