Agent skill

Scenario Multi Reference

by scenario-labs in scenario-labs/skills

A skill your agent uses 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…

MITAuto-check passedAgent Workflows

Install Scenario Multi Reference

skills CLI
$ npx skills add scenario-labs/skills --skill scenario-multi-reference -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install scenario-labs/skills scenario-multi-reference --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scenario-multi-reference .claude/skills/scenario-multi-reference && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
scenario-multi-reference
GitHub stars
946
Token cost
~2.6k tokens
SKILL.md length
1,261 words
Files
3 (incl. references)
Skills in repo
146
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • Works in 6 steps: upload_asset each card, then… → recommend with capability="img2img",… → model_schema_get on the pick. Read: the… → …
  • One image must be composed from several reference pictures through the Scenario MCP server
  • SKILL.md covers Overview, Quick reference, Rules that held and Worked example: a crayon…, plus 2 more sections
  • Calls npx

What it does

Scenario Multi Reference is an agent skill from scenario-labs/skills. 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.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `README.md` and `references/prompt-patterns.md`).

It sits in Agent Workflows, covering Banking and insurance. It works with Model Context Protocol. The repository describes itself as: Get production-ready images, video, audio, and 3D from any AI agent: skills that pick the right model, price before spending, and keep characters and brands consistent through… The licence is MIT.

When your agent uses it

  • One image must be composed from several reference pictures through the Scenario MCP server
  • Each lending one thing: the character from one
  • Layout from others

Example prompts

  • “/scenario-multi-reference”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. upload_asset each card, then upload_asset_complete (see scenario). Keep the asset ids in the order you will number them.
  2. recommend with capability="img2img", features=["referenceImages"] (keeps only members exposing that exact field; drop it to see members…
  3. model_schema_get on the pick. Read: the reference field's cap (four or five cards fit the leading members at authoring time, up to ten on…
  4. model_run with dry_run=true (top-level, beside model_id, never inside parameters) and the schema's own names, for example…
  5. Check every picture for a leak (below). Fix by tightening that picture's line and running again, never by retouching.
  6. To animate it, hand the result to scenario-video as the first frame. The film prompt carries no jobs, only motion, camera, and sound: the…

What it can do on your machine

Read from SKILL.md and the folder at commit f6f8ab7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scenario Multi Reference loads about 2.6k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 128 tokens; SKILL.md has 1,261 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from scenario-labs/skills at commit f6f8ab7, republished under its MIT licence (© scenario-labs). 1,261 words, ~2,625 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-multi-reference/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
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, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.

Quick reference

JobThe picture lendsTypical "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
Posethe body pose"Do not show the mannequin or any wood."
Anglethe camera"Do not include the lighthouse."
Stylemedium, render, texture"Do not include the raccoon, the kitchen, the apron or the pot."
Lightthe light only"Do not include the flowers or vase."
Palettethe only allowed colors"No green anywhere."
Materiala surface"Do not show any fish, fins or water."
Expressionthe mood of a face"No human skin, no nose, no ears, no hair."
Wearclothing or armor"The cat's own face stays visible; no human face mask."
Inspirationa design idea, not the thing"a gown designed from this jellyfish. Do not show a jellyfish."
Layoutgrid 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):

text
<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.
Show full SKILL.md (662 more words)Show less

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).

  1. upload_asset each card, then upload_asset_complete (see scenario). Keep the asset ids in the order you will number them.
  2. recommend with capability="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 as prompt. Handle next_step as scenario directs.
  3. model_schema_get on 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 @Image1 on 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.
  4. model_run with dry_run=true (top-level, beside model_id, never inside parameters) and the schema's own names, for example parameters={"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 with wait=false, jobs_wait, and asset_display.
text
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.
  1. Check every picture for a leak (below). Fix by tightening that picture's line and running again, never by retouching.
  2. To animate it, hand the result to scenario-video as 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 off model_schema_get, price with dry_run=true.

© scenario-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/scenario-multi-reference of scenario-labs/skills.

  • SKILL.md
  • README.md
  • references/prompt-patterns.md

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Multi Reference next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scenario Multi Reference compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Multi Reference this skillscenario-labs/skills946—~2.6kAutomated safety check: PassMIT
BNB Chain MCP Serverinternet-court/internet-court-skill6.6k1 repos~1.7kAutomated safety check: PassMIT
Dd Report FormatAbilityai/trinity636—~707Automated safety check: PassApache-2.0
Banknoskillish/bankmcp277—~1.1kAutomated safety check: PassMIT
Dd Risk ScoringAbilityai/trinity636—~736Automated safety check: PassApache-2.0
Skill Design Referencelow-hands/MyCareer108—~2.3kAutomated safety check: PassMIT

Similar skills

  • BNB Chain MCP Server

    internet-court/internet-court-skill

    Connects an agent to the BNB Chain MCP server to read blocks and contracts, move tokens and NFTs, register ERC-8004 agents and use Greenfield storage.

    6.6k GitHub starsUsed in 1 repo~1.7k tokens
    Agent WorkflowsAuto-check passed
  • Dd Report Format

    Abilityai/trinity

    Standard output format for due diligence analysis reports. An agent skill from Abilityai/trinity.

    636 GitHub stars~707 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Bank

    noskillish/bankmcp

    Answer questions about the user's own bank accounts and money using the bank MCP tools (listaccounts, getbalances, gettransactions, watches).

    277 GitHub stars~1.1k tokensUpdated 12 days ago
    Agent WorkflowsAuto-check passed
  • Dd Risk Scoring

    Abilityai/trinity

    Calculate weighted risk scores from specialist agent reports.

    636 GitHub stars~736 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Skill Design Reference

    low-hands/MyCareer

    A skill your agent uses when creating or reviewing a Skill package for this Career Agent, including its SKILL.md, progressive disclosure, tool workflow, MCP coordination, subagent boundaries…

    108 GitHub stars~2.3k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Setup

    noskillish/bankmcp

    Set up BankMCP™ on this machine step by step: check Node, register the local MCP server, walk through the Enable Banking application, finish the setup page and connect the first bank.

    277 GitHub stars~805 tokensUpdated 12 days ago
    Agent WorkflowsAuto-check passed

More from scenario-labs/skills

All 146 skills in this repo
  • Scenario Blender Grease Pencil

    scenario-labs/skills

    A skill your agent uses when drawing or animating with Grease Pencil in Blender 5.x from Python: 2D or 2.5D illustration, frame-by-frame animation, a cutout or part-based 2D character, strokes with…

    946 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Scenario Blender Hair

    scenario-labs/skills

    A skill your agent uses when grooming hair or fur in Blender with hair curves, such as a character hairstyle, animal fur, procedural fur in geometry nodes, or hair cards and mesh hair for games.

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when lighting, rendering or compositing in Blender: light a character, product or hero shot, interior at dusk or night, three-point or motivated lighting, sun and sky, HDRI…

    946 GitHub stars~5k tokensUpdated yesterday
    Auto-check passed
  • Scenario Chatgpt Pet Create

    scenario-labs/skills

    A skill your agent uses when creating a ChatGPT pet or Codex pet with Scenario: hatching an animated companion from a text idea, a character, mascot or brand cue, or reference photos and art; making…

    946 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Scenario Godot Animation

    scenario-labs/skills

    A skill your agent uses when animating characters or scenes in Godot 4.7: AnimationPlayer clips and RESET, AnimationTree state machines and blend spaces built in code, Mixamo or glTF import, loop…

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • Scenario Godot Audio

    scenario-labs/skills

    A skill your agent uses when adding or fixing sound in Godot 4.7: audio buses and effects, volume sliders, 'too many sounds', combat audio with hundreds of enemies, sounds clipping or distorting, 3D…

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed

Questions about Scenario Multi Reference

What does Scenario Multi Reference do?

A skill your agent uses 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…. Scenario Multi Reference is an agent skill from scenario-labs/skills. 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.

When should I use Scenario Multi Reference?

Scenario Multi Reference fits situations like: one image must be composed from several reference pictures through the Scenario MCP server; each lending one thing: the character from one; layout from others.

How do I install Scenario Multi Reference in Claude Code?

Run `npx skills add scenario-labs/skills --skill scenario-multi-reference -a claude-code`. Or copy the skill folder (skills/scenario-multi-reference in scenario-labs/skills) into .claude/skills/scenario-multi-reference in your project. Claude Code loads it when a task matches its description.

How do I install Scenario Multi Reference in Codex?

Run `npx skills add scenario-labs/skills --skill scenario-multi-reference -a codex`. Or copy the skill folder (skills/scenario-multi-reference in scenario-labs/skills) into .agents/skills/scenario-multi-reference in your project. Codex loads it when a task matches its description.

Can I use Scenario Multi Reference in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add scenario-labs/skills --skill scenario-multi-reference -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-multi-reference, .gemini/skills/scenario-multi-reference, .github/skills/scenario-multi-reference and .opencode/skills/scenario-multi-reference in your project.

What does Scenario Multi Reference need to run?

Going by SKILL.md and its folder, Scenario Multi Reference needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Scenario Multi Reference access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Scenario Multi Reference safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Scenario Multi Reference use?

Scenario Multi Reference is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scenario Multi Reference use?

About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.

What are the alternatives to Scenario Multi Reference?

Skills that share tags, products or a category with Scenario Multi Reference: BNB Chain MCP Server (internet-court/internet-court-skill, 6.6k stars), Dd Report Format (Abilityai/trinity, 636 stars), Bank (noskillish/bankmcp, 277 stars) and Dd Risk Scoring (Abilityai/trinity, 636 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Multi Reference?

scenario-labs (a GitHub organization) maintains it in scenario-labs/skills, which has 946 GitHub stars. The repository holds 146 skills in this directory. The repository was last updated on October 10, 2026.

Source: scenario-labs/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.