managing-bst-overrides

Use when creating, evaluating, or removing BuildStream junction element overrides - ensures agents follow GNOME OS upstream-first principle and maintain recognizable patterns

Quality

76%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.opencode/skills/managing-bst-overrides/SKILL.md

Quality

Discovery

75%

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 has a clear 'Use when...' clause and targets a very specific technical niche, making it complete and distinctive. However, it could benefit from more concrete action descriptions and additional trigger terms that users might naturally use when needing this functionality.

Suggestions

Expand the specific actions beyond 'creating, evaluating, removing' to describe concrete outcomes (e.g., 'configure upstream dependencies', 'validate override configurations')

Add alternative trigger terms users might say, such as 'BST junctions', 'element dependencies', or 'upstream tracking'

Dimension	Reasoning	Score
Specificity	Names the domain (BuildStream junction element overrides) and lists three actions (creating, evaluating, removing), but lacks detail on what these actions specifically entail or what concrete outcomes they produce.	2 / 3
Completeness	Explicitly answers both 'what' (creating, evaluating, removing BuildStream junction element overrides) and 'when' (starts with 'Use when...'), providing clear trigger guidance for Claude to select this skill.	3 / 3
Trigger Term Quality	Includes technical terms like 'BuildStream', 'junction element', 'overrides', and 'GNOME OS' which are relevant but highly specialized. Missing common variations or simpler terms users might naturally say.	2 / 3
Distinctiveness Conflict Risk	Highly specific niche targeting BuildStream junction element overrides with GNOME OS context. Very unlikely to conflict with other skills due to the specialized terminology and narrow scope.	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 high-quality, actionable skill with excellent workflow clarity and concrete examples. The decision matrix and red flags sections provide clear guidance on when to use overrides. The main weakness is length - at ~350 lines, some content (detailed examples, troubleshooting) could be split into referenced files to improve token efficiency.

Suggestions

Move the detailed 'Example: Removing an Identical Override (bootc)' section to a separate EXAMPLES.md file and reference it

Consolidate the decision matrix, 'When to Create an Override', and 'Red Flags' sections to reduce redundancy in explaining override vs patch decisions

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some redundancy - the decision matrix, examples, and red flags sections overlap in explaining when to use overrides vs patches. The 'Current Overrides' table with dates and the extensive examples add value but could be tightened.	2 / 3
Actionability	Excellent executable guidance throughout - specific bash commands, YAML snippets, exact file paths, and copy-paste ready verification commands. The step-by-step processes for creating and removing overrides are fully actionable.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with explicit validation checkpoints. The 'Removing an Override' section has a mandatory checklist with verification steps, and the examples show the exact verification commands to confirm success.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but this is a monolithic document that could benefit from splitting. The 'Integration with Other Skills' section properly references related skills, but the detailed examples and troubleshooting could be separate files.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: 11 days ago

Table of Contents

Discovery Implementation Validation

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.