scenario-image-editing
Scenario Image Editing
Overview
Editing an existing image is a model_run on a tool model: one file in, a few numeric knobs, one or more assets out, nothing to prompt on most of them. Generating a new image, prompt-driven edits and masked inpainting are scenario-image; the same effects on footage are scenario-video-editing; stacking layers is scenario-video-assembly (Image Studio). Connection and the core loop: scenario. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.
Quick reference
Two discovery lanes. A family is browsed with search (target="models", public=true) by tag. A single utility is a capability, so it goes to recommend with capability="img2img" and the need in the user's own words, which names the purpose-built tool and prices it against the general editors; when it answers a utility job with general editors only, find the tool by name with search and filters={"tags": ["tool"]}, as the watermark row does:
| Need | Route |
|---|---|
| The effects family | search, filters={"tags": ["Post Processing"]} (40 hits, image and video) |
| Upscale or enhance | search, filters={"tags": ["image-upscale"]} |
| Cutouts, relight, layers, vector | recommend: at authoring time each lane returned its purpose-built tool ranked by measured cost and latency against the general editors, where search returned the same tools with nothing to rank them by |
| Watermarks, burned-in text | search, query="text remover", a name lookup: at authoring time recommend sent watermark removal to general instruction editors and missed the purpose-built Photoroom Text Remover |
| Tiles, sheets | none: model_scenario-image-slicer, model_scenario-grid-maker (fixed first-party ids, each Scenario's single deterministic tool for its job) |
Reframe ids below are authoring-time hits: re-discover them.