CtrlK
BlogDocsLog inGet started
Tessl Logo

worktree-make-dev

Set up a dev environment in an existing worktree (make dev + copy secrets)

59

Quality

68%

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/worktree-make-dev/SKILL.md
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.

The body is concise, well-structured, and action-oriented with a clear workflow and stop-on-failure guard. Minor gaps: the command placeholder is inconsistent with the documented $ARGUMENTS and there is no error-recovery feedback loop.

Suggestions

Use the $ARGUMENTS token consistently in the script command instead of the <worktree-path> placeholder to keep it copy-paste ready.

Add an explicit feedback loop after script failure (e.g. re-run after fixing the reported error) to strengthen workflow clarity.

Note where to find or inspect tools/setup_worktree_env.sh so failures can be diagnosed rather than only reported.

DimensionReasoningScore

Conciseness

Lean body with no padding; assumes Claude's competence and every line earns its place.

5 / 5

Actionability

Provides the concrete script invocation and a parseable output contract, but the command uses a placeholder <worktree-path> rather than $ARGUMENTS and the script itself is an opaque bundle.

4 / 5

Workflow Clarity

Clear two-step sequence with a stop-on-failure checkpoint and a defined reporting contract, but no retry/fix feedback loop after a script failure.

4 / 5

Progressive Disclosure

Well-organized sections delegating the heavy logic to the bundled script; appropriately shallow reference depth for a short skill.

5 / 5

Total

18

/

20

Passed

Description

51%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 specific and distinct about what it does, but lacks an explicit 'Use when...' trigger clause, capping completeness. Trigger terms are present but lean technical rather than natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when preparing an existing worktree for development.'

Include natural user-facing phrasing like 'dev environment' or 'set up dev env' alongside the technical terms.

Clarify scope boundary (existing worktree only, not creation) to reduce overlap with worktree-creation skills.

DimensionReasoningScore

Specificity

Names two concrete actions ('make dev' and 'copy secrets') in the dev-env setup domain, with minor gaps (no mention of env teardown or verification).

4 / 5

Completeness

Clear 'what' (set up dev env in a worktree via make dev + copy secrets) but no 'Use when...' trigger clause, capping completeness at 3.

3 / 5

Trigger Term Quality

Contains 'worktree' and 'secrets' but lacks natural user phrasing like 'set up dev environment' or 'dev env'; leans on technical jargon.

2 / 5

Distinctiveness Conflict Risk

Tightly scoped to worktree dev-env setup; minimal overlap risk with other skills, though 'make dev' is a common phrase.

4 / 5

Total

13

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
dlt-hub/dlt
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.