install-deps
Skill21 starsChanged 7 days agoMITView on GitHub
Provision the plugin's tools — system binaries via the host package manager, Python tools into a plugin-owned uv venv at <data-dir>/venv/. Idempotent doctor — run before any command reports a missing dep. Never touches system Python or fights PEP 668.
- Pipes a download into a shell
- Installs packages
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- danielrosehill/Claude-Audio-Production-Pluginedited, first seen Apr 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
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 repository28 other files it gives its agents.
- ai-graphicsSkill
- auto-deskewSkill
- auto-toneSkill
- auto-white-balanceSkill
- batch-set-copyrightSkill
- check-model-pricingSkill
- convert-to-avifSkill
- fast-resizeSkill
- fast-thumbnailSkill
- from-jxlSkill
- images-to-pdfSkill
- new-projectSkill
- new-workflowSkill
- open-workspaceSkill
- optimize-jpegSkill
- optimize-pngSkill
- pdf-extract-embedded-imagesSkill
- pdf-to-imagesSkill
- read-metadataSkill
- scrub-metadataSkill
- set-metadataSkill
- svg-to-rasterSkill
- to-jxlSkill
- transcode-jpeg-to-jxl-losslessSkill
- upscale-imageSkill
- vectorizeSkill
- web-readySkill
- workspace-setupSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
Ask before running. Fall back to system pip with --break-system-packages only if the user declines — prefer uv.
- Very specific: line 72
If <VENV_DIR> doesn't exist:
- Distinctive: line 78
If it exists, leave it.
- Very specific: line 99
If cairosvg import fails at runtime with a libcairo error, prompt the user to install the system lib: sudo apt install libcairo2 (Linux) / …
- Distinctive: line 103
After installs, re-run the detect commands and report a green/red status table per tool.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Dependencies
Two surfaces:
- System binaries — required:
ImageMagick,exiftool. Optional:libvips-tools,libheif-examples,oxipng,pngquant,jpegoptim,mozjpeg,libavif-bin,libjxl-tools,realesrgan-ncnn-vulkan,darktable-cli. - Python tools —
imagehash,Pillow(perceptual dedupe). Installed into a plugin-owned uv venv at<data-dir>/venv/.
The plugin invokes Python via <data-dir>/venv/bin/python, so the user's system Python stays untouched and PEP 668 / externally-managed-environment errors never occur.
Resolve paths
PLUGIN_DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/image-production"
VENV_DIR="$PLUGIN_DATA_DIR/venv"Procedure
1. Detect host
uname -s
which apt-get apt brew dnf pacman 2>/dev/null
which uv 2>/dev/nullRecord what's available; this drives which install commands you propose.
2. Ensure uv is available
uv is the only hard prerequisite for the Python side. If missing, propose:
curl -LsSf https://astral.sh/uv/install.sh | shAsk before running. Fall back to system pip with --break-system-packages only if the user declines — prefer uv.
3. Walk the system-binary matrix
| Tool | Detect | Required? | Install (apt) | Install (brew) |
magick / convert / identify | which magick || which convert | required | sudo apt install imagemagick | brew install imagemagick |
exiftool | which exiftool | required | sudo apt install libimage-exiftool-perl | brew install exiftool |
fdupes | which fdupes | optional | sudo apt install fdupes | brew install fdupes |
vips / vipsthumbnail | which vips | optional (recommended >500 images) | sudo apt install libvips-tools | brew install vips |
heif-convert | which heif-convert | optional | sudo apt install libheif-examples | brew install libheif |
oxipng | which oxipng | optional | sudo apt install oxipng | brew install oxipng |
pngquant | which pngquant | optional | sudo apt install pngquant | brew install pngquant |
jpegoptim | which jpegoptim | optional | sudo apt install jpegoptim | brew install jpegoptim |
mozjpeg (cjpeg-mozjpeg) | which cjpeg-mozjpeg | optional | cargo install mozjpeg-cli (or binary) | brew install mozjpeg |
avifenc | which avifenc | optional | sudo apt install libavif-bin | brew install libavif |
cjxl / djxl | which cjxl | optional | sudo apt install libjxl-tools | brew install jpeg-xl |
upscayl-bin | which upscayl-bin || ls /opt/Upscayl/resources/bin/upscayl-bin 2>/dev/null | optional | install Upscayl from https://upscayl.org (deb / flatpak / appimage) | install Upscayl from https://upscayl.org |
realesrgan-ncnn-vulkan (fallback) | which realesrgan-ncnn-vulkan | optional | binary release from upstream | binary release from upstream |
darktable-cli | which darktable-cli | optional | sudo apt install darktable (GUI + CLI) | brew install darktable |
img2pdf | which img2pdf | optional | uv tool install img2pdf (or sudo apt install python3-img2pdf) | pipx install img2pdf |
For each: if missing, stage the install command tagged required/optional. Required tools that are missing block the install — surface that clearly.
realesrgan-ncnn-vulkan and mozjpeg are not in apt — for those, point the user at the upstream releases page rather than auto-downloading. Ask before placing binaries under ~/bin/.
4. Provision the venv
If <VENV_DIR> doesn't exist:
uv venv "$VENV_DIR" --python 3.11If it exists, leave it.
5. Install Python packages into the venv
| Package | Required? | Used by |
Pillow | required | dedupe (perceptual), inspection |
imagehash | required | dedupe (perceptual) |
numpy | required (Pillow/imagehash dep) | dedupe |
cairosvg | optional | svg-to-raster (SVG → PNG/PDF). Needs system libcairo2 (preinstalled on most Linux/macOS). |
vtracer | optional | vectorize (raster → SVG). Self-contained wheel (bundled Rust binary). |
Stage:
source "$VENV_DIR/bin/activate"
uv pip install Pillow imagehash numpy
# Optional — only if user wants SVG conversion / vectorization:
uv pip install cairosvg vtracerIf cairosvg import fails at runtime with a libcairo error, prompt the user to install the system lib: sudo apt install libcairo2 (Linux) / brew install cairo (macOS).
6. Verify
After installs, re-run the detect commands and report a green/red status table per tool. Surface install commands the user still needs to run themselves (sudo, cargo).
Output
Single status report:
- Required system bins: present / missing.
- Optional system bins: present / missing (with one-line reason to install each).
- Venv: provisioned at
<VENV_DIR>, Python<version>. - Python packages: installed.
Refuse to mark "OK" if any required tool is missing.
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.