setup-build-tools
Skill1 starsChanged 6 months agoApache-2.0View on GitHub
Install build and extraction tools needed for building Claude Desktop Debian packages
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- aaddrick/claude-desktop-debianedited, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- aaddrick/claude-desktop-debian★ 5.5k90% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- implement-issueSkill
- improvement-loopSkill
- lintSkill
- simplifySkill
- triageSkill
- writing-agentsSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Run the build tools installation script to ensure all required tools are available:
- Very specific: line 32
Before running ./build.sh for the first time
- Distinctive: line 33
After setting up a new development environment
- Very specific: line 34
When build.sh fails due to missing dependencies
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Install the build dependencies required to run build.sh and create .deb/.AppImage packages.
Your Task
Run the build tools installation script to ensure all required tools are available:
bash "$CLAUDE_PROJECT_DIR/.claude/hooks/install-build-tools.sh"Tools Installed
This script installs:
| Tool | Package | Purpose |
7z | p7zip-full | Extract Windows installers and nupkg archives |
wget | wget | Download Claude Desktop installers |
wrestool | icoutils | Extract icons from Windows executables |
convert | imagemagick | Process tray icons for Linux |
dpkg-deb | dpkg-dev | Build .deb packages |
libfuse2 | libfuse2 | Run AppImages |
node | nodejs | Node.js v20+ for npm/asar operations |
When to Use
- Before running
./build.shfor the first time - After setting up a new development environment
- When build.sh fails due to missing dependencies
Optional Guidance
$ARGUMENTS
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

