CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

environment-triage

Environment Triage

Quality

60%

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 ./.claude/skills/environment-triage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%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 an exemplary lean, actionable troubleshooting skill: executable diagnostic commands, a concrete fix, and clear do/don't guidance with no wasted tokens. The only real gap is workflow closure — the destructive venv rebuild is not followed by an explicit re-verification step, leaving the fix→verify feedback loop implicit.

Suggestions

Add an explicit post-fix verification step to the Common Fix, e.g. 'Then confirm the import now resolves: uv run python -c "import <package>; print(<package>.__version__)"', closing the validate→fix→retry loop around the destructive venv rebuild.

Present the DO checks as an ordered diagnostic sequence (1→4) so the diagnose-then-fix workflow is explicit rather than implied by section ordering.

DimensionReasoningScore

Conciseness

The ~43-line body is lean and every section earns its place; the single conceptual line ('System Python is not authoritative if uv/venv selects a different interpreter') is the non-obvious key insight rather than a tutorial on concepts Claude already knows. No padding or verbosity anywhere — a clear anchor 5.

5 / 5

Actionability

Every command is concrete and executable — 'uv run python --version', 'cat .python-version', 'uv pip show <package>', 'uv run python -c "import <package>..."', and the copy-paste-ready Common Fix ('echo "3.13" > .python-version; rm -rf .venv && uv venv && uv sync --all-extras') — covering the common failure cases, matching anchor 5.

5 / 5

Workflow Clarity

The DO checks are listed in a sensible diagnostic order and DON'T supplies sequencing ('Debug further before checking interpreter version'), but the Common Fix performs a destructive venv rebuild ('rm -rf .venv && uv venv && uv sync') with no explicit post-fix re-verification step — the validate→fix→retry feedback loop is only implicit. Per the rubric's feedback-loop guidance for destructive operations this caps the score at 3, not a 4 ('most checkpoints present') because the fix's verification checkpoint is missing rather than minor.

3 / 5

Progressive Disclosure

No bundle files exist or are needed; the skill is under 50 lines, single-task, and organized into clear sections (Pattern, DO, Common Fix, DON'T, Source Sessions). Per the rubric's simple-skill note, well-organized sections alone warrant a 5 with no external references required.

5 / 5

Total

18

/

20

Passed

Description

16%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 just a two-word title with no actions, no trigger clause, and no natural user vocabulary. It communicates a vague domain at best and would rarely surface this skill when needed. The strong body content is completely undersold by this frontmatter.

Suggestions

Add concrete actions to the description, e.g. 'Diagnoses uv/pip environment mismatches by checking the actual interpreter, pinned Python version, and package imports, and rebuilds the venv when the pinned version is wrong.'

Add an explicit 'Use when...' trigger clause with natural user phrases, e.g. 'Use when uv sync or pip install fails, a package import errors out, or a dependency is skipped due to a python_version marker.'

Include the natural trigger terms users would say — 'uv sync', 'pip install', 'wrong Python version', 'import error', '.python-version' — to improve both trigger quality and distinctiveness.

DimensionReasoningScore

Specificity

The description is only the title 'Environment Triage' — it names a domain but contains no action verbs at all, making it weaker than anchor 2's 'Processes PDF files' yet more domain-specific than the pure abstraction of anchor 1's 'Helps with documents'.

2 / 5

Completeness

Neither 'what' (no concrete actions are described) nor 'when' (no 'Use when...' clause or equivalent trigger guidance) is present — the description matches anchor 1, 'missing both what and when'.

1 / 5

Trigger Term Quality

No natural phrases a user would actually say when hitting this problem ('uv sync fails', 'pip install not working', 'wrong Python version'); only the single generic keyword 'environment' is present. Not a 1 because 'environment' at least gestures at the domain without being pure jargon.

2 / 5

Distinctiveness Conflict Risk

'Environment' is very broad (shell env vars, Docker environments, virtual environments, CI environments), creating high overlap risk with many skills, matching anchor 2's 'very broad; high overlap risk'. It is not a 1 because 'triage' does narrow it toward debugging rather than conflicting with virtually any skill.

2 / 5

Total

7

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (18 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/environment-triage/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.