CtrlK
BlogDocsLog inGet started
Tessl Logo

wt

Create a git worktree in worktree/ subdirectory with up-to-date master

80

2.30x
Quality

73%

Does it follow best practices?

Impact

90%

2.30x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/wt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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, executable one-shot script for a simple single-purpose skill — fully copy-paste ready with a clear step order and useful cleanup notes. The only gap is the absence of explicit validation or error-recovery steps for the update/checkout steps, which keeps workflow clarity at 4.

DimensionReasoningScore

Conciseness

The ~35-line body contains only a heading, one complete script, and three terse notes — no git-concept explanations, no padding, and every comment is functional. It is lean and assumes Claude's competence, matching the top anchor.

5 / 5

Actionability

The body provides a single fully executable bash script (cd to toplevel, checkout/pull master, worktree add, submodule update, cd into the worktree) that is copy-paste ready and uses $ARGUMENTS consistently, covering the whole task. The Notes add concrete remove/list commands.

5 / 5

Workflow Clarity

The sequence is clearly ordered (return to root → update master → create worktree → init submodules → navigate) and ends with a confirmation echo of location and branch, which is a light checkpoint. However, there is no validation that the pull or worktree creation succeeded and no error-recovery guidance, so it falls at 'clear sequence with most checkpoints present; minor validation gaps' rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no bundle files needed; content is split into 'Execution' and 'Notes' sections that are well-organized and easy to navigate. Per the rubric's simple-skill guideline, this warrants the top score with just well-organized sections.

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 states a clear, concrete capability but omits any 'when to use this' trigger guidance, which caps its completeness and limits natural trigger-term coverage. It is specific enough to be distinguishable, yet terse enough to miss the synonyms users would naturally say.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to create a worktree, isolate changes in a parallel branch, or work on a branch without disturbing the current checkout.'

Include natural trigger terms and synonyms such as 'worktree', 'isolate', 'parallel branch', 'sandbox', and 'new branch' so the skill matches how users actually phrase the request.

State the follow-up capabilities explicitly (e.g. branch creation from latest master, submodule initialization, and cleanup/removal) to round out action coverage.

DimensionReasoningScore

Specificity

The phrase 'Create a git worktree in worktree/ subdirectory with up-to-date master' names the domain (git worktree) and one concrete action with location and freshness details, but does not list several specific actions. This matches the anchor for naming the domain with 1-2 concrete actions without comprehensive coverage, and is not generic enough to score 2.

3 / 5

Completeness

The 'what' is clear (create a worktree with an up-to-date master), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The 'when' is entirely absent rather than weakly implied, so it cannot reach 4.

3 / 5

Trigger Term Quality

'git worktree' is a natural keyword a user would say, but coverage stops there — common variations and synonyms like 'isolate', 'parallel work', 'sandbox', or 'new branch' are missing. This sits at 'some relevant keywords but missing common variations', below the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

'git worktree' identifies a clear niche that is mostly distinct from general skills, with only minor overlap risk against generic git/branching skills given the terse phrasing. It does not reach 5 because without any trigger phrasing it is less clearly distinguishable from other git workflow 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
homeassistant-ai/ha-mcp
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.