Bare-bones GIMP CLI wrapper for Claude Code on Linux. Detects install (native/Flatpak/Snap/AppImage), persists a per-user profile, exposes Script-Fu batch ops, image export, and GIMP-side plugin install/list.
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Plugin gimp in danielrosehill/Claude-GIMP-Plugin. Commands read from the repo's manifest — 1 month ago.
batch-processApply one operation across a folder of images using GIMP's headless console — resize, crop, format-convert, flatten, watermark, etc. Use when the user wants to bulk-process images and ImageMagick alone isn't enough (e.g. needs a GIMP-only filter or PSD/XCF support).
export-imageConvert a single image (XCF, PSD, PNG, JPG, TIFF, WebP, etc.) to another format via GIMP headless. Use when the user wants to export a GIMP-native file to a web format, or when format support outside GIMP is missing.
gimp-cli-referenceReference for the GIMP command-line interface — non-interactive batch mode, Script-Fu invocation, console binary, and the differences between GIMP 2.10 and GIMP 3.0. Read this before authoring batch ops or Script-Fu calls.
install-gimp-pluginInstall a GIMP-side plugin (Script-Fu .scm, Python-Fu .py, or compiled binary) into the user's GIMP config directory so it appears in the GIMP menu next launch. Use when the user wants to add a third-party GIMP filter or extension.
list-gimp-pluginsList every Script-Fu, Python-Fu, and binary plugin currently installed in the user's GIMP config directory, including version (where derivable) and whether it lives in the user dir or system dir. Use when the user asks "what plugins do I have", or before installing one to check for duplicates.
onboardFirst-run setup for the GIMP plugin. Detects how GIMP is installed on the user's Linux machine (native package, Flatpak, Snap, AppImage), captures version and CLI binary path, and persists a profile to $CLAUDE_USER_DATA so the other skills can shell out without re-detecting. Use the first time the p
run-script-fuExecute an arbitrary Script-Fu expression (or a .scm file) against the user's GIMP install in headless mode, using the binary path stored by onboard. Use when the user asks to run a Script-Fu snippet, debug a script, or test PDB calls.
upgrade-detectRe-probe the local GIMP install and update the saved profile if version, binary path, or install type has changed. Use after `apt upgrade`, `flatpak update`, `snap refresh`, replacing an AppImage, or when another skill reports a stale binary.
Harness Adobe's creative AI-powered tools to edit images, automate design workflows, and bring creative visions to life — from background removal to vectorization and professional retouching.
26 skills · 1 MCP server
Brings together Adobe Creative Cloud tools for images, vectors, design, and video. Edit multiple assets at once, adapt for different platforms, and complete multi-step creative workflows for polished results.
26 skills · 1 MCP server
Comprehensive C/C++ security code review, with coverage verified against a parse of the source
1 skill · 1 agent
Hooks that send each Claude Code tool call to a local Tracekit signer before it runs: allowed, denied with the rule that matched, or held until you approve it from another terminal. The signer signs every call, decision and result into a hash-chained record that `tracekit verify` checks offline. Needs the tracekit-ai Python package (`pip install tracekit-ai==1.6.0 && tracekit init --dev --v2 --no-hooks`). In that dev mode the signer runs as your own user; on Linux, system mode runs it as a separate user.
3 skills · 3 commands · hooks
Brief-led image generation, editing, review, and bounded multi-model orchestration with current Gemini image models. Requires Claude Code 2.1.199+, Python 3.11+ with python3 on PATH, and Linux, macOS, or WSL for generation.
1 skill · 2 agents · 1 MCP server
Per-session screenshot cleanup: tracks screenshots created during each Claude Code session and asks before moving them to the Trash (recoverable). macOS + Linux, zero dependencies.
1 skill · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.