Use when working in a manyrepo workspace managed by Branchout (~/projects/*/), finding repos the user mentions by name (even if not exactly) within the naming-convention-based folder structure, cloning updating or adding repos, running isolated builds via wrappers like branchout mvn or branchout yarn, or when someone mentions Branchout or asks what Branchout is. Detect by Branchoutfile or .branchout in current or parent directories.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 well-crafted skill description that clearly identifies the Branchout tool ecosystem with specific actions, detection methods, and trigger scenarios. It uses third person voice appropriately and provides enough distinctive markers (tool name, file patterns, wrapper commands) to avoid conflicts with other repository or build-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: finding repos by name, cloning/updating/adding repos, running isolated builds via wrappers (branchout mvn, branchout yarn), and detecting by Branchoutfile/.branchout files. | 3 / 3 |
Completeness | Opens with explicit 'Use when...' clause covering multiple trigger scenarios (working in manyrepo workspace, finding repos, running builds, mentioning Branchout) and clearly describes what it does throughout. | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: 'Branchout', 'manyrepo', 'repos', 'cloning', 'builds', 'branchout mvn', 'branchout yarn', plus file markers like 'Branchoutfile' and '.branchout'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific tool name 'Branchout', unique path pattern (~/projects/*/), specific wrapper commands, and detection files (.branchout, Branchoutfile) that clearly differentiate from generic repo or build skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that efficiently teaches Branchout usage with concrete commands, clear directory layouts, and well-sequenced workflows. It respects Claude's intelligence by avoiding unnecessary explanations while providing all the actionable details needed. The safety considerations (trusting repos, stashing work) and gotchas section demonstrate thoughtful coverage of edge cases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section provides actionable information without padding or unnecessary context about what git repos are or how version control works. | 3 / 3 |
Actionability | Provides concrete, executable commands throughout with copy-paste ready examples. The quick start table, installation commands, and workflow examples are all immediately usable without modification. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit steps. The 'Switch branches safely' workflow includes validation (stashing with timestamps), and the 'Start using a new workspace' flow has clear sequential steps with appropriate safety warnings about trusting repos. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from quick start to detailed workflows. References REFERENCE.md for full CLI details, keeping the main skill focused. Content is appropriately split between overview and detailed guidance. | 3 / 3 |
Total | 12 / 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.
99249ec
Table of Contents
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.