scenario-luma-image
Use when generating or editing images with Luma Uni-1 models on Scenario via MCP: text-to-image, prompt-based editing of an existing image, style or character reference images with named roles, web search grounding for real-world subjects, rendering exact title text into posters, aspect ratio contro…
Install / Use
npx skills add scenario-labs/skills --skill scenario-luma-imageInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of scenario-luma-image
scenario-luma-image scores 82/100 on our quality scale, 3394th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 6.1 KB long, split into 7 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-luma-image 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-09. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-luma-image compared with similar skills
All 4 of these similar skills score higher than scenario-luma-image; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-luma-image (this skill)by scenario-labs | 82 | 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-luma-image?
- Run
npx skills add scenario-labs/skills --skill scenario-luma-image. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-luma-image 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-luma-image 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-luma-image still maintained?
- The repository was last updated 29 days ago, so scenario-luma-image is actively maintained.
Skill content
View source on GitHubname: scenario-luma-image description: "Use when generating or editing images with Luma Uni-1 models on Scenario via MCP: text-to-image, prompt-based editing of an existing image, style or character reference images with named roles, web search grounding for real-world subjects, rendering exact title text into posters, aspect ratio control, or choosing between Uni-1 Max and Uni-1. Keywords: Luma Labs, Uni-1, Photon, txt2img, img2img, image edit, reference images, webSearch, reasoning image model." license: MIT
Scenario Luma Image
Overview
Uni-1, Luma Labs' image family on Scenario, folds generation and editing into one contract: every
member is both txt2img and img2img, and passing a source image is what flips the run into edit
mode, so where each image lands (source versus reference) decides more than prompt wording. These
are reasoning models that plan lighting and composition before rendering, so a run takes a minute or
two, not seconds. Discover members with search and treat model_schema_get as the contract: the
tiers share every field name and disagree on caps and price. Luma's video models are the
scenario-luma-video skill's domain.
Connection and the core loop: see the scenario skill in this repo; model-agnostic image work
(sizing families, masks, batch fields): 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
Mode follows from the inputs (names from the live schema):
| Mode | Inputs | Behavior |
| ------ | ---------------------------------- | ----------------------------------------------------------------------------------- |
| Create | prompt (+ imageRef) | full scene from the prompt; aspectRatio honored, default 3:2 |
| Edit | source + prompt (+ imageRef) | prompt states the change; output keeps the source ratio unless aspectRatio is set |
imageRef is an array of guiding images and combines with source. Caps are per member: at
authoring time the Max hit took 9 references and the standard 8, with the source occupying one of
those slots when editing; both took a 6000 character prompt, nine aspectRatio values from 1:3 to
3:1, and outputFormat png (default) or jpeg. Each reference adds cost, so re-estimate with
dry_run after changing the count. webSearch (default false) has the model fetch real-world
visuals before generating: enable it when the prompt names a real place, product, or style the model
may not know. No seed, mask, pixel-size, or batch-count field exists: sizing is the ratio alone,
masked edits belong to other models, and identical re-runs cannot be pinned, so change one thing per
iteration. At authoring time the Max tier cost roughly two and a half times the standard for one 2K
image despite near-identical public arena ratings, so dry_run the same job on both before a batch.
References work by role
The model follows a reference reliably only when the prompt says what to take from it: character likeness, style, composition, color palette, lighting, texture, or mood. Unlabeled references get guessed at, and there is no adherence slider; influence rises with prompt specificity ("use the first reference for the exact colorway and stitching"). Roles stack across references, one each. Reusing one canonical reference across iterations is what holds a character steady.
Create prompts describe, edit prompts preserve
Create prompts read as one scene in natural prose: subject, setting, lighting, mood, style, and always name the lighting, the single biggest quality lever. For text in the image, put the exact string in quotes; rendered text is a family strength, and the Max tier's advertised edge is accurate non-Latin scripts, not Latin text generally. Edit prompts are surgical: state the change first, then pin what must not move ("Change X to Y. Keep Z exactly as it is."). One scene or one change per run.
Worked example: a travel poster with rendered title text
searchwithtarget="models",query="luma uni",public=true. Prefer the newest non-deprecated hit, e.g.model_luma-uni-1-max(a live hit at authoring time: re-discover each session).model_schema_getwith that id: reference cap, ratio list, and defaults before anything else.upload_assetthe palette reference (see thescenarioskill) to get its asset id.model_runwith thatmodel_id,dry_run=true, and the exactparameters={"prompt": "A travel poster of Kyoto in autumn, a pagoda above red maples, warm golden hour light, flat-print texture. Use the reference for color palette and print grain. The title text \"KYOTO\" in bold serif across the top.", "imageRef": ["asset_a"], "aspectRatio": "2:3", "webSearch": true}(a real place is named, so ground it).- Repeat
model_runwithwait=false, thenjobs_waitwith the returned job id, re-called withpending_job_idson timeout. The model reasons before rendering (median latency near 90 seconds at authoring time), so a timeout is not a failure and never justifies a secondmodel_run. asset_displayto check the title spelling and palette, thenasset_downloadto save.
Common mistakes
- A style reference passed as
source: that flips the run into edit mode and the output hugs the reference. References go inimageRef;sourceis only the image being changed. - Unlabeled references: name each one's role in the prompt or the model guesses which to follow.
- An edit prompt with no preservation clause: whatever is not pinned is fair game.
- Expecting a square by default: create mode defaults to 3:2, so set
aspectRatioexplicitly. - Hunting for
seed,mask,width, or a batch count: none exist at authoring time; readmodel_schema_getinstead of assuming. - Carrying the Max member's reference cap or price to the standard one: they share field names, not numbers.
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.
