updating-upstream-refs
Use when updating a package version, bumping upstream refs, wondering how dependency tracking works, or asking how to update Tailscale/Zig/junction refs in the Bluefin image
82
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.opencode/skills/updating-upstream-refs/SKILL.mdQuality
Discovery
54%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger terms and distinctiveness by naming specific technologies and use cases, but critically fails at completeness by only describing when to use the skill without explaining what it actually does. This is essentially a 'Use when...' clause without the preceding capability description.
Suggestions
Add a capability statement before the 'Use when...' clause describing what the skill does, e.g., 'Manages package versions and dependency updates in Bluefin container images. Handles version bumping, upstream reference tracking, and configuration updates.'
Include specific actions the skill performs, such as 'edits version files', 'updates refs in configuration', or 'tracks dependency changes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (package version updates, dependency tracking) and mentions specific technologies (Tailscale/Zig/junction refs, Bluefin image), but doesn't list concrete actions like 'edit version files', 'run update commands', or 'modify configuration'. | 2 / 3 |
Completeness | Only answers 'when' (Use when...) but completely lacks the 'what does this do' component. There's no description of what actions or capabilities the skill provides, only trigger conditions. | 1 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'updating a package version', 'bumping upstream refs', 'dependency tracking', 'update Tailscale/Zig/junction refs', and the specific 'Bluefin image' context. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche with distinct triggers like 'Bluefin image', 'Tailscale/Zig/junction refs', and 'upstream refs'. Unlikely to conflict with generic package management skills due to the specific technology references. | 3 / 3 |
Total | 9 / 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 document that efficiently conveys complex, project-specific dependency tracking information. It excels at providing concrete, actionable guidance with clear decision trees, executable commands, and well-organized reference tables. The content respects Claude's intelligence while providing all the domain-specific details needed to perform version updates correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is dense with project-specific information Claude wouldn't know. No unnecessary explanations of basic concepts; every section provides actionable, domain-specific details about this particular build system's dependency tracking mechanisms. | 3 / 3 |
Actionability | Provides fully executable commands (curl, just bst, sha256sum), concrete YAML examples, specific file paths, and copy-paste ready patterns. The manual version bump workflow has numbered steps with exact commands. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation (step 5: build element, step 6: full image build to verify). The decision tree provides clear routing logic, and the 'Common Mistakes' section addresses error recovery scenarios. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from overview to decision tree to detailed mechanisms. Cross-references at the end point to related skills without deep nesting. Tables organize information efficiently for scanning. | 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.
- Repository
- projectbluefin/dakota
- Commit
f062bf8
- 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.