Scenario Agent Skills

Agent Skills that teach AI coding agents (Claude Code, Cursor, Codex, Copilot, and 70+ others) how to create production-ready content with Scenario through the Scenario MCP server: images, video, audio, textures, skyboxes, 3D assets, and custom-trained models, for games, entertainment, and any creative vertical.

Skills follow the Agent Skills format.

Install

# Every skill, no picker
npx skills add scenario-labs/skills --skill "*"

# Pick from the installer menu (it opens with nothing preselected)
npx skills add scenario-labs/skills

# A single skill
npx skills add scenario-labs/skills --skill scenario

Some skills direct sibling skills per stage, so installing one of them alone leaves its references unfilled. Install a composed pipeline together:

# Video ads (director skill plus the siblings it delegates to)
npx skills add scenario-labs/skills --skill scenario --skill scenario-video-ads --skill scenario-image --skill scenario-video --skill scenario-seedance --skill scenario-audio --skill scenario-video-assembly --skill scenario-text-overlay --skill scenario-consistency --skill scenario-asset-analysis

# Seedance music video
npx skills add scenario-labs/skills --skill scenario --skill scenario-seedance-music-video --skill scenario-seedance --skill scenario-consistency

# Seedance storyboarded choreography
npx skills add scenario-labs/skills --skill scenario --skill scenario-seedance-storyboard --skill scenario-seedance --skill scenario-consistency --skill scenario-video-editing --skill scenario-video-assembly

Skills need the Scenario MCP server connected:

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

Or add https://mcp.scenario.com/mcp to any MCP client and sign in with a Scenario account (OAuth), or use an API key. Full setup lives in the scenario skill.

Staying up to date

Installs always fetch the latest copy of each skill from main; there is no version pinning. Releases are how changes become visible: every feature, fix, and documentation change merged to main lands in the next release, staged by release-please as an open release PR. Merging that PR tags a version, updates CHANGELOG.md in this repository, publishes a GitHub release, and posts the notes to the Scenario changelog.

• To learn that a skill changed, watch this repository's releases (Watch, then Custom, then Releases on GitHub) or check any of the changelog pages above. An entry scoped to a single skill carries that skill's name; changes spanning several skills appear under broader scopes such as skills.
• To pull the changes, run npx skills update where you installed, or re-run your original npx skills add command.

Skills

Getting started

Connect the Scenario MCP server and learn the core generation loop every other skill builds on.

Finding a direction

Turn a blank brief into references, options someone can choose between, and a moodboard the next batch runs from.

Images

Generate and edit images: model choice, sizing, references, masked edits, post-processing tools, and letter-perfect text overlay cards.

Game art and environments

Sprites, icons, tilesets, textures, skyboxes, and 3D assets ready for game engines.

Video and audio

Video generation and editing, music, sound effects, voice, and speech.

Consistency and custom models

Hold one character, product, or style across a whole set, and train custom models on your own art.

Reviewing and organizing output

Read finished assets back: caption them, extract a style or a control map, check a batch against a brief or the Quality Gate, compare candidate models on one brief, and file the keepers.

Formats and placements

Ship one approved master, image or video, to every placement: ratios, safe zones, and platform specs from social feeds to shops, storefronts, and print.

Workflows and apps

Discover, run, build, and publish Scenario workflows (apps), and migrate graphs from Weavy, ComfyUI, or other node editors.

Troubleshooting

Get past a blocked generation, and turn a stuck session into a reproducible public issue.

Team administration

Govern a team from the agent: which models it can run, who is on it and in which projects, per-member spend caps, API key roles, and who spent what.

Image model families

The top image families in depth: generation and editing modes, reference rules, and the caps that differ per member.

Video model families

The top video families in depth: conditioning modes, native audio, editing and extension, and per-member caps and costs.

Audio model families

The top audio families in depth: music, covers and stems, sound effects, speech, dubbing, and video scoring.

3D model families

The top 3D families in depth: mesh generation, retexture and rigging toolchains, portraits, and explorable worlds and splats.

Example prompts

Once the skills are installed and the MCP server is connected, ask your agent things like:

• "Generate four style-matched potion icons with transparent backgrounds for my RPG inventory"
• "Make a seamless brick texture, then upscale it to 2048 without breaking the tiling"
• "Turn this concept sketch into a 3D prop and let me preview it before I export the GLB"

What is an Agent Skill?

A skill is a SKILL.md file with procedural knowledge an agent loads on demand, defined by the open Agent Skills specification. The skills CLI installs these files into 70+ agents, and the ecosystem directory lives at skills.sh.

Contributing

See CONTRIBUTING.md for the contribution workflow, and AGENTS.md for the authoring contract, the public-content policy, validation, and the application-testing bar. One-time setup after cloning: pnpm install (installs commitlint, cspell, prettier, and the husky git hooks). pnpm run validate runs the same content checks CI runs; commit messages and the PR title are linted separately with commitlint. PRs welcome; PR titles follow Conventional Commits since they become the squash commit header on main.

Every script shipped with a skill has a test suite in tests/<name>/; pnpm test runs them all (CI does too). Suites need Python 3.11+ with any tests/<name>/requirements.txt dependencies installed, plus ffmpeg on PATH where a suite uses it. Python suites use stdlib unittest, TypeScript suites use vitest.

License

MIT