CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

using-git-worktrees

Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.

Quality

74%

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 ./skills/using-git-worktrees/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-structured, highly actionable skill with an exemplary workflow: explicit sequencing, validation checkpoints, and error-recovery loops throughout. Its main weakness is redundancy — the core rules are repeated across four sections, and the Overview and 'When to Use' sections add no value — so a consolidation pass would meaningfully improve token efficiency.

Suggestions

Consolidate the overlapping restatements: Quick Reference, Common Mistakes, and Red Flags each repeat the same rules (ignore verification, directory priority, failing tests) — merge them into one section.

Delete the filler 'When to Use' section ("This skill is applicable to execute the workflow or actions described in the overview.") and the Overview sentence that duplicates the frontmatter description verbatim.

Make the creation snippet concretely executable by showing how $LOCATION and $BRANCH_NAME are determined, or simplify to direct per-location commands.

DimensionReasoningScore

Conciseness

Individual sections are tight and no git basics are over-explained, but the same rules are restated four times across the main flow, the Quick Reference table, Common Mistakes, Red Flags (and again in the Example Workflow); the Overview duplicates the frontmatter description verbatim and the trailing 'When to Use' section is filler. This matches anchor 3 ('mostly efficient but could be tightened') rather than 2, since the padding is repetition of actionable content, not concept explanation.

3 / 5

Actionability

Concrete, mostly executable commands throughout: 'git check-ignore -q .worktrees', 'git worktree add "$path" -b "$BRANCH_NAME"', 'project=$(basename "$(git rev-parse --show-toplevel)")', plus detection commands and a worked example transcript. Minor gaps keep it below anchor 5: the 'case $LOCATION' fragment relies on undefined variables ($LOCATION, $BRANCH_NAME) and the setup checks are disjoint if-fragments rather than a runnable sequence.

4 / 5

Workflow Clarity

The sequence (directory selection → ignore verification → creation → setup → baseline tests → report) is explicit, with genuine validation checkpoints ('MUST verify directory is ignored', baseline test run) and feedback loops for error recovery ('If NOT ignored: add to .gitignore, commit, proceed'; 'If tests fail: report failures, ask whether to proceed'). The Quick Reference table adds a checklist. This matches anchor 5 exactly; anchor 4's 'minor validation gaps' are absent.

5 / 5

Progressive Disclosure

No bundle files exist and the single-file structure is appropriate for this size: clear section headers (Directory Selection, Safety Verification, Creation Steps, Quick Reference, Example Workflow) make navigation easy. Not anchor 5, which requires well-signaled one-level-deep references (and the under-50-lines exception does not apply at ~220 lines); better than anchor 3 given the genuinely good organization. Minor gaps: the vague 'When to Use' section adds nothing.

4 / 5

Total

16

/

20

Passed

Description

65%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 clear, distinct, appropriately terse description that conveys the niche well, but it reads as a definition of git worktrees rather than a statement of what the skill does, and it entirely lacks a 'when to use' trigger clause. Adding an explicit 'Use when...' clause and the skill's concrete actions would lift both completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause, e.g., "Use when setting up an isolated workspace before implementing a feature, working on multiple branches in parallel, or when the user mentions worktrees."

Describe the skill's concrete actions rather than defining the git feature, e.g., "Sets up git worktrees: selects the worktree directory, verifies it is gitignored, runs project setup, and confirms a clean test baseline."

Include a few more natural trigger terms such as "parallel branches" or "isolated workspace" variants to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Git worktrees") and 1-2 concrete actions ("create isolated workspaces", "work on multiple branches simultaneously without switching"), but does not list the several specific actions the skill actually performs (directory selection, gitignore verification, project setup, test baseline). It matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') rather than 4, which requires several listed actions, and rather than 2, since the actions given are concrete rather than generic.

3 / 5

Completeness

It clearly answers 'what' (creates isolated workspaces sharing the repository for simultaneous branch work) but contains no 'Use when...' clause or equivalent trigger guidance — the judging guidelines explicitly cap completeness at 3 for this. Not 4 because 'when' is entirely absent rather than under-specified; not 2 because the 'what' is clear, not vague.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "Git worktrees", "isolated workspaces", "multiple branches", "without switching" — phrases a user would naturally say when needing this skill. A few natural terms are missing (e.g., "parallel work", "sandbox", "worktree add"), keeping it below anchor 5's comprehensive synonym coverage, but it is clearly above anchor 3's single-keyword example ('Works with PDF files').

4 / 5

Distinctiveness Conflict Risk

"Git worktrees" is a highly distinctive trigger term occupying a clear niche; "isolated workspaces sharing the same repository" ties it unambiguously to this feature. A user mentioning worktrees or wanting parallel branch work would land on this skill, with minimal risk of it firing for unrelated skills. Anchor 5 ('clear niche with distinct triggers; minimal conflict risk') is the best fit.

5 / 5

Total

15

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/using-git-worktrees/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.