setup-build-tools
Install build and extraction tools needed for building Claude Desktop Debian packages
Install with Tessl CLI
npx tessl i github:aaddrick/claude-desktop-debian --skill setup-build-tools71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%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 identifies a clear, narrow niche (Claude Desktop Debian packaging) which makes it distinctive, but lacks explicit trigger guidance and could be more specific about the concrete tools and actions involved. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'building .deb packages', 'Debian packaging', 'dpkg-deb', or 'creating installers for Claude Desktop'
List specific tools that are installed (e.g., 'Installs dpkg-deb, ar, tar, and other extraction utilities')
Include common user phrases like 'package Claude Desktop for Linux' or 'create Debian installer'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Claude Desktop Debian packages) and mentions actions (install, build, extraction), but doesn't list specific concrete actions like which tools are installed or what extraction operations are performed. | 2 / 3 |
Completeness | Describes what it does (install build tools) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Debian packages', 'build', 'install', but missing common variations users might say like '.deb', 'packaging', 'dpkg', or 'apt'. The term 'Claude Desktop' is specific but niche. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Claude Desktop Debian package building - unlikely to conflict with other skills due to the narrow, well-defined scope combining 'Claude Desktop' with 'Debian packages'. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides clear, actionable guidance for installing build dependencies. The main weakness is the lack of validation steps - there's no guidance on verifying successful installation or troubleshooting failures, which is important for dependency installation tasks.
Suggestions
Add a verification step after the install command (e.g., 'Verify installation: `7z --help && wrestool --version`' or check script exit code)
Include brief troubleshooting guidance for common failure scenarios (e.g., permission issues, missing apt sources)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It provides the essential command, a clear table of tools without unnecessary explanation, and concise usage guidance. No padding or concepts Claude already knows. | 3 / 3 |
Actionability | Provides a single, copy-paste ready bash command. The tools table gives specific package names and purposes. Fully executable with no ambiguity. | 3 / 3 |
Workflow Clarity | This is a simple single-step task (run one script), but lacks any validation or feedback guidance. No mention of how to verify tools were installed successfully or what to do if installation fails. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with a single purpose, the content is well-organized with clear sections (task, tools table, when to use). No need for external references given the scope. | 3 / 3 |
Total | 11 / 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.