CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

worktree-make-dev

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

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 ./.claude/skills/worktree-make-dev/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 instruction: one unambiguous step, explicit error handling, and a fully specified report format covering all three secret-source outcomes. The only improvement is tying the command placeholder to $ARGUMENTS and stating the expected working directory.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with zero padding: a one-line goal ("Prepare the worktree at $ARGUMENTS for development"), a single executable command, a short parsing rule, and a compact report template. Every token earns its place and no concepts Claude already knows are explained. Clearly anchor 5, not 4, since there is nothing to trim.

5 / 5

Actionability

Guidance is concrete and near copy-paste ready: the command `bash tools/setup_worktree_env.sh <worktree-path>`, the exact parse key `SECRETS_SOURCE=`, three enumerated outcomes, and an exact report template. Falls to anchor 4 rather than 5 due to a minor gap: the command's `<worktree-path>` placeholder is never explicitly tied to `$ARGUMENTS`, and the relative `tools/` path assumes an unstated working directory.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill whose one action is unambiguous (run the setup script), with an explicit failure checkpoint — "If it fails, report the error and stop" — plus a structured reporting step. Environment setup is non-destructive/non-batch, so the validation cap does not apply, and the simple-skill exception holds: anchor 5.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (references/, scripts/, assets/ are absent), and needs none — the referenced `tools/setup_worktree_env.sh` lives in the target repo, not the skill bundle. Sections are clear and well-organized, which per the simple-skill guideline earns anchor 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 delivers a clear, specific "what" with concrete actions and a well-defined niche, but it omits any "when to use" trigger guidance and under-covers natural search terms and synonyms. It is a solid mid-range description that would rarely trigger spuriously yet might not be surfaced when needed.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up a new or existing git worktree for development, running make dev, or copying secrets into a worktree."

Include natural synonyms and variations users would say — "development environment", "git worktree", "set up", "bootstrap" — to improve trigger-term coverage.

Briefly enumerate what setup covers beyond the parenthetical (e.g., dependency installation, secrets.toml configuration) to raise specificity from two actions to a fuller list.

DimensionReasoningScore

Specificity

"Set up a dev environment in an existing worktree" names the domain and the parenthetical "make dev + copy secrets" gives two concrete actions, but coverage is not comprehensive — nothing beyond those two actions is described. Matches anchor 3 (domain + 1-2 concrete actions), not 4, which requires several specific actions.

3 / 5

Completeness

The "what" is clear and specific ("Set up a dev environment in an existing worktree (make dev + copy secrets)"), but there is no "Use when..." clause or any equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords are present ("dev environment", "worktree", "make dev", "secrets") but common variations users would naturally say are missing ("development setup", "git worktree", "set up environment"). Fits anchor 3 (some relevant keywords, missing variations/synonyms) rather than 4's fuller coverage.

3 / 5

Distinctiveness Conflict Risk

"in an existing worktree" combined with "make dev" carves a distinct niche with only minor overlap risk against generic environment-setup or bootstrap skills. Fits anchor 4 (mostly distinct, minor overlap) rather than 5, since "set up a dev environment" alone would collide with broader setup skills.

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.

Validation — 15 / 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

Path

.claude/skills/worktree-make-dev/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.