Image editing
Skill event4u-app/agent-config/dist/agent-src/skills/image-editing
Universal AI Agent OS — audited skills, governance rules, replayable state. One contract, every host agent.
npx -y skills add event4u-app/agent-config --skill image-editingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Edit an existing image — inpaint, background swap, variation — via providers that support it. Use when editing/modifying/inpainting an image or making variations.
SKILL.md
5.5 KB, as published. Nobody here has run it
image-editing
Edit or vary an existing image: inpaint masked regions, swap backgrounds, produce
variations from a seed, or upscale — routed to providers that support the edit API,
with governance applied before delivery. All adapters are scaffold-tier (dry-run) until promoted to stable.
When to use
- User asks to edit, modify, inpaint, or make a variation of an existing image.
- Background removal or swap on a provided asset.
- Upscaling or restyling an existing render from a prior generation run.
- Any task that starts from an image rather than a blank brief.
Procedure
- Identify the edit type — classify the request:
inpaint(replace a masked region),background(remove or swap),variation(alternate version of the same subject), orupscale(resolution increase). - Confirm provider support — not all providers support image editing. GPT Image 2
and
gemini-imageboth expose an edit/inpaint endpoint. Flux and Recraft support variation via seed/ref-image only; Ideogram is largely generate-only. Check the provider's capability before proceeding. - Route the provider via
image-provider-routing— route to a provider whose adapter exposes an edit endpoint for the required edit type. Selecting a generate-only provider for an inpaint task will fail silently. - Author the edit instruction via
prompt-engineering-image— write the edit prompt in the target provider's grammar. For inpaint, describe what fills the masked region. For variation, carry the original seed/ref-image path forward. - Invoke the adapter (dry-run today) — run
src/scripts/ai-image/adapters/<provider>.shwith the assembled params including the source image path and, for inpaint, the mask path. Validate the returned artifact path or dry-run confirmation. All adapters areexperimental(scaffold-tier); no live editing occurs until a maintainer promotes the adapter viaprovider-lifecycle-discipline. - Apply rights and disclosure governance — run the rights check
(
image-likeness-and-rights) when the source image or edit instruction involves a real person's likeness, a brand mark, or a named living artist's style. Attach the AI-disclosure footer permedia-governance-routingbefore delivering output.
Output format
- Edit plan — edit type, chosen provider, routing rationale, and prompt string ready to copy.
- Provider + params — adapter file reference, source image path, mask path (if inpaint), key params (aspect ratio, strength, seed/ref-image for variation).
- Artifact path / dry-run note — the path returned by the adapter, or an
explicit note: "adapter is experimental (scaffold-tier) — dry-run plan only; no
edited asset until promotion per
provider-lifecycle-discipline."
Gotcha
- Scaffold-tier adapters produce plans, not pixels — adapters for GPT Image 2,
gemini-image, Flux, and Recraft are scaffold-tier (dry-run only). This skill produces the edit blueprint + dry-run confirmation; actual edits require a maintainer to capture a smoke trace and promote the adapter tostable. Claiming an edited asset exists when no adapter is stable misleads the caller. - Not all providers support editing — Ideogram and Recraft are primarily generate-only; they do not expose a mask-based inpaint endpoint. Routing an inpaint task to them silently falls back to generation from scratch, discarding the source image entirely.
- Variation needs the original seed or ref-image — requesting a variation without carrying the seed value or ref-image path from the original generation will produce a stylistically unrelated result. The seed/ref-image is the only reliable continuity lever for variation workflows.
Do NOT
- Do NOT assume every provider supports image editing — check provider capability before routing; a generate-only provider will discard the source image.
- Do NOT skip
image-likeness-and-rightswhen the source image or edit prompt involves a real person's face, a brand mark, or a named living artist's style. - Do NOT claim a live edit is produced while adapters are scaffold-tier — surface the dry-run caveat explicitly every time.
- Do NOT use this skill for generating a new image from scratch — route that to
image-generationinstead.
See also
image-generation— generate a new image from a brief (not editing an existing one).image-provider-routing— select the right provider before writing the prompt.prompt-engineering-image— translate the edit brief into provider-specific prompt grammar.image-likeness-and-rights— rights check before editing real-person likenesses or brand marks.screenshot-hygiene— for redacting a documentation screenshot, use a deterministic opaque box/blur (never the lossy inpaint here).