using-git-worktrees

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/using-git-worktrees/SKILL.md

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.

The content is a well-structured, actionable guide with strong workflow sequencing and explicit validation/feedback loops for the risky parts of worktree creation. Its main weakness is mild verbosity and redundancy across the mistake/red-flag sections plus a filler 'When to Use' line.

Suggestions

Merge 'Common Mistakes' and 'Red Flags' into a single section to remove overlapping content.

Replace the generic 'When to Use' line with a concrete trigger statement or remove it.

Define $LOCATION and $BRANCH_NAME (or note they are template variables) so the creation case statement is fully executable as written.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable guidance, but includes filler (the generic 'When to Use' line 'applicable to execute the workflow... described in the overview') and notable redundancy between 'Common Mistakes' and 'Red Flags' that could be tightened.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands (git check-ignore, git worktree add, dependency auto-detect), with a minor gap in the case statement using unset $LOCATION/$BRANCH_NAME template variables.	4 / 5
Workflow Clarity	The process is clearly sequenced (directory selection -> ignore verification -> creation -> baseline tests -> report) with explicit validation checkpoints and feedback loops (ignore check -> add to .gitignore + commit; tests fail -> report and ask), plus a Quick Reference checklist.	5 / 5
Progressive Disclosure	Well-organized into clear sections with no unnecessary external references (none needed), but the ~215-line body has minor organization gaps where 'Common Mistakes' and 'Red Flags' overlap and could be consolidated.	4 / 5
	Total	16 / 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 clearly conveys what git worktrees are but functions more as a feature definition than a skill capability statement, and lacks any explicit 'use when' trigger guidance. It is reasonably specific and distinct but not comprehensive.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working on multiple branches in parallel, creating an isolated workspace for a feature, or running tests on a separate branch without switching.'

Replace the definitional phrasing with action-oriented capability language (e.g. 'Creates and manages isolated git worktree workspaces...').

Expand trigger-term coverage with natural synonyms like 'worktree', 'parallel branches', and 'isolated checkout'.

Dimension	Reasoning	Score
Specificity	It names the domain ('Git worktrees') and 1-2 concrete capabilities ('create isolated workspaces', 'work on multiple branches simultaneously without switching'), but reads as a definition of the feature rather than an enumerated list of the skill's actions.	3 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	It surfaces relevant natural terms ('git worktrees', 'isolated workspaces', 'multiple branches') but omits common synonyms and variations users might say (e.g. 'worktree', 'parallel branches', 'checkout').	3 / 5
Distinctiveness Conflict Risk	'Git worktrees' is a fairly distinct niche; minor overlap risk only with closely related isolation/workspace skills, not a 5 because the phrasing is generic enough to brush against adjacent skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: fbdfd63

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.