multiverse/stardust-consumer-upgrade
Upgrade "@multiverse-io/stardust-react" and/or "@multiverse-io/stardust" in any consumer repo — auto-detects repo structure, runs safe upgrade workflow with visual validation and regression handling. Supports single-repo and fleet (multi-repo wave) modes.
78
Does it follow best practices?
Validation for skill structure
Discovery
67%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 description excels at specificity and distinctiveness by naming exact packages and concrete workflow steps. However, it lacks an explicit 'Use when...' clause and could benefit from additional trigger term variations like 'update dependencies' or 'bump stardust version' to improve discoverability.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when upgrading stardust packages, updating design system dependencies, or bumping @multiverse-io library versions.'
Include common trigger term variations such as 'update', 'bump version', 'dependency upgrade', 'design system update' to improve matching with natural user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Upgrade', 'auto-detects repo structure', 'runs safe upgrade workflow', 'visual validation', 'regression handling'. Also specifies two distinct modes (single-repo and fleet/multi-repo wave). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with detailed capabilities, but lacks an explicit 'Use when...' clause. The when is only implied through the action verb 'Upgrade' at the start. | 2 / 3 |
Trigger Term Quality | Includes specific package names '@multiverse-io/stardust-react' and '@multiverse-io/stardust' which are good triggers, plus 'upgrade' and 'consumer repo'. However, missing common variations like 'update', 'bump version', 'dependency update', or 'package upgrade'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to specific package names '@multiverse-io/stardust-react' and '@multiverse-io/stardust'. Very unlikely to conflict with other skills as it targets a specific library ecosystem. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill for a complex multi-repo upgrade workflow. Its strengths are the concrete commands, explicit validation gates, and clear wave-based fleet execution. The main weakness is length—some reference tables could be externalized to improve token efficiency while maintaining the excellent workflow clarity.
Suggestions
Consider moving the Consumer Registry table to a separate CONSUMER_REGISTRY.md file and referencing it, reducing the main skill's token footprint
The validation commands table (Step 5) could be condensed by grouping repos with identical patterns rather than listing each individually
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., the consumer registry table duplicates information that could be discovered at runtime, and the validation commands table repeats patterns). The changelog boundaries section is valuable but could be more compact. | 2 / 3 |
Actionability | Excellent actionability with concrete bash commands, specific package manager syntax, exact file paths, and copy-paste ready code blocks. The workflow steps are executable with clear commands for each repo type and scenario. | 3 / 3 |
Workflow Clarity | Outstanding workflow structure with numbered steps, explicit validation checkpoints (Steps 4-5), gate checks between fleet waves, and clear rollback procedures. The risk check step explicitly requires stopping for HIGH severity boundaries, demonstrating proper feedback loops. | 3 / 3 |
Progressive Disclosure | References external documentation appropriately (Stardust Consumer Upgrade Investigation.md) but the skill itself is quite long (~300 lines). The consumer registry and validation tables could potentially be split into separate reference files, though the inline approach does provide immediate access. | 2 / 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.
Install with Tessl CLI
npx tessl i multiverse/stardust-consumer-upgradeReviewed
Table of Contents