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 solid skill description with excellent trigger coverage and a clear 'Use when' clause that covers multiple realistic scenarios. The main weakness is that the 'what' portion could be more specific about the concrete actions beyond 'create and manage'. Overall it performs well for skill selection purposes.
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 are terms users would naturally use when needing this skill. | 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 triggers are distinct and clearly scoped to worktree-related workflows. | 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 weaknesses are a somewhat redundant workflow section that doesn't add value beyond the commands reference, and missing explicit validation checkpoints integrated into the workflow steps (e.g., verifying commit status before cleanup should be a numbered step, not just a guardrail note).
Suggestions
Integrate the guardrail about checking `git status` directly into the Workflow section as an explicit validation step before removal (e.g., '4. Verify changes committed: `git -C ../project-feat status` 5. Only when clean: `git worktree remove ../project-feat`').
Merge the vague 'Workflow' section into the 'Commands' section or make the workflow steps concrete with actual commands instead of abstract descriptions like 'Create a worktree for the parallel task'.
| 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 throughout — from creating worktrees to listing, removing, and pruning them. The quick start section gives concrete commands for both Claude Code and other editors. | 3 / 3 |
Workflow Clarity | The workflow section lists steps but is vague ('Create a worktree for the parallel task' rather than a specific command). The guardrails section includes a verification step (checking git status before removing), but this isn't integrated into the workflow sequence as an explicit checkpoint. For destructive operations like worktree removal, the validation is mentioned but not structured as a feedback loop. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope, 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 the sections serve as natural progressive disclosure within the document. | 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
1de1554
- 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.