Agent skill

Scenario Orbit Views

by scenario-labs in scenario-labs/skills

A skill your agent uses when a single image of a character, creature, prop, vehicle, or building must be seen from new camera angles through the Scenario MCP server: turnarounds, a 360 orbit, views…

MITAuto-check passedAgent Workflows

Install Scenario Orbit Views

skills CLI
$ npx skills add scenario-labs/skills --skill scenario-orbit-views -a claude-code

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

GitHub CLI
$ gh skill install scenario-labs/skills scenario-orbit-views --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-orbit-views .claude/skills/scenario-orbit-views && 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-orbit-views
GitHub stars
946
Token cost
~2.3k tokens
SKILL.md length
1,161 words
Files
6 (incl. scripts)
Skills in repo
146
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a single image of a character, creature, prop, vehicle, or building must be seen from new camera angles through the Scenario MCP server: turnarounds, a 360 orbit, views…

  • Works in 8 steps: upload_asset the user's picture (or… → recommend an image-to-3D model with the… → Find a skybox model with search… → …
  • A single image of a character
  • SKILL.md covers Overview, Quick reference, Worked example: eight views… and Common mistakes
  • Runs Python scripts from its folder; calls python3, npx and curl

What it does

Scenario Orbit Views is an agent skill from scenario-labs/skills. Use when a single image of a character, creature, prop, vehicle, or building must be seen from new camera angles through the Scenario MCP server: turnarounds, a 360 orbit, views from behind, above, below, or straight down, consistent multi-angle renders on the same grounded background or on transparency, or novel views that go through a 3D intermediary instead of guessing.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `README.md`, `scripts/compose_layout.py` and `scripts/match_view.py`).

It sits in Agent Workflows, covering Creative writing and fiction and MCP servers. It works with Model Context Protocol and Blender. 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

  • A single image of a character
  • Building must be seen from new camera angles through the Scenario MCP server: turnarounds
  • Views from behind
  • Consistent multi-angle renders on the same grounded background

Example prompts

  • “/scenario-orbit-views”

Requirements

  • Python 3
  • Node.js

Workflow steps

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

  1. upload_asset the user's picture (or generate one with a plain background and the camera above), upload_asset_complete.
  2. recommend an image-to-3D model with the user's words ("untextured mesh from one image"), plus max_cost_cu when the user set a budget, then…
  3. Find a skybox model with search (target="models", query="skybox", public=true, as scenario-skyboxes teaches; recommend has no skybox…
  4. blender ... render_grounded.py -- --glb hero.glb --out search --search, then python3 match_view.py hero.png search/cameras.json. The top…
  5. blender ... render_grounded.py -- --glb hero.glb --pano world.png --out views --az0 --elev --only 00,02,04,06,08,10,12,14,top (the eye…
  6. Upload each layout_.jpg. recommend an image model for reference-guided repainting, and check that its model_schema_get lists…
  7. jobs_wait in batches of 32 or fewer. asset_download every result and build a contact sheet of all views. Regenerate only the views that…
  8. Transparent set: recommend a background-removal model, read its image field from model_schema_get, run it on each repainted asset id (not…

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

    Ships 4 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • npx
    • curl

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

  • Network

    No URLs in SKILL.md. Its commands use npx and curl, 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 Orbit Views loads about 2.3k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 1,161 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

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); the scripts in this folder are not scanned.

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/scenario-orbit-views/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
scenario-orbit-views
description
Use when a single image of a character, creature, prop, vehicle, or building must be seen from new camera angles through the Scenario MCP server: turnarounds, a 360 orbit, views from behind, above, below, or straight down, consistent multi-angle renders on the same grounded background or on transparency, or novel views that go through a 3D intermediary instead of guessing.
license
MIT

Scenario Orbit Views

Overview

Asking an image model to "show it from behind" guesses the geometry, and each angle drifts in size, pose, and ground contact. The reliable route puts a 3D step in the middle: rebuild the subject as an untextured mesh, render a gray clay layout for every camera, then let a reference-capable image model repaint each layout from the original picture. The mesh fixes silhouette, scale, and perspective; the picture supplies identity, colors, and finish. Connection and the core generation loop: see the scenario skill. Image-to-3D model choice: scenario-3d. The background panorama: scenario-skyboxes. 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.

The Blender steps run locally in a shell with Blender 4.x or later; everything that generates goes through MCP tools. Check for Blender before the first paid step (on macOS it is usually /Applications/Blender.app/Contents/MacOS/Blender, not on the PATH). When it is missing, ask the user to install it, or unattended, stop and report it: no MCP tool renders a mesh from chosen cameras.

Quick reference

StepHow
Source pictureOne subject, whole body with margin, plain background, a known camera (slightly above eye level, turned about 30 degrees)
Meshrecommend an image-to-3D model, geometry only (texture is not needed), asset_download the GLB
WorldA skybox panorama in the same art style, flat open floor all around the viewpoint
Camera zerorender_grounded.py --search, then match_view.py, confirmed by eye
Layoutsrender_grounded.py, then compose_layout.py: background, clay, real cast shadow per camera
Uploadupload_asset with file_size, PUT the parts, upload_asset_complete, one per layout
RepaintReference-capable image model, referenceImages: [layout, source], prompt below
No backgroundBackground-removal model on the same repainted frame, then studio_shadow.py
Waitjobs_wait takes at most 32 ids per call; re-call with pending_job_ids

All four scripts are run by the agent in a local shell, not by the MCP server. render_grounded.py runs inside Blender (blender -b --factory-startup --python render_grounded.py -- ...); the other three need Python with Pillow and numpy. Each prints its usage when run without arguments.

Worked example: eight views plus top-down of one character

  1. upload_asset the user's picture (or generate one with a plain background and the camera above), upload_asset_complete.

  2. recommend an image-to-3D model with the user's words ("untextured mesh from one image"), plus max_cost_cu when the user set a budget, then model_schema_get and model_run with dry_run=true to price (image-to-3D jobs are expensive; a dry run rejects a payload missing its required image, so a quote for the whole chain before the source exists prices against any uploaded picture), then wait=false and jobs_wait. asset_download the GLB and save it with curl -L.

  3. Find a skybox model with search (target="models", query="skybox", public=true, as scenario-skyboxes teaches; recommend has no skybox capability and can return a generic image model whose edges do not wrap) and generate one panorama in the picture's style, prompting for "viewpoint standing in the middle of an open empty floor at eye level, the floor clearly visible all around, no people". Download it.

  4. blender ... render_grounded.py -- --glb hero.glb --out search --search, then python3 match_view.py hero.png search/cameras.json. The top row's azimuth and elevation are <az> and <el> below; open the matching search/search_az..._el...png next to the picture to confirm, since front and back can score alike.

  5. blender ... render_grounded.py -- --glb hero.glb --pano world.png --out views --az0 <az> --elev <el> --only 00,02,04,06,08,10,12,14,top (the eye ring has 16 cameras, 22.5 degrees apart; --height sets the panorama eye height, --yaw turns the world, --zoom the framing). Keys count from camera zero, not from the subject's front, so with a turned source key 08 shows the back at that same turn; for views square to the subject, render into another --out with --az0 set to the search frame where it faces the camera squarely. Then python3 compose_layout.py views. Look at every layout: the clay must stand on the floor, with the shadow under it.

  6. Upload each layout_<key>.jpg. recommend an image model for reference-guided repainting, and check that its model_schema_get lists referenceImages (1024 square, a high quality tier and an opaque background worked well). Price one with dry_run=true (the quote covers one view: multiply by the view count before launching), then launch one model_run per view with wait=false, referenceImages: ["<layout asset>", "<source asset>"], and:

    Image 1 is the exact final frame: a plain gray clay 3D model standing on the ground of a finished background, with its real cast shadow, seen from the exact camera angle wanted. Image 2 is the original design reference of the {kind}. Repaint the gray clay model as {what}, matching Image 2 for identity, design, materials and colors: {details}. {finish}. Follow the clay model exactly: same silhouette, pose, proportions, position and size in frame, and the same camera angle. {ground}; keep the cast shadow of Image 1. Keep the background of Image 1: same place, composition, perspective and horizon, in {background style}, crisp and detailed. Light the {kind} with the scene: {light}. No gray clay left, no extra characters or objects, no text.

    {ground} names the contact, for example "Her boots stand on the wet cobblestones exactly where the clay feet touch the ground". Add a line for parts the picture never shows (a shield on the back, a count of bags).

  7. jobs_wait in batches of 32 or fewer. asset_download every result and build a contact sheet of all views. Regenerate only the views that fail; a fresh run of the same prompt usually fixes a one-off.

  8. Transparent set: recommend a background-removal model, read its image field from model_schema_get, run it on each repainted asset id (not on a new studio repaint), download, then python3 studio_shadow.py views/clay_<key>.png cut_<key>.png studio_<key>.png. It prints how much of the clay body the cutout covers and how much lies outside it: a view far off the others, or with corners not clear, lost part of the subject or kept background, so rerun its removal.

Show full SKILL.md (169 more words)Show less

Common mistakes

  • Repainting each angle independently on a plain background: scale drifted 7 to 53 percent between views in testing. Repaint the grounded layout, and cut out that same frame.
  • Compositing the subject over a flat background photo: it floats and the horizon does not move with the camera. The dome floor is what gives true perspective from above and below.
  • Adding a third reference, such as a previous view of the same angle: its mistakes are copied (one run gained an extra bag on every back view). Keep two references unless the extra one is verified clean.
  • A "harmonize" pass over a finished view: it re-crops the frame and breaks the alignment with the clay.
  • Skipping camera zero: view 00 then does not match the picture the user started from.
  • Hardcoding model ids or prices: discover with recommend, price with dry_run=true.
  • Passing more than 32 ids to jobs_wait, or polling job_get.
  • Trusting a view without looking: check contact sheets for extra limbs, wrong sides, and leftover gray clay.

© 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 5 other files (scripts) in skills/scenario-orbit-views of scenario-labs/skills.

  • SKILL.md
  • README.md
  • scripts/compose_layout.py
  • scripts/match_view.py
  • scripts/render_grounded.py
  • scripts/studio_shadow.py

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Orbit Views 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 Orbit Views compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Orbit Views this skillscenario-labs/skills946—~2.3kAutomated safety check: PassMIT
Geometry Nodesarjun988/blender-skills283—~963Automated safety check: PassMIT
Blender MCPTommy-yw/RunbookHermes5461 repos~1kAutomated safety check: PassMIT
Lightingarjun988/blender-skills283—~922Automated safety check: PassMIT
Uv Workflowarjun988/blender-skills283—~1.1kAutomated safety check: PassMIT
Asset Optimizationarjun988/blender-skills283—~934Automated safety check: PassMIT

Similar skills

  • Geometry Nodes

    arjun988/blender-skills

    Blender Geometry Nodes for procedural modeling, scatter systems, vegetation, buildings, pipes, cables, and reusable node groups.

    283 GitHub stars~963 tokensUpdated 3 mo ago
    Game DevelopmentAuto-check passed
  • Blender MCP

    Tommy-yw/RunbookHermes

    Control Blender directly from Hermes via socket connection to the blender-mcp addon.

    546 GitHub starsUsed in 1 repo~1k tokens
    Agent WorkflowsAuto-check passed
  • Lighting

    arjun988/blender-skills

    Cinematic and game lighting in Blender including three-point lighting, HDRI, horror lighting, volumetrics, rim lighting, and mood-driven illumination.

    283 GitHub stars~922 tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Uv Workflow

    arjun988/blender-skills

    Production UV unwrapping for seam placement, UV packing, texel density, UDIM, lightmap UVs, and modular UV layouts.

    283 GitHub stars~1.1k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Asset Optimization

    arjun988/blender-skills

    Validates and optimizes Blender assets for polycount, topology, UV efficiency, material count, naming, collections, and game-ready performance.

    283 GitHub stars~934 tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Retopology

    arjun988/blender-skills

    Production retopology for animation-ready, low-poly, quad-dominant meshes with proper edge loops and efficient polygon flow.

    283 GitHub stars~967 tokensUpdated 3 mo 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 Orbit Views

What does Scenario Orbit Views do?

A skill your agent uses when a single image of a character, creature, prop, vehicle, or building must be seen from new camera angles through the Scenario MCP server: turnarounds, a 360 orbit, views…. Scenario Orbit Views is an agent skill from scenario-labs/skills. Use when a single image of a character, creature, prop, vehicle, or building must be seen from new camera angles through the Scenario MCP server: turnarounds, a 360 orbit, views from behind, above, below, or straight down, consistent multi-angle renders on the same grounded background or on transparency, or novel views that go through a 3D intermediary instead of guessing.

When should I use Scenario Orbit Views?

Scenario Orbit Views fits situations like: A single image of a character; building must be seen from new camera angles through the Scenario MCP server: turnarounds; views from behind; consistent multi-angle renders on the same grounded background.

How do I install Scenario Orbit Views in Claude Code?

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

How do I install Scenario Orbit Views in Codex?

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

Can I use Scenario Orbit Views 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-orbit-views -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-orbit-views, .gemini/skills/scenario-orbit-views, .github/skills/scenario-orbit-views and .opencode/skills/scenario-orbit-views in your project.

What does Scenario Orbit Views need to run?

Going by SKILL.md and its folder, Scenario Orbit Views needs Python for the scripts in its folder and the command-line tools its instructions call (python3, npx and curl). Our summary lists: Python 3; Node.js.

Does Scenario Orbit Views access the network?

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

Is Scenario Orbit Views 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Scenario Orbit Views use?

Scenario Orbit Views 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 Orbit Views use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Scenario Orbit Views?

Skills that share tags, products or a category with Scenario Orbit Views: Geometry Nodes (arjun988/blender-skills, 283 stars), Blender MCP (Tommy-yw/RunbookHermes, 546 stars), Lighting (arjun988/blender-skills, 283 stars) and Uv Workflow (arjun988/blender-skills, 283 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Orbit Views?

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.