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 English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
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.
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.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.
The English summary is being prepared. Showing the original description.
Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Use for questions such as “what is a CD set?” or “what does 50% CDs mean?”; do not use for code/jurisdiction, outline-spec, agreement-scope, or work-plan work.
The English summary is being prepared. Showing the original description.
Create an HTML color palette from a mood, description, or image, with swatches, color codes, pairings, and contrast checks. Use for color schemes or brand colors.
The English summary is being prepared. Showing the original description.
Export a project's FF&E product-library CSV as dealer-system SIF. Use to produce a .sif schedule; use sif-to-csv for the reverse direction.
The English summary is being prepared. Showing the original description.
Research population, income, age, housing, and employment around a site. Use for census, demographic, or local-market questions tied to a location.
The English summary is being prepared. Showing the original description.
Extract countable FF&E or luminaire instances from supplied drawings with position-level evidence. Use for plan quantities or symbol counts; not area takeoffs, product specs or cross-source reconciliation.
The English summary is being prepared. Showing the original description.