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.
88
81%
Does it follow best practices?
Impact
100%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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 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 |
Implementation
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 concrete commands and covers the key use cases for git worktrees. Its main weakness is the disconnect between the vague 'Workflow' section and the concrete 'Commands' section — merging these into a single workflow with validation checkpoints (especially around cleanup) would strengthen it. Minor redundancy between sections could be tightened.
Suggestions
Merge the 'Workflow' and 'Commands' sections into a single numbered workflow with explicit validation steps, e.g., '4. Verify changes committed: `git -C ../project-feat status` 5. Only then remove: `git worktree remove ../project-feat`'
Remove the generic 'Workflow' steps (e.g., 'Create a worktree for the parallel task') and replace with the actual commands already listed in the Commands section to eliminate redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — the 'Workflow' section is vague and adds little beyond what 'Commands' already shows. The 'When to Parallelize' table, while useful, restates the trigger section. The 'Usage Pattern' section is somewhat obvious given the commands above it. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready commands for every operation (creating, listing, removing worktrees). The quick start section gives concrete commands for both Claude Code and Cursor workflows, and the commands section covers all common operations. | 3 / 3 |
Workflow Clarity | The workflow section is vague ('Create a worktree for the parallel task') rather than giving explicit steps with commands. The guardrails section mentions verifying changes are committed before removing, but this isn't integrated into the workflow as an explicit validation checkpoint — it's separated and easy to miss. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope, the content is well-organized into clearly labeled sections (Quick Start, Commands, Guardrails, etc.) with logical progression. No external references are needed, and the structure supports quick scanning. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- rohitg00/pro-workflow
- Commit
9df6af8
- 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.