cross-repo-upgrade
Generates a plan to coordinate a dependency upgrade across multiple Oxide repos with cyclic dependencies. Triggered when upgrading a shared dependency (like progenitor, reqwest, dropshot) that must be synchronized across omicron, crucible, propolis, dendrite, maghemite, lldp, or other repos. Produces a reviewable plan document rather than executing directly.
94
92%
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 an excellent skill description that clearly defines a specific use case for coordinating dependency upgrades across Oxide's interconnected repositories. It excels in all dimensions by providing concrete actions, natural trigger terms including specific dependency and repo names, explicit 'Triggered when' guidance, and a highly distinctive scope that prevents conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Generates a plan to coordinate a dependency upgrade', 'Produces a reviewable plan document'. Also names specific dependencies (progenitor, reqwest, dropshot) and specific repos (omicron, crucible, propolis, dendrite, maghemite, lldp). | 3 / 3 |
Completeness | Clearly answers both what ('Generates a plan to coordinate a dependency upgrade', 'Produces a reviewable plan document') and when ('Triggered when upgrading a shared dependency... that must be synchronized across' specific repos). The 'Triggered when' clause explicitly defines usage conditions. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'dependency upgrade', 'shared dependency', specific dependency names (progenitor, reqwest, dropshot), specific repo names, and 'cyclic dependencies'. These are terms developers would naturally use when facing this problem. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically targets Oxide repos with cyclic dependencies, names exact repos and common shared dependencies. Very unlikely to conflict with generic dependency or planning skills due to the specific organizational context. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill for a complex coordination task. It excels at workflow clarity with explicit phases, checklists, and validation gates. The progressive disclosure is excellent, keeping the main skill focused while referencing supporting files. Minor verbosity in the principles section and cross-repo boundary explanations could be tightened.
Suggestions
Condense the 'Core principles' section - the Cargo.lock insulation explanation could be reduced to 2-3 sentences since experienced Rust developers understand lockfile semantics.
The 'identify cross-repo type boundaries' section (Step 4) could be more concise - the three bullet patterns (Client injection, Shared types, Re-exported types) could be a simple list without the detailed explanations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some explanatory content that could be tightened. The 'Core principles' section explains concepts like Cargo.lock insulation that experienced Rust developers would know, and some sections are verbose (e.g., the detailed explanation of cross-repo type boundaries). | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific TOML syntax for version aliasing, exact naming conventions (e.g., `reqwest012`), specific cargo commands (`cargo update -p reqwest`), and clear file output format. The checklist and template references make execution straightforward. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit numbered steps, a progress checklist with checkboxes, clear phase separation (isolated commits → landing → cleanup), and explicit validation checkpoint (Step 8: present plan for review before execution). The guardrails section adds explicit safety constraints. | 3 / 3 |
Progressive Disclosure | Well-structured with clear one-level-deep references to REFERENCE.md for VCS commands and search patterns, and EXECUTION-TEMPLATE.md for detailed execution steps. The main skill stays focused on the planning workflow while appropriately delegating mechanical details to supporting files. | 3 / 3 |
Total | 11 / 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
- oxidecomputer/claude-plugins
- Commit
7bd491a
- 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.