CtrlK
BlogDocsLog inGet started
Tessl Logo

using-git-worktrees

Use this whenever you need to create an isolated workspace.

49

Quality

53%

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

Quality

Content

81%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 strong, executable workflow with clear sequencing and robust validation/recovery checkpoints. Its main weaknesses are minor redundancy across overlapping summary sections and one malformed command snippet.

Suggestions

Fix the unclosed code fence/quote on the 'git worktree add' command (line 27) so the snippet is copy-paste ready.

Consolidate the overlapping Quick Reference, Common Mistakes, and Red Flags sections to reduce redundancy and save tokens.

DimensionReasoningScore

Conciseness

The body is mostly lean with concrete commands and little padding of concepts Claude already knows; there is some redundancy across the Quick Reference, Common Mistakes, and Red Flags sections that keeps it just below the lean anchor 5.

4 / 5

Actionability

It provides concrete, executable bash throughout (ls, grep, git worktree add, npm test, etc.) with mostly copy-paste-ready snippets; a minor gap (the unclosed quote in the 'git worktree add' command on line 27) prevents a 5.

4 / 5

Workflow Clarity

The 7-step sequence is clearly numbered with explicit validation checkpoints (gitignore verification before creation, baseline test run, failure reporting and permission gate) plus a recovery loop for accidentally exiting the worktree, matching the anchor with feedback loops and checklists.

5 / 5

Progressive Disclosure

As a single-file skill with no bundle files, it is well-organized into clearly labeled sections (Maintaining Working Directory, Quick Reference, Common Mistakes, Example Workflow); with no external references to split out it sits just below the one-level-deep reference anchor 5.

4 / 5

Total

17

/

20

Passed

Description

25%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 too vague and generic: it states a broad goal ('isolated workspace') without naming git worktrees or any concrete capability, and provides only weak trigger guidance. It is unlikely to fire precisely for the intended skill.

Suggestions

Name the concrete capability explicitly, e.g. 'Create git worktrees to get an isolated working copy on a separate branch'.

Add natural trigger terms users actually say, such as 'worktree', 'parallel branch', 'isolated branch', or 'work on a feature without affecting main'.

Clarify the 'when' with concrete scenarios, e.g. 'Use when you need to work on a feature in isolation, run parallel branches, or avoid polluting the main checkout'.

DimensionReasoningScore

Specificity

The phrase 'create an isolated workspace' names the goal but offers no concrete actions or mechanisms (e.g., git worktree, branch); it is above the purely-vague anchor 1 but below the domain-plus-action anchor 3.

2 / 5

Completeness

The 'when' clause is present ('Use this whenever you need to create an isolated workspace') but the 'what' is barely articulated — no mention of git worktrees or the actual operation — placing it between anchor 2 and 3 and closer to 2.

2 / 5

Trigger Term Quality

'isolated workspace' is a single generic phrase; it lacks the natural terms users would say (worktree, branch, sandbox, parallel branch), matching the one-or-two-generic-keywords anchor.

2 / 5

Distinctiveness Conflict Risk

'Isolated workspace' is very broad and could trigger for sandboxing, containers, or virtualenvs; high overlap risk with many related skills, matching the very-broad anchor 2.

2 / 5

Total

8

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/FluidFramework
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.