using-git-worktrees

Use this whenever you need to create an isolated workspace.

Quality

67%

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

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, actionable, well-sequenced workflow with solid validation checkpoints and clean organization. Its main weakness is verbosity from over-emphasis and redundant sections.

Suggestions

Collapse the duplicated "Red Flags" content (it appears both inside the Maintaining section and as a top-level section) into one location.

Trim repeated emphasis markers like "*CRITICAL*" and "ABSOLUTELY CRITICAL"; a single clear statement conveys the same urgency with fewer tokens.

Fix the broken code fence on the `git worktree add` line, which is missing its closing backtick and breaks rendering of that command block.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence, but it is padded with repeated emphasis ("CRITICAL", "ABSOLUTELY CRITICAL") and a duplicated "Red Flags" section that could be tightened.	2 / 3
Actionability	It provides concrete, copy-paste-ready bash commands (git worktree add, the auto-detect setup block, test commands) plus a worked example workflow, all executable.	3 / 3
Workflow Clarity	A clear 7-step sequence is given with explicit validation checkpoints (.gitignore verification, baseline test run) and a feedback loop ("If tests fail: Report failures, ask whether to proceed").	3 / 3
Progressive Disclosure	The single SKILL.md is well-organized into clearly labeled sections (Quick Reference, Common Mistakes, Example Workflow, Red Flags) with no nested external references and no need for bundle files.	3 / 3
	Total	11 / 12 Passed

Description

50%

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 has an explicit trigger clause but is vague about what the skill actually does and never names git worktrees, making it weak and somewhat indistinct. It reads more as a usage prompt than a capability statement.

Suggestions

Name the concrete capability explicitly, e.g. "Create git worktrees to set up isolated working directories with their own branches."

Add natural trigger terms users would say, such as "git worktree", "worktree", "isolated branch", or "parallel branch workspace".

Combine what and when into one statement, e.g. "Creates isolated git worktrees for parallel branch work. Use when you need a separate working directory per branch or want to isolate changes from the main checkout."

Dimension	Reasoning	Score
Specificity	The phrase "create an isolated workspace" names a domain and one action, but offers only a single vague capability rather than multiple concrete actions.	2 / 3
Completeness	An explicit "Use this whenever..." trigger provides the "when", but the "what" ("create an isolated workspace") is vague and does not clearly describe the skill's concrete capabilities.	2 / 3
Trigger Term Quality	"isolated workspace" is a somewhat natural phrase, but the description omits the core terms a user would actually say ("worktree", "git worktree", "branch"), missing common variations.	2 / 3
Distinctiveness Conflict Risk	"isolated workspace" is generic enough to overlap with sandbox, virtualenv, or container skills, and the description never mentions git worktrees to carve out a distinct niche.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/FluidFramework
Path: .agency/plugins/nori/skills/using-git-worktrees/SKILL.md
Commit: f9f2007

Reviewed: about 7 hours 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.