packaging-gnome-shell-extensions
Use when packaging a GNOME Shell extension for BuildStream, when adding a new extension to the image, or when debugging extension installation paths, UUID discovery, or GSettings schema compilation
88
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
72%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 trigger terms and distinctiveness due to its highly specific technical domain, but it inverts the typical structure by focusing entirely on 'when' without explaining 'what' the skill does. The description would benefit from adding concrete actions like 'Packages GNOME Shell extensions, configures manifest files, validates UUIDs' before the 'Use when' clause.
Suggestions
Add a 'what' clause at the beginning describing concrete actions (e.g., 'Packages GNOME Shell extensions for BuildStream, configures element files, validates extension metadata.')
Restructure to follow the pattern: [What it does]. Use when [triggers] - currently the description only contains the 'Use when' portion
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GNOME Shell extension packaging for BuildStream) and mentions some actions (debugging installation paths, UUID discovery, GSettings schema compilation), but doesn't comprehensively list what concrete actions the skill performs - it focuses more on 'when' than 'what'. | 2 / 3 |
Completeness | The description is essentially all 'when' with no explicit 'what'. It tells Claude when to use the skill but doesn't describe what the skill actually does or what capabilities it provides. The 'what' must be inferred from the trigger conditions. | 2 / 3 |
Trigger Term Quality | Includes highly specific natural keywords users would say: 'GNOME Shell extension', 'BuildStream', 'extension installation paths', 'UUID discovery', 'GSettings schema compilation'. These are precise technical terms that users working in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: GNOME Shell extensions + BuildStream + specific debugging scenarios. The combination of these technical terms makes it extremely unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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 covers a complex topic with 6 distinct build patterns. It provides concrete, executable YAML examples for each pattern, a clear decision flowchart for pattern selection, and a comprehensive troubleshooting table. The structure progresses logically from overview to specific patterns to integration steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is highly efficient with no unnecessary explanations of concepts Claude would know. Every section serves a purpose, and the YAML examples are minimal yet complete. No padding or verbose descriptions of what GNOME Shell extensions are. | 3 / 3 |
Actionability | Provides fully executable YAML configurations for all 6 patterns with copy-paste ready code. Specific commands like `jq -r .uuid metadata.json`, `bsdtar xvf`, and `glib-compile-schemas --strict` are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The decision flowchart clearly guides pattern selection. Each pattern has explicit step sequences, and the 'Common Mistakes' table serves as a validation checklist. The ordering of operations (build → UUID extraction → install → schema compilation) is explicit. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections: Overview → Pattern Selection → Common Elements → Individual Patterns → Integration → Troubleshooting. References to real examples at the end provide navigation without deep nesting. Content is appropriately organized for a single comprehensive skill file. | 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.