Give this skill to your agent

Copy the prompt and paste it into Claude Code, Codex or any agent that can read a web page. It installs the skill and tells you what it does.

Install this skill for me.

Read https://cwyz.com/skills/scenario-agent-skills-en
The raw SKILL.md is at https://cwyz.com/api/skills/scenario-agent-skills-en/raw

Save it as scenario-agent-skills/SKILL.md in my skills folder (Claude Code: ~/.claude/skills/ for every project, or .claude/skills/ for this project only).

Then tell me in two sentences what it does and when it applies. Do not run anything it describes until I say so.

Or unzip the download into ~/.claude/skills/ (every project) or .claude/skills/ in your project. A skill tells an agent what to do. Read it before you install it, especially one you did not write.

Scenario Skill Pack Generates Images, Video and 3D and Drives Game Engines

Use when a user wants an agent to generate images, video, audio, 3D assets and game art, or to model, rig, build levels and create effects in Blender, Maya, ZBrush, Unreal, Unity or Godot. Built on the open-source scenario-labs/skills (MIT): run dry_run to estimate cost before generating, and confirm before spending; expert tools only need the matching software installed locally.

Use caseHave an agent generate images, video, audio and 3D assets, estimate cost with a dry run before generating, and drive software such as Blender, Maya, ZBrush, Unreal and Unity.

Machine translation. Read the original

Scenario Creative and 3D Software Skill Pack

Have an agent make images, video, audio and 3D assets, and drive software such as Blender, Maya, ZBrush, Unreal Engine and Unity to do the work. It is built on the open-source scenario-labs/skills (MIT license, published by Scenario, follows the Agent Skills format).

This skill pack has two parts, used differently:

  • Generation skills: generate images, video, audio, textures, skyboxes, 3D models and game assets through Scenario's MCP service. Requires a Scenario account.
  • Expert tools: teach the agent to operate software installed on your machine the way an expert would (Blender, Maya, ZBrush, Unreal, Unity, plus Godot and Roblox Studio). Requires only the software itself, not a Scenario account.

When to Use

Use when a user wants an agent to generate images, video, audio, 3D models, sprites, textures or game assets, mentions Scenario, or needs modeling, rigging, animation, levels, effects, packaging or similar work in Blender, Maya, ZBrush, Unreal, Unity or Godot.

Hard Rules

  1. Estimate before generating. Scenario generations consume credits from the account. Before each generation, run dry_run (quotes the price without executing) to see what this one will cost, unless the user explicitly says cost does not matter. When several models can do the job, present the prices and differences to the user and let them choose.
  2. Confirm before spending. For expensive tasks such as batch generation, high-quality tiers or long videos, tell the user the expected cost before proceeding.
  3. Do not charge twice. Before retrying, check the task list to confirm whether the previous attempt actually succeeded. Do not rerun just because no response was received.
  4. Keys stay out of the conversation. Connect to Scenario via OAuth login first; if using an API key, have the user configure it themselves. Do not ask them to paste it to you, and do not print it.
  5. Explain third-party code before installing it. npx skills add installs third-party skills onto the user's computer. Tell the user what will be installed before doing so; for a reviewable state, pin to a commit of a release version as described in the repository instructions.
  6. Do not install paid software for the user. Blender, Maya, ZBrush, Unreal and Unity must already be installed by the user; say which are missing.
  7. Do not overstate expert tools. The repository states how far each one has been verified (for example, the ZBrush bridge is verified, but full testing of every skill is not finished); report this accurately.

Installation

First check what is already present:

ls ~/.claude/skills 2>/dev/null | grep -i scenario || echo "not installed"

Generation skills (excluding expert tools):

npx skills add scenario-labs/skills --skill scenario

Installing only the core scenario skill is enough to get started. For others (images, video, 3D, textures, sprite animation, etc.), run npx skills add scenario-labs/skills to open the menu and select them yourself, or check INSTALL.md in the repository, which groups them by role and goal with one command per group.

Then connect Scenario's MCP service:

claude mcp add --transport http scenario https://mcp.scenario.com/mcp

The first use will prompt a Scenario account login (OAuth).

Expert tools: each software's skills are installed as a set, because the expert skills share scripts from the lead skill. Go to the matching software folder in the repository and copy the install command from its README:

Software Repository location
Blender skills/dcc/blender
Maya skills/dcc/maya
ZBrush skills/dcc/zbrush
Unreal Engine skills/game-engines/unreal
Unity skills/game-engines/unity
Godot, Roblox Studio skills/game-engines/godot, skills/game-engines/roblox

Restart Claude Code after installing.

Choosing by Need

User wants How to do it
Generate a batch of icons, textures, concept art Generation skills, quote with dry_run first
Turn an image into a 3D model, export after previewing The 3D part of the generation skills
Compare several models to see which fits the need Model comparison skill: run several candidates on the same request and compare price and quality
Model, rig, animate in Blender, Maya, ZBrush Expert tool for that software
Build levels, create effects, optimize performance in Unreal, Unity, Godot Expert tool for that engine

Example Requests

Generate 4 style-consistent potion icons for my RPG inventory, with transparent backgrounds. Quote the price first, and I'll confirm before you generate.
Turn this concept sketch into a 3D prop, and let me preview it before exporting as GLB.
Using the Blender expert tool, retopologize this model and create UVs, then export it as a file that can go into Unity.

Output Format

  1. First state which skills were used and whether the connection is working.
  2. Where generation is involved, list the quote and actual spend.
  3. Give the output paths (images, models, project files), and note which are previews and which have been exported.
  4. List items the user must confirm or supply: missing software, accounts not logged in, unconfirmed spending.
Done with this one? Mark it to track your path.Sign in
Save it for laterSign in
Questions about this piece?Ask AI about this

Comments (0)

No comments yet. Start the conversation.

Sign in to join the discussion.Sign in