packaging-pre-built-binaries
Use when packaging a project that provides official pre-built static binaries, when building from source is impractical, or when you need a bootstrap compiler
69
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.opencode/skills/packaging-pre-built-binaries/SKILL.mdQuality
Discovery
22%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 fails to explain what the skill actually does, focusing entirely on usage conditions without describing capabilities. The 'when' guidance is present but the complete absence of 'what' makes it impossible for Claude to understand the skill's purpose. The technical terms provide some distinctiveness but are insufficient without concrete action descriptions.
Suggestions
Add a clear statement of what the skill does at the beginning (e.g., 'Downloads and installs pre-built binaries from official release pages' or 'Configures bootstrap compilers for language toolchains').
Include specific concrete actions the skill performs (e.g., 'fetches releases, verifies checksums, extracts archives, configures PATH').
Add natural trigger terms users might say, such as 'install binary', 'download release', 'precompiled', or specific tool names this skill handles.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'packaging a project' without specifying concrete actions. It doesn't describe what the skill actually does - only when to use it. | 1 / 3 |
Completeness | The description only addresses 'when' to use the skill but completely omits 'what' the skill does. There's no explanation of the actual capabilities or actions performed. | 1 / 3 |
Trigger Term Quality | Contains some relevant technical terms like 'static binaries', 'bootstrap compiler', and 'building from source' that users might mention, but lacks common variations and natural phrasing users would typically use. | 2 / 3 |
Distinctiveness Conflict Risk | Terms like 'bootstrap compiler' and 'pre-built static binaries' provide some specificity, but 'packaging a project' is generic and could overlap with other build/deployment skills. | 2 / 3 |
Total | 6 / 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 provides highly specific, actionable guidance for a complex BuildStream packaging scenario. It efficiently covers required settings, templates, multi-arch patterns, and common pitfalls without any unnecessary explanation. The real Tailscale example and comprehensive mistakes table make this immediately usable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place with specific, non-obvious information. No explanation of basic concepts—jumps straight to BuildStream-specific requirements, patterns, and gotchas that Claude wouldn't know. | 3 / 3 |
Actionability | Provides complete, copy-paste ready YAML templates with real examples (Tailscale). Includes specific commands, exact file paths, and concrete sed patterns. The templates are executable, not pseudocode. | 3 / 3 |
Workflow Clarity | Multi-arch pattern clearly sequences the file creation process. The 'Common Mistakes' table serves as a validation checklist. Dependency tracking section explicitly calls out the manual update workflow with numbered steps. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from 'When to Use' through templates to real examples. References to related skills ('packaging-zig-projects', 'updating-upstream-refs') are one level deep and clearly signaled. | 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.