Venice Image Edit
Wire Venice.ai image edit, upscale, and background-removal into agent workflows without hunting the upstream skills repo during planning.
Overview
Venice-image-edit is an agent skill for the Build phase that routes image edits, upscaling, and background removal through the Venice.ai API after you install the upstream bundle.
Install
npx skills add https://github.com/nexu-io/open-design --skill venice-image-editWhat is this skill?
- Covers image edits, upscaling, and background removal via the Venice.ai API
- Open Design catalogue entry with triggers: venice image edit, venice upscale, venice background removal
- Upstream bundle lives at github.com/veniceai/skills for full scripts and assets
- Frontmatter mode image, category image-generation for agent discovery during planning
- Invoke by skill name or trigger phrases after installing the upstream bundle into the agent skills directory
- 3 trigger phrases in frontmatter
- upstream source github.com/veniceai/skills
Adoption & trust: 783 installs on skills.sh; 61.4k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want Venice-powered image fixes in agent workflows but only have a catalogue stub without triggers, upstream location, or install steps.
Who is it for?
Indie builders already using or evaluating Venice.ai who want Claude Code or Cursor to surface image-edit tasks by name during implementation.
Skip if: Teams that need a self-contained skill with all scripts in-repo—this entry requires cloning the upstream Venice skills bundle.
When should I use this skill?
User says venice image edit, venice upscale, venice background removal, or asks for Venice.ai image API workflows.
What do I get? / Deliverables
The agent discovers venice-image-edit during planning and you install github.com/veniceai/skills so edits and upscales run against the real API workflow.
- Edited, upscaled, or background-removed images via Venice API
- Agent-invoked workflow aligned with upstream Venice skill assets
Recommended Skills
Journey fit
Generative image operations are a build-time integration: you connect an external API while assembling product or marketing assets. Venice-image-edit is an upstream API bundle pointer—canonical shelf is third-party service wiring, not frontend layout or launch distribution.
How it compares
Open Design catalogue pointer to an upstream integration skill, not a built-in MCP image server or local-only generator.
Common Questions / FAQ
Who is venice-image-edit for?
Solo and indie builders shipping visual assets who use Venice.ai and want their coding agent to recognize edit, upscale, and background-removal intents during build planning.
When should I use venice-image-edit?
Use it in Build when you are wiring generative or post-production image steps—product screenshots, marketing hero images, or asset cleanup—after you are ready to add the Venice API skill bundle to your agent.
Is venice-image-edit safe to install?
Treat it as third-party network integration: review the Security Audits panel on this Prism page and audit github.com/veniceai/skills before granting API keys or network access to your agent.
SKILL.md
READMESKILL.md - Venice Image Edit
# venice-image-edit > Curated from the Venice.ai team. ## What it does Image edits, upscaling, and background removal via the Venice.ai API. ## Source - Upstream: https://github.com/veniceai/skills - Category: `image-generation` ## How to use This catalogue entry advertises the skill in Open Design so the agent discovers it during planning. To run the full upstream workflow with its original assets, scripts, and references, install the upstream bundle into your active agent's skills directory: ```bash # Inspect the upstream README for exact paths open https://github.com/veniceai/skills ``` Then ask the agent to invoke this skill by name (`venice-image-edit`) or with one of the trigger phrases listed in this skill's frontmatter.