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
Hook script usage and package identification
Hook script referenced
0%
0%
Correct script path
0%
0%
p7zip-full package
100%
100%
icoutils package
0%
100%
dpkg-dev package
100%
100%
libfuse2 package
100%
100%
Node.js v20+
0%
100%
wget package
0%
100%
imagemagick package
100%
100%
Setup timing guidance
90%
100%
Without context: $0.2376 · 1m 16s · 15 turns · 304 in / 4,101 out tokens
With context: $0.3621 · 1m 24s · 24 turns · 61 in / 3,948 out tokens
Build tool identification and version checking
7z tool check
100%
100%
wrestool tool check
100%
100%
convert tool check
100%
100%
dpkg-deb tool check
100%
100%
libfuse2 check
0%
100%
Node.js presence check
100%
100%
Node.js version check
0%
100%
wget tool check
100%
100%
Package names on failure
100%
100%
Non-zero exit on failure
100%
100%
Without context: $0.2577 · 1m 21s · 14 turns · 21 in / 4,856 out tokens
With context: $0.2733 · 1m 3s · 18 turns · 23 in / 3,689 out tokens
Package-to-tool mapping and Node.js version requirement
p7zip-full mapping
100%
100%
icoutils mapping
100%
100%
imagemagick mapping
100%
100%
dpkg-dev mapping
0%
100%
libfuse2 entry
0%
0%
Node.js version constraint
100%
100%
nodejs package name
100%
100%
wget entry
0%
100%
Tool purposes included
100%
100%
Binary-to-package format
100%
100%
Without context: $0.2400 · 1m 35s · 12 turns · 16 in / 5,246 out tokens
With context: $0.2178 · 1m 2s · 12 turns · 530 in / 2,843 out tokens
Table of Contents
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.