CtrlK
BlogDocsLog inGet started
Tessl Logo

using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

64

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/using-git-worktrees/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

This is a well-crafted skill with strong actionability and workflow clarity — the detection-first approach with explicit fallback chains and validation checkpoints is excellent. The main weakness is moderate redundancy: the Quick Reference table, Common Mistakes, and Red Flags sections substantially overlap with each other and with the main workflow, inflating token cost. The content could be tightened by consolidating these trailing sections.

Suggestions

Consolidate the Common Mistakes, Red Flags, and Quick Reference sections into a single compact reference — they currently repeat the same guidance three different ways, adding ~60 lines of redundant content.

Consider moving the Quick Reference table to a separate bundle file (e.g., REFERENCE.md) to keep the main SKILL.md focused on the workflow steps.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy — the Quick Reference table largely duplicates information already covered in the steps, and the Common Mistakes and Red Flags sections overlap significantly. The "Always/Never" lists at the end repeat guidance from the workflow. However, the core workflow steps are well-written without excessive explanation of concepts Claude already knows.

2 / 3

Actionability

The skill provides concrete, executable bash commands throughout — detection checks, directory selection, worktree creation, project setup, and test verification are all copy-paste ready. Decision logic is explicit with clear conditionals (if GIT_DIR != GIT_COMMON, if check-ignore fails, etc.).

3 / 3

Workflow Clarity

The multi-step process is clearly sequenced (Step 0 → 1a → 1b → 3 → 4) with explicit validation checkpoints: submodule guard in Step 0, ignore verification before creation, sandbox fallback on permission error, and baseline test verification with a feedback loop (report failures, ask whether to proceed). The priority ordering for directory selection is unambiguous.

3 / 3

Progressive Disclosure

The content is well-structured with clear sections and a useful quick reference table, but it's a long monolithic file (~180 lines of substantive content) with no bundle files. The Common Mistakes, Red Flags, and Quick Reference sections could be split into a separate reference file to keep the main skill leaner. However, given no bundle files exist, the single-file approach is acceptable if not ideal.

2 / 3

Total

10

/

12

Passed

Description

75%

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 good completeness with explicit 'Use when' triggers and a distinct niche around workspace isolation. However, it could be more specific about the concrete actions performed and include more natural trigger terms that users would actually say. The phrase 'ensures an isolated workspace exists' is somewhat vague about what the skill actually does mechanically.

Suggestions

List specific concrete actions like 'Creates git worktrees, sets up isolated directories, configures branches for parallel feature development'.

Add more natural trigger terms users would say, such as 'branch', 'new feature', 'parallel work', 'separate workspace', 'worktree'.

DimensionReasoningScore

Specificity

It mentions 'isolated workspace', 'native tools', and 'git worktree fallback' which name the domain and some actions, but doesn't list concrete specific actions like 'create worktree', 'clone repository', or 'set up branch'. The actual capabilities are vague ('ensures an isolated workspace exists').

2 / 3

Completeness

It explicitly answers both 'what' (ensures an isolated workspace exists via native tools or git worktree fallback) and 'when' (when starting feature work that needs isolation or before executing implementation plans) with a clear 'Use when...' clause.

3 / 3

Trigger Term Quality

Includes some relevant terms like 'feature work', 'isolation', 'workspace', 'git worktree', and 'implementation plans', but misses common user phrases like 'branch', 'new feature', 'parallel development', 'separate directory', or 'working copy'. Users might not naturally say 'isolation from current workspace'.

2 / 3

Distinctiveness Conflict Risk

The description targets a clear niche — workspace isolation via worktrees for feature development. This is specific enough to be distinguishable from general git skills, branching skills, or project setup skills.

3 / 3

Total

10

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
obra/superpowers
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.