CtrlK
BlogDocsLog inGet started
Tessl Logo

setup-build-tools

Install build and extraction tools needed for building Claude Desktop Debian packages

83

1.34x
Quality

Does it follow best practices?

Impact

86%

1.34x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, fully actionable, and well-organized for a simple single-task skill, with an executable command and a clear tool table and no wasted tokens.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and table-driven, assumes Claude's competence and never pads with explanations of what the tools are, so every token earns its place.

3 / 3

Actionability

It gives a fully executable, copy-paste command (bash "$CLAUDE_PROJECT_DIR/.claude/hooks/install-build-tools.sh") plus a concrete package mapping table, making the guidance immediately runnable.

3 / 3

Workflow Clarity

This is a simple single-action skill whose one action (run the install script) is unambiguous and accompanied by clear "When to Use" guidance, satisfying the simple-skill allowance for a top score.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, the content is well-organized into Task, Tools Installed, and When to Use sections; no bundle files exist to verify, meeting the under-50-line top-score allowance.

3 / 3

Total

12

/

12

Passed

Description

57%

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 is concise and distinct but describes a narrow single action without listing specific tools and lacks an explicit "Use when..." trigger, leaving it solid but not exemplary.

Suggestions

Add an explicit "Use when..." trigger clause, e.g. "Use when preparing to build Claude Desktop .deb packages or when build.sh fails on missing dependencies."

Name the key concrete tools in the description (e.g. 7z, dpkg-deb, Node.js) to raise specificity and trigger-term coverage.

Include natural user phrasings such as "install dependencies" or "build Claude Desktop" alongside the technical terms.

DimensionReasoningScore

Specificity

"Install build and extraction tools needed for building Claude Desktop Debian packages" names the domain and a concrete action (install) but does not enumerate the specific tools, matching the anchor that names domain and some actions without being comprehensive.

2 / 3

Completeness

It states what the skill does (install tools for building Debian packages) but lacks any explicit "Use when..." trigger clause, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like "build and extraction tools" and "Debian packages" are relevant but lean technical; common user phrasings such as "install dependencies" or "build Claude Desktop" are absent, fitting the anchor for some relevant keywords with missing variations.

2 / 3

Distinctiveness Conflict Risk

The niche of installing build/extraction tooling for Claude Desktop Debian packaging is clearly scoped and unlikely to trigger for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

9

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
aaddrick/claude-desktop-debian
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.