ce-worktree

Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch/PR/commit to work on it in isolation. Use when starting isolated work or isolating an existing ref; detects existing isolation first.

Quality

96%

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

Quality

Content

92%Weight 40%Scale 1-3

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

A high-quality, actionable skill with an excellent detect-first workflow and concrete executable commands, assuming Claude's competence without padding basics. The one weaker spot is progressive disclosure: detailed edge-case and per-harness guidance lives inline in a single long file rather than being split into signaled reference files.

Suggestions

Move the detailed PR-checkout variants (fork-safe detached-then-`gh pr checkout`, the already-checked-out edge cases) and the per-harness blocking-question tool list into a reference file (e.g. references/edge-cases.md), keeping SKILL.md as a tighter overview that links to it.

Pull the 'Other worktree operations' and 'Troubleshooting' sections into a separate reference so the main body stays focused on the detect -> native-tool -> git-fallback core flow.

Signal each extracted reference explicitly in-place (e.g. '**PR checkout edge cases**: See [references/edge-cases.md]') so navigation is one level deep and clearly marked.

Dimension	Reasoning	Score
Conciseness	Lean and information-dense with no padding or explanation of basics Claude already knows; every extended passage addresses a non-obvious gotcha (resolved-path comparison, trailing-slash check-ignore, detached FETCH_HEAD orphaning commits). It is dense, but each token earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands throughout — `git rev-parse --absolute-git-dir`, `git worktree add -b <branch-name> .worktrees/<branch-name> origin/<from-branch>`, `git fetch origin pull/<n>/head:pr-<n>` — with concrete mode-specific variants rather than pseudocode.	3 / 3
Workflow Clarity	Clear detect -> native-tool -> git-fallback sequence with explicit validation checkpoints (resolved-path isolation check, `git check-ignore` before creation, non-fatal fetch handling, already-checked-out rule, blocking user decision on permission failure) and error-recovery feedback loops for a risky operation.	3 / 3
Progressive Disclosure	Well-sectioned and self-contained, but at ~87 lines it exceeds the simple-skill (<50 line) carve-out and keeps detailed edge-case content inline (fork-safe PR checkout variants, per-harness blocking-tool enumeration, troubleshooting) that could instead be split into one-level-deep reference files. It is not merely an overview pointing to deeper materials.	2 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 crisp, well-targeted description that states concrete capabilities, gives an explicit Use-when trigger, and occupies a distinct niche with low conflict risk. Third-person voice is maintained throughout with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "create a new branch for fresh work, or attach a worktree to an existing branch/PR/commit to work on it in isolation" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("Set up isolated git worktrees ... create a new branch ... or attach a worktree") and when ("Use when starting isolated work or isolating an existing ref"), with an explicit Use-when trigger clause present.	3 / 3
Trigger Term Quality	Covers natural terms a developer would say — "git worktrees", "branch", "PR", "commit", "isolated work", "isolating an existing ref" — giving good coverage of natural trigger language. The lone jargon term "ref" is offset by the plain-language alternatives alongside it.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche — isolated git worktree setup with a detect-first twist — and its triggers (worktree isolation, isolating an existing ref) are unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: EveryInc/compound-engineering-plugin
Path: skills/ce-worktree/SKILL.md
Commit: a9f6d53

Reviewed: 7 days 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.