scenario-multi-reference
Use when one image must be composed from several reference pictures through the Scenario MCP server, each lending one thing: the character from one, the place, pose, style, light, palette, material, outfit, or layout from others.
Install / Use
npx skills add scenario-labs/skills --skill scenario-multi-referenceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of scenario-multi-reference
scenario-multi-reference scores 88/100 on our quality scale, 1967th of 4,698 Development & Engineering skills we index (top 42%).
Its SKILL.md is 10 KB long, split into 7 sections with 2 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-multi-reference 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-multi-reference compared with similar skills
All 4 of these similar skills score higher than scenario-multi-reference; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-multi-reference (this skill)by scenario-labs | 88 | 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-multi-reference?
- Run
npx skills add scenario-labs/skills --skill scenario-multi-reference. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-multi-reference 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-multi-reference 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-multi-reference still maintained?
- The repository was last updated 29 days ago, so scenario-multi-reference is actively maintained.
Skill content
View source on GitHubname: scenario-multi-reference description: "Use when one image must be composed from several reference pictures through the Scenario MCP server, each lending one thing: the character from one, the place, pose, style, light, palette, material, outfit, or layout from others. Also when a reference leaks into the result (its object, colors, or face showing where it should not) or a reference's role is ignored. Keywords: multi-reference, reference roles, combine references, style reference, pose reference, give each picture a job." license: MIT
Scenario Multi-Reference Composition
Overview
A reference image lends everything it shows unless the prompt says otherwise: hand a model a raccoon
chef as a style reference and the raccoon walks into the scene. The fix is to give each picture
exactly one job, then say, for every picture, what not to take from it. Four or five pictures,
one idea each (a drawing, a photo, a mannequin, a film still, a color swatch), compose into one
image that keeps each contribution and nothing else. Connection and the generation loop: see the
scenario skill. Per-family reference caps and syntax: scenario-image lists the image
model-family skills. One subject held across many images: scenario-consistency. Animating the
result: scenario-video. Refusals: scenario-moderation. 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
| Job | The picture lends | Typical "not" line | | ------------------ | ---------------------------- | ---------------------------------------------------------------- | | Main subject (WHO) | the character, product | "Use only the idea of a gecko. Do not copy the photo's colors." | | Stage (WHERE) | the place | "redrawn as woodblock architecture" when the medium differs | | Pose | the body pose | "Do not show the mannequin or any wood." | | Angle | the camera | "Do not include the lighthouse." | | Style | medium, render, texture | "Do not include the raccoon, the kitchen, the apron or the pot." | | Light | the light only | "Do not include the flowers or vase." | | Palette | the only allowed colors | "No green anywhere." | | Material | a surface | "Do not show any fish, fins or water." | | Expression | the mood of a face | "No human skin, no nose, no ears, no hair." | | Wear | clothing or armor | "The cat's own face stays visible; no human face mask." | | Inspiration | a design idea, not the thing | "a gown designed from this jellyfish. Do not show a jellyfish." | | Layout | grid and composition | "Do not copy the word MONDAY." |
The prompt, one line per picture (the kept prompts wrote Main subject and Stage as WHO and WHERE):
<One sentence naming the medium.> Each reference picture has exactly one job:
Image N (<what it shows>) = <JOB> only. <What it lends, concretely.> Do not <what to leave out>.
...
<Framing: shot size, placement, mood, text rules.>
Rules that held
- One job per picture. Two jobs on one card (subject plus palette) blur both. A card kept in the call but unused gets "Image 4 = no job: ignore it completely."
- One main subject. Two identities in one run split attention; compose them per
scenario-consistency. - The job most likely to be ignored goes first, usually Style, with "This is the most important job". A clay scene came back as chrome CG until the Style line moved to the top.
- Lend concretely. "Copy its 3D render look, soft materials, warm bounce light" beats "use its style". A palette job names each element's color ("the gecko is Prussian blue with vermilion spots"); "palette only" barely recolors.
- Settle conflicts between jobs. Every picture carries more than its job, so a Style card brings its own colors and a subject photo its own fur. With a Palette card, the Style line adds "do not copy its colors", and the subject's colors are named from the swatch. When that recolors something the user cares about (their dog, their product), ask before running; unattended, follow the task instructions, else keep the subject's own colors and report the conflict.
- Idea, not copy. When a subject photo must not survive literally: "Use only the idea of a gecko ... Do not copy the photo's pose, lighting, colors or realism."
- Text is quoted exactly with "No extra words, no duplicate text"; copy that must be
letter-perfect goes to
scenario-text-overlay. - Clean cards. Plain backgrounds, no readable signs or logos. The user's own pictures are best; generate a missing card with a text-to-image run, one idea per card.
Worked example: a crayon drawing becomes a film still
Cards: a child's crayon monster (Main subject), a backyard photo (Stage), a wooden mannequin leaping (Pose), a 3D animated film still of a raccoon chef (Style).
upload_asseteach card, thenupload_asset_complete(seescenario). Keep the asset ids in the order you will number them.recommendwithcapability="img2img",features=["referenceImages"](keeps only members exposing that exact field; drop it to see members that name the slot differently), and the user's own words asprompt. Handlenext_stepasscenariodirects.model_schema_geton the pick. Read: the reference field's cap (four or five cards fit the leading members at authoring time, up to ten on some),array: true, how the description says the prompt addresses references (by order as "Image 1", or by tags such as@Image1on some families), the sizing family, and the quality tier. When the schema offers a dedicated slot for a job (a style-reference field, a pose control), put that card there instead of in the reference array (scenario-consistency), and read the field description for how the prompt refers to it, since prompt numbering follows the array.model_runwithdry_run=true(top-level, besidemodel_id, never insideparameters) and the schema's own names, for exampleparameters={"prompt": "<below>", "referenceImages": ["asset_monster", "asset_yard", "asset_mannequin", "asset_raccoon"], "quality": "high"}plus its sizing fields. Quote the user the total, any cards still to generate and the film included when one is wanted (a dry run rejects a payload missing its required image, so price against any uploaded picture, a small stand-in when no card exists yet), and run nothing paid until they agree (unattended, launch only inside a budget the task states; otherwise stop and report the quote). Then the same call withwait=false,jobs_wait, andasset_display.
A still frame from a 3D animated family feature film. Each reference picture has exactly one job:
Image 1 (child's crayon drawing) = WHO. Turn this crayon monster into a soft, plush 3D animated character: round purple body, three uneven eyes, spiky green hair, tiny orange legs, big toothy smile. Keep its lopsided, hand-drawn charm.
Image 2 (backyard photo) = WHERE. Use this exact backyard: lawn, wooden fence, red hose, blue kiddie pool, swing set, lemon tree.
Image 3 (wooden mannequin) = POSE only. The monster leaps mid-air with both arms thrown up and one knee raised, exactly like the mannequin. Do not show the mannequin or any wood.
Image 4 (raccoon chef frame) = STYLE only. Copy its 3D render look, soft materials, warm bounce light and rich color. Do not include the raccoon, the kitchen, the apron or the pot.
Wide shot, the monster in the center above the lawn, afternoon sun, joyful.
- Check every picture for a leak (below). Fix by tightening that picture's line and running again, never by retouching.
- To animate it, hand the result to
scenario-videoas the first frame. The film prompt carries no jobs, only motion, camera, and sound: the frame already holds every job.
Seven more kept prompts across claymation, product ad, woodblock print, fashion editorial, pixel art, tilt-shift miniature, and risograph poster, each with its film prompt: references/prompt-patterns.md.
Leak check before keeping
For each picture, ask two questions: is its job visible, and is anything else from it visible?
- Pose and Angle: no mannequin, no wood, no prop from the sketch.
- Style: none of the style reference's own subject, set, or objects.
- Expression: the mood moved, the face did not (no human nose or skin on a toaster).
- Layout: the grid moved, the reference's own words did not.
- Palette: no color outside the swatch.
Before rewriting a line for an ignored job, asset_get the output: metadata.referenceImages lists
what the run consumed, and a reference sent as a bare string where the schema says array: true was
dropped silently, so no wording brings its job back.
Common mistakes
- The main subject copied the photo. A green gecko photo came back as the same green gecko in a woodblock print. Put Style first, use "only the idea of", and make the palette strict.
- A logo by accident. Red, white and blue swooshes on generated billboards read as a soda brand: the image-to-video model refused the frame, and the image editor then refused it as input. Say what billboards and signs show (waves, clouds, cranes).
- Brands in a reference. A street photo with real shop signs was refused as a reference. Regenerate the card with "invented, blank signs, no logos".
- A protected design named in the prompt. A famous chair named outright was refused. Describe an original design instead.
- A garment blocked by the safety filter. A translucent gown was refused; "opaque, fully covered, high-necked" passed.
- Drift in the film. A guitar changed color mid-clip. Ask for "almost static", list what must not change, and move only what should.
- Hardcoding a model id or price. Discover with
recommend, read caps offmodel_schema_get, price withdry_run=true.
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.
