scenario-labs/skills

scenario-reve

Use when generating or editing images with Reve models on Scenario via MCP: text-to-image from a prompt alone, instruction edits (swap poster text, recolor a product, change materials, relight or restyle a scene), merging references with consistent subjects…

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/scenario-labs/skills --skill scenario-reve

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Scenario Reve Image

Overview

Reve, Reve AI's image family on Scenario, splits into two members that share a brand and little else: v2.1 is a reasoning-driven generator and instruction editor (a top-2 text-to-image arena entry at authoring time), Remix a fast, cheap compositor that blends several images into one. Discover them with search and treat model_schema_get as the contract: they disagree on field names, prompt caps, and ratio lists.

Connection and the core loop: see the scenario skill in this repo; 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 (the live schema wins):

MemberCapabilitiesReferencesPrompt capAspect ratios
Reve v2.1txt2img, img2imgreferences, optional400018 values, 4:1 through 1:4, default auto
Reve Remiximg2imgreferenceImages, required, 1 to 625607 values, 16:9 through 9:16, default 3:2

Three parameters each: the prompt, the reference array, aspectRatio. Neither member has a mask, seed, width and height, negative prompt, or batch-count field, so an edit is scoped by wording and size comes only as a ratio. auto (v2.1 only) picks a fitting shape; pass an explicit ratio when the deliverable demands one.

Pick by job. v2.1 covers generation from a prompt alone and precise edits: swap the text on a poster, recolor a product, change a material, relight or restyle, merge references while every subject stays consistent. Remix blends photos, illustrations, or design assets into one cohesive composite. Where either would do, dry_run both: at authoring time a v2.1 run cost several times a Remix run and took over a minute at p50 against Remix's twenty-odd seconds.

Frame tags wire v2.1 references

In a v2.1 prompt, a reference is addressed with a <frame>N</frame> tag, numbered from 0 in the order the assets appear in references: the first is <frame>0</frame>, the second <frame>1</frame>. Use the tags whenever more than one reference is in play; without them the model guesses which image you mean. Remix documents no tag syntax: name subjects in plain words ("the bottle from the first image, the lighting from the second").

Edits are instructions, not masks

Neither member takes a mask, so the prompt carries the whole edit: state what changes and what must stay untouched. v2.1's reasoning rewards specific plain-language instructions over keyword lists, and its 4000-character budget leaves room for constraints. For masked inpainting on an exact region, use a model that exposes a mask field (see scenario-image).

Worked example: swapping the text on a poster

  1. search with target="models", query="reve", public=true. At authoring time the hits were

model_reve-v2-1 (generation and instruction edits) and model_reve-remix (multi-image blends); re-discover each session.

  1. model_schema_get on the pick: field names, caps, and the ratio list before anything else.
  2. upload_asset the poster (see the scenario skill) to get an asset id.
  3. model_run with that model_id, dry_run=true, and

parameters={"prompt": "Replace the headline on the poster in <frame>0</frame> with 'SUMMER SALE', matching the original font, perspective, and lighting. Change nothing else.", "references": ["asset_x"], "aspectRatio": "auto"} for the cost estimate.

  1. Repeat model_run with wait=false, then jobs_wait with the returned job id, re-called with

pending_job_ids on timeout, never a second model_run.

  1. asset_display to check the swap, then asset_download to save.

Common mistakes

  • Counting frames from 1: <frame>1</frame> is the second reference; the first is

<frame>0</frame>.

  • Carrying a field name across members: v2.1 takes references, Remix takes referenceImages; each

schema lists only its own.

  • Running Remix without references: referenceImages is required (1 to 6 at authoring time);

prompt-only generation belongs to v2.1.

  • Reusing a v2.1 prompt on Remix without checking length: 4000 characters overflow its 2560 cap.
  • Sending width, height, a mask, or a seed: none exists on either member; aspectRatio is the only

size control.

  • Treating a v2.1 jobs_wait timeout as an error: p50 latency topped a minute at authoring time;

re-call with pending_job_ids.

from this repository

More skills

All skills
scenario-labs
Community

scenario-blender-expert

Use when doing any 3D work in Blender through Python or an MCP bridge, headless or in a live session: modeling, sculpting a character or head, retopology, UV unwrapping, baking, texturing, rigging, animating, previs, geometry nodes, lighting and rendering, grease pencil, or finishing an AI-generated mesh into a production asset. Also before exporting or handing off an asset, to check it is ready for a game engine, a render or a 3D print (floating parts, z-fighting, inside-out normals, unapplied

1h installs
3
GitHub stars
4K
Updated
Nov 22
scenario-labs
Community

scenario-blender-sculpting

Use when sculpting in Blender through Python: sculpt a head, face or bust, a stylized or cartoon character, a creature or a realistic portrait; block out from primitives; cut planes, a jaw or gonial angle, cheekbones; fix a jaw or face that looks like a ball or balloon; stylized hair clumps; eyelids; an expression or smirk; plan remesh or multires resolution; reproduce Clay Strips, Crease, Draw Sharp, Scrape, Grab or mask moves without a tablet; final clay renders; or when a sculpt operator cras

1h installs
3
GitHub stars
4K
Updated
Nov 22
scenario-labs
Community

scenario-blender-texturing-shading

Use when texturing, shading or look-developing in Blender: building a PBR material from a texture set, displacement, procedural materials, edge wear, dirt, grime, color variation, decals, box or triplanar mapping on meshes without UVs, stylized character skin (subsurface, pores), eyes and cornea, hand-painted stylized textures, texture painting or painting masks headless. Also when a material looks plastic, CG, waxy or blown out, color spaces are wrong, or EEVEE and Cycles disagree.

1h installs
3
GitHub stars
4K
Updated
Nov 22
scenario-labs
Community

scenario

Use when connecting an AI agent to Scenario (scenario.com) through MCP, or when a task involves generating images, video, 3D, audio, sprites, textures, or game assets. Also when picking a Scenario model, running a LoRA, refining a generation prompt, uploading reference images, waiting on generation jobs, checking credits or quota, hitting Scenario auth, scope, or Forbidden errors, or setting up mcp.scenario.com in Claude Code, Cursor, VSCode, or another agent.

1h installs
2
GitHub stars
4K
Updated
Nov 22