parallel-worktrees

Create and manage git worktrees for parallel coding sessions with zero dead time. Use when blocked on tests, builds, wanting to work on multiple branches, context switching, or exploring multiple approaches simultaneously.

1.13x

Quality

81%

Does it follow best practices?

Impact

100%

1.13x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

72%

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

A solid, practical skill that provides actionable git worktree commands and covers both Claude Code and general editor workflows. Its main weakness is that the workflow section lacks integrated validation checkpoints (the safety check for uncommitted changes is buried in Guardrails rather than being part of the numbered workflow). Minor conciseness improvements could be made by trimming the 'When to Parallelize' table which largely restates the trigger section.

Suggestions

Integrate the 'verify changes are committed' guardrail directly into the Workflow section as an explicit step before worktree removal (e.g., step 4: 'Check for uncommitted changes: `git -C ../project-feat status`, then remove: `git worktree remove ../project-feat`').

Consider merging the 'When to Parallelize' table into the Trigger section to reduce redundancy and save tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but has some unnecessary content. The 'When to Parallelize' table and 'Usage Pattern' section are somewhat redundant with the trigger section. The 'Claude Code Extras' section adds useful tool-specific info but the bullet about Ctrl+F/Ctrl+B feels tangential to the core worktree skill.	2 / 3
Actionability	Provides fully executable git commands throughout, including creation, listing, and cleanup. The quick start gives copy-paste ready commands for both Claude Code and Cursor workflows, and the Commands section is a complete reference of real git worktree commands.	3 / 3
Workflow Clarity	The workflow steps are listed but the validation checkpoint in Guardrails ('verify changes are committed') is separated from the workflow sequence rather than integrated as an explicit step before removal. For a workflow involving potential data loss (removing worktrees with uncommitted changes), the feedback loop should be inline in the workflow.	2 / 3
Progressive Disclosure	For a skill of this size and scope (single-purpose, under 100 lines, no bundle files), the content is well-organized into clearly labeled sections with a logical progression from quick start to details to guardrails. No external references are needed and none are artificially created.	3 / 3
	Total	10 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description with excellent trigger coverage and clear 'what/when' structure. The main weakness is that the capability description could be more specific about the concrete actions beyond 'create and manage'. The trigger terms are well-chosen and cover realistic user scenarios naturally.

Suggestions

Expand the capability list with more specific actions, e.g., 'Create, list, remove, and switch between git worktrees' instead of the vaguer 'create and manage'.

Dimension	Reasoning	Score
Specificity	Names the domain (git worktrees) and mentions 'create and manage' as actions, but doesn't list specific concrete actions like creating worktrees, listing them, removing them, linking branches, etc. 'Manage' is somewhat vague.	2 / 3
Completeness	Clearly answers both 'what' (create and manage git worktrees for parallel coding sessions) and 'when' (explicit 'Use when' clause covering blocked on tests, builds, multiple branches, context switching, exploring multiple approaches).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'git worktrees', 'parallel coding', 'blocked on tests', 'builds', 'multiple branches', 'context switching', 'multiple approaches'. These cover a wide range of scenarios a user would naturally describe.	3 / 3
Distinctiveness Conflict Risk	Git worktrees is a very specific niche that is unlikely to conflict with general git skills or other coding skills. The trigger terms like 'worktrees', 'parallel coding sessions', and 'zero dead time' are distinctive enough to avoid false matches.	3 / 3
	Total	11 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: rohitg00/pro-workflow
Commit: 5c313e2

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