scenario-seedream
Use when generating or editing images with Seedream models on Scenario via MCP: text-to-image, image-to-image editing with reference images, posters or packaging with exact in-image text (non-Latin scripts too), subject-preserving edits, sets of related images in one run, editing a transparent asset…
Install / Use
npx skills add scenario-labs/skills --skill scenario-seedreamInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of scenario-seedream
scenario-seedream scores 84/100 on our quality scale, 2936th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 8.5 KB long, well organised into 8 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 29 days ago, so scenario-seedream is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-seedream compared with similar skills
All 4 of these similar skills score higher than scenario-seedream; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-seedream (this skill)by scenario-labs | 84 | 1.0k | 29d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install scenario-seedream?
- Run
npx skills add scenario-labs/skills --skill scenario-seedream. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-seedream work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-seedream safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-seedream still maintained?
- The repository was last updated 29 days ago, so scenario-seedream is actively maintained.
Skill content
View source on GitHubname: scenario-seedream description: "Use when generating or editing images with Seedream models on Scenario via MCP: text-to-image, image-to-image editing with reference images, posters or packaging with exact in-image text (non-Latin scripts too), subject-preserving edits, sets of related images in one run, editing a transparent asset without losing its alpha, or splitting an image into transparent PNG layers with Layerize. Keywords: Seedream 5.0 Pro, Lite, Flash, 4.5, Layerize, ByteDance, txt2img, img2img, layer extraction." license: MIT
Scenario Seedream Images
Overview
Seedream, ByteDance's image family on Scenario, spans generation, reference-driven editing, and one
member that only takes images apart: Layerize splits a finished image into editable layers. The
members agree on little else, so discover them with search and read model_schema_get before
every run.
Connection and the core loop: see the scenario skill; model-agnostic image work: the
scenario-image skill. If a sibling skill named here is missing from your available skills, load it
with skill_get (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag
the gap.
Quick reference
At authoring time (fields and caps are per member, read the live schema):
| Member | References | Sizing | Notes |
| ------------------ | --------------------------- | --------------------------------------------------- | ----------------------------------------------------------- |
| 5.0 Pro | referenceImages, up to 10 | exact width and height, 672 to 3136 px, step 16 | exact in-image text; 3500-char prompt |
| 5.0 Lite | referenceImages, up to 14 | width and height, up to 4K | fast and cheap; 2048-char prompt |
| 5.0 Flash | referenceImages, up to 10 | exact width and height, 672 to 3136 px, step 16 | cheapest; background keeps a reference's alpha |
| 4.5 | referenceImages | size (2K, 4K) plus aspectRatio enum | subject-preserving edits; "auto" ratio follows the source |
| 5.0 Pro Layerize | one image, required | size tier: auto, 1K, 1.5K, 2K | splits, never generates; prompt optional |
| 5.0 Flash Layerize | one image, required | size tier: auto, 1K, 1.5K, 2K | same contract minus optimizePromptMode |
On the generators, mode follows from the inputs: empty referenceImages is text-to-image, one or
more is an edit or a multi-reference generation (with several, the prompt gives each reference a
role by position), and the array shape holds even for one asset. Sequence mode
(sequentialImageGeneration: "auto" plus maxImages) lets Lite and 4.5 return a related set in one
run, input plus generated capped at 15 images; Pro has no sequence fields. Price per image differs
widely: a 2048 px square quoted 4 CU on Flash, 6 on Lite, and 18 on Pro at authoring time, and Pro
took about two minutes against under one, so iterate on the cheap members and spend Pro on finals;
dry_run both before a batch (the estimate prices the run exactly as submitted, a whole sequence
included). Pro and Pro Layerize carry optimizePromptMode: the default standard reasons about the
prompt first and is slower; fast costs the same and is usually enough when a reference already
sets the composition (on Layerize it trades some split fidelity for speed). Flash's schema says
width and height apply only when Resolution is Custom, but Flash has no Resolution field: the
pixels apply directly.
Keeping a transparent asset transparent
Flash's background: "transparent" preserves alpha through an edit; it does not cut a subject out.
It keeps the transparent surround, not translucency inside the subject: glass at alpha 170 came back
near-opaque in one authoring-time test, so composite a translucent part in post. The field defaults
to opaque, so a restyle that omits it flattens a valid cutout: set it on every run that must stay
transparent. It applies only with exactly one reference image that already carries an alpha channel,
and is ignored otherwise: a text-only run, a flattened JPEG reference, or two references all come
back opaque without an error. So restyle or recolor an existing cutout (a sprite, an icon, a prop)
on Flash with the PNG as the one reference, and check the result's alpha on the downloaded file
before shipping it, since asset_display composites transparency away: with Pillow
(uv run --with pillow when it is missing), Image.open(path).getchannel("A").getextrema() should
start at 0 (fully transparent pixels exist), and an image with no A channel was flattened. To get
a cutout in the first place, generate on a plain field and run background removal (the
scenario-image-editing skill), or split the image with Layerize.
Write the exact copy into the prompt
Pro renders legible in-image text, multi-line layouts and non-Latin scripts included. Quote the
exact strings in the prompt instead of paraphrasing them, give each a position and a size rank
(headline across the top, date line small at the foot), and keep to a few elements at one or two
sizes: letters are drawn, not typeset, so paragraphs and many small labels turn to shapes, and copy
past that budget (tour dates, credits) is composited in post from the start. Proofread with
asset_display; a word that garbles is spelled out letter by letter after the quoted string on the
rerun, and one that still garbles goes to post. To swap copy on a reference, quote the new string,
pin its position, and require the original typeface, size and color with everything else unchanged.
Layerize: one image in, an editable stack out
Layerize returns a base layer plus up to 16 transparent PNG cutouts, rebuilding the background
behind whatever it lifts. The prompt picks the mode: empty runs a full automatic split; an
enumerated list of parts ("Separate this poster into transparent layers: headline, product, shadow,
background") cuts better than "all layers"; <bbox>x1 y1 x2 y2</bbox> on a 0 to 1000 grid, origin
top left, confines the split to one region. Set size explicitly, since auto inherits the source's
tier and the tier moves the price; cost is otherwise flat per run, not per layer. Layers come back
cropped to their own bounds with bbox and z-index metadata, not aligned to the source canvas, and
there is no PSD export.
Worked example: a poster, then its layers
searchwithtarget="models",query="seedream",public=true. Prefer the newest non-deprecated hit for the job, e.g.model_bytedance-seedream-5-0-pro(a live hit at authoring time: re-discover each session).model_schema_getwith that id: sizing fields, caps, defaults.model_runwith that id,dry_run=true, andparameters={"prompt": "Concert poster, teal and cream, screen-print grain. Headline \"MIDNIGHT ORBIT\" across the top, date line \"Nov 14, Union Hall\" small at the foot.", "width": 1600, "height": 2368}; both sizing fields move price.- Rerun
model_runwithwait=false, thenjobs_waitwith the returned job id, re-called withpending_job_idson timeout, never a secondmodel_run. asset_displayand proofread the rendered text.model_schema_geton the Layerize hit, thenmodel_runwith that id andparameters={"image": "<poster asset id>", "prompt": "Separate this poster into transparent layers: the headline text, the date line, and the background. Clean edges, complete transparency.", "size": "2K"}.jobs_wait, thenasset_displayeach layer andasset_downloadthe keepers.
Common mistakes
- Reusing one member's parameter block on another: pixels on Pro and Lite, tier enums on 4.5 and Layerize; pixels sent to an enum field are rejected.
- Passing
referenceImagesto Layerize orimageto the generators: the input field's name and shape differ per member. - Expecting Layerize layers to overlay the source directly: each is cropped to its own bounds, so reposition with the returned metadata.
- Asking Pro for a sequence: the sequence fields existed on Lite and 4.5 only.
- Moving a 3000-character prompt from Pro to Lite: prompt caps are per member.
- Setting Flash's
backgroundtotransparenton a text-only run or a flattened reference: it is silently ignored, and the image comes back opaque.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
