CtrlK
BlogDocsLog inGet started
Tessl Logo

compute-env-setup

Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.

73

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A tight, well-structured workflow skill with excellent token efficiency and clear sequencing including a smoke-test checkpoint. The main improvement area is actionability: adding a couple of concrete example commands (install, smoke job) and an explicit fix-and-retry loop on smoke failure would lift it further.

Suggestions

Add one or two concrete example commands (e.g., a representative install command and a minimal smoke-job invocation) so the guidance is copy-paste ready, not just described.

Spell out the error-recovery loop explicitly: if the smoke job fails, diagnose the missing dependency, fix the environment note, and re-run the smoke before proceeding to the expensive job.

Consider naming where the environment note and smoke logs should be saved (path or convention) to make the 'done state' verifiable rather than implied.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a one-line intro, five numbered steps, and a defined done state, with no padding and no explanation of basic concepts Claude already knows.

5 / 5

Actionability

Steps name concrete options and mechanisms (virtualenv/conda, Modal, SSH/Slurm, Feynman Settings, smoke job), giving actionable guidance, but stop short of copy-paste commands or example install/smoke invocations, leaving minor gaps.

4 / 5

Workflow Clarity

Five clearly sequenced steps include a validation checkpoint (smoke job before the expensive job) and a done state that accounts for failure ('a precise missing dependency'), but the error-recovery loop when a smoke job fails is implied rather than an explicit fix-and-retry cycle.

4 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no external references (no references/scripts/assets bundle exists), and well-organized into intro, Workflow, and done-state sections, meeting the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

95%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.

A strong, concise description that clearly states both capability and explicit trigger conditions with comprehensive natural keywords. The only minor gap is that the 'what' is carried by a single setup verb rather than multiple distinct actions.

DimensionReasoningScore

Specificity

The description names the domain ('reproducible Feynman compute environment') and lists several concrete components (Python/R packages, GPU libraries, containers, Modal, SSH, caches, managed model runtime), but the 'what' rests on a single verb ('Set up') rather than multiple distinct actions, so it stops just short of comprehensive.

4 / 5

Completeness

It explicitly answers 'what' ('Set up a reproducible Feynman compute environment for research jobs') and 'when' with a concrete 'Use when...' clause listing specific triggers, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger terms are comprehensive and span the domain ('Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup'), covering the phrases a user would actually say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

The 'Feynman' qualifier plus distinctive triggers (Modal, SSH, managed model runtime, GPU libraries) carve a clear niche with minimal overlap risk against generic environment skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
companion-inc/feynman
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.