From image-production
Use when the user wants to generate thumbnails at scale — index views, contact sheets, web previews, or just shrinking a library to manageable sizes. Wraps `vipsthumbnail` for sub-second-per-image generation, much faster than ImageMagick on large batches.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin image-productionThis skill uses the workspace's default tool permissions.
Generate thumbnails at high throughput using `vipsthumbnail`. Distinct from `fast-resize`: this is purpose-built for "make small previews of every image in this folder" workflows where output is always a downscale and quality is "good enough for a thumbnail".
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Generate thumbnails at high throughput using vipsthumbnail. Distinct from fast-resize: this is purpose-built for "make small previews of every image in this folder" workflows where output is always a downscale and quality is "good enough for a thumbnail".
Do not use this skill when:
fast-resize (or upscale-image for AI upscale).NxN (fit within square). Default: 512.<input>/thumbnails/. The skill never overwrites originals.jpg (best size/quality balance for thumbs). Options: jpg, png, webp, avif.80.--recursive to descend. Mirrors subdirectory structure under the output dir.--prefix <s> or --suffix <s> if collision is a risk.Verify vipsthumbnail is on PATH. If missing, point at install-deps. No graceful fallback — if vips isn't installed, the skill's whole reason to exist is gone; tell the user to install or use batch-resize.
Enumerate input files (image extensions only).
For each file:
vipsthumbnail "<input>" \
--size "<size>" \
--output "<output-dir>/<basename>.<ext>[Q=<quality>]"
For non-JPEG outputs, the [Q=N] syntax still works for WebP/AVIF.
For very large batches, parallelise with find ... | xargs -P <ncpu> -I{} vipsthumbnail .... vips is internally threaded but per-image work is small enough that process-level parallelism wins on >5k batches.
Track progress and skipped files (corrupt, wrong format).
<output-dir>/.<n> thumbnails, <total-output-MB>MB, <elapsed-s>s, avg <ms>ms/image.vipsthumbnail shrink-on-load: for JPEG sources, it decodes at the smallest DCT scale ≥ target — so generating a 256-px thumbnail from a 4000-px JPEG is much faster than full decode + resize. This is the headline reason to use it.--no-rotate and explicit --linear flags only if Daniel asks; the defaults are sensible for thumbnails.montage separately.--export-profile <path-to-srgb.icc>.