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
Install with Tessl CLI
npx tessl i github:projectbluefin/dakota --skill packaging-pre-built-binaries75
Quality
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./.opencode/skills/packaging-pre-built-binaries/SKILL.mdDiscovery
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 is fundamentally incomplete as it only describes when to use the skill without explaining what the skill actually does. While it includes some technical trigger terms, the lack of concrete actions or capabilities makes it nearly impossible for Claude to understand what this skill provides or how to apply it.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Downloads and installs pre-built binaries, verifies checksums, configures PATH')
Restructure to lead with capabilities before the 'Use when...' clause to clearly answer 'what does this do'
Include more natural user-facing trigger terms like 'install binary', 'download release', 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 are no concrete capabilities or actions described. | 1 / 3 |
Trigger Term Quality | Contains some relevant technical terms like 'static binaries', 'bootstrap compiler', and 'building from source' that users might mention, but these are fairly technical and may miss common variations or natural phrasing. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'pre-built static binaries' and 'bootstrap compiler' provides 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 file that demonstrates best practices across all dimensions. It provides concrete, executable templates with real-world examples (Tailscale), includes a comprehensive troubleshooting table, and maintains excellent token efficiency by assuming Claude's competence with the underlying technologies. The multi-arch pattern explanation is particularly well-done, explaining the 'why' (BuildStream limitations) alongside the 'how'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is highly efficient with no unnecessary explanations. It assumes Claude understands YAML, BuildStream concepts, and systemd. Every section provides actionable information without padding or explaining obvious concepts. | 3 / 3 |
Actionability | Provides complete, copy-paste ready YAML templates with real examples (Tailscale). Includes specific commands, exact file paths, and concrete patterns for sed patching, install commands, and preset files. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced (create per-arch elements, then dispatcher). The dependency tracking section explicitly notes manual update workflow with numbered steps. The common mistakes table serves as a validation checklist. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from when-to-use to templates to real examples. References to related skills (packaging-zig-projects, updating-upstream-refs) are one level deep and clearly signaled. Content is appropriately structured without being monolithic. | 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.
- 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.