agentleFS
AlpacaLabsLLCAlpacaLabsLLC/skills-for-architects/skills/resize-images/SKILL.md

resize-images

Skill390 starsChanged 55 days agoMITView on GitHub

Batch-resize or convert a folder of images for web, social media, slides, or ARCH-size print output while preserving originals. Use for image resizing, format presets, or photo batches; not for product-image background removal.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before acting, read the host contract and this component's declaration (skill:resize-images).

    line 13

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/as:resize-images — Image Resizer for Web, Social, and Print

Before acting, read the host contract and this component's declaration (skill:resize-images). Compose only applicable modes from the shared catalog; declarations do not prove access or permission. Use the actual host’s delivery route.

Select the requested batch

Resize photos and renders into requested copies while preserving originals. Reuse the supplied source folder and selected web, social, slides or print modes. Ask only for materially missing inputs, not information or authorization already supplied. This one-off operation requires no studio/project setup.

Read the complete native resize owner for resize_images.resize: exact input and output membership, all twelve preset labels/dimensions/encoding settings, width-only web behavior, center crop, print rounding/DPI, first-frame/color scope, literal collision checks, failure and retry semantics. Use the actual host's available tools; no installed Arch Studio runner, executable handoff or universal dependency installation is required. The presets are Arch Studio-authored sizes, not current external platform requirements. A different requested dimension/crop needs an actually supported separately selected route.

Inspect, prepare and publish

Scan the authorized folder non-recursively for supported .jpg, .jpeg, .png, .tif, .tiff and .webp files; report the count and stop explicitly on no supported inputs. Inspect actual access, source membership and collision boundaries before processing. Preserve originals, names, unrelated files and source access metadata. Duplicate stems or existing reserved outputs block except a proven exact retry.

Follow the owner's complete-batch preparation and the native mutation sequence. Prepare every successful source's whole derivative group and any requested public report before the first publisher; failed sources contribute no partial derivative group and do not prevent preparing other sources. Durably finish, separately reopen and verify the entire retained original/prepared byte and access set. Publish complete files with no clobber; a direct public file creation followed by writing is insufficient. Reopen and inspect every actual image/report destination and access metadata, then the full protected/source set before completion. Reconcile interrupted or exact repeated work before making new copies.

Inspect and report results

Verify decoded dimensions, format, print 300×300 DPI and actual crop/orientation/color behavior. Inspect the images for material subject clipping; center crop has no subject detection. Web limits width, print fits an unrotated box, and both avoid enlargement. Small inputs still receive every selected labelled output; social/slides enlarge to fill. Non-RGB/L sources convert to RGB with alpha discarded, and animated/multipage sources contribute only their initial frame. Do not promise ICC/EXIF preservation, metadata stripping or automatic orientation correction.

List actual output directories, filenames, dimensions and integer KiB, successful/failed source counts and concrete errors/omissions. Keep the compatible mechanical summary separate from actual completion evidence; partial batch success is not full completion. No record adoption, registration, upload or external delivery is implicit.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.