App Promo Materials
glifxyz/glif-mcp-server
Plan and make launch, store, ad and campaign graphics with Glif: real app screens turned into store listings and launch posts, or a coordinated set of product photos, ads, a short video and a jingle…
A skill your agent uses when one approved visual, image or video, must ship at many sizes or placements through Scenario: adapting a master to 1:1, 4:5, 9:16, or 16:9, social formats for feeds and…
Install Scenario Formats
$ npx skills add scenario-labs/skills --skill scenario-formats -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install scenario-labs/skills scenario-formats --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scenario-formats .claude/skills/scenario-formats && rm -rf skills-srcUse ~/.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/
Install the "scenario-formats" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-formats into .claude/skills/scenario-formats/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-formats", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/scenario-labs/skills/tree/main/skills/scenario-formatsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add scenario-labs/skills --skill scenario-formats -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install scenario-labs/skills scenario-formats --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/scenario-formats .agents/skills/scenario-formats && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scenario-formats" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-formats into .agents/skills/scenario-formats/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-formats", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add scenario-labs/skills --skill scenario-formats -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install scenario-labs/skills scenario-formats --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/scenario-formats .cursor/skills/scenario-formats && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "scenario-formats" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-formats into .cursor/skills/scenario-formats/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-formats", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/scenario-labs/skills.git --path skills/scenario-formats--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add scenario-labs/skills --skill scenario-formats -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install scenario-labs/skills scenario-formats --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/scenario-formats .gemini/skills/scenario-formats && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "scenario-formats" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-formats into .gemini/skills/scenario-formats/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-formats", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install scenario-labs/skills scenario-formatsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add scenario-labs/skills --skill scenario-formats -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/scenario-formats .github/skills/scenario-formats && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "scenario-formats" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-formats into .github/skills/scenario-formats/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-formats", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add scenario-labs/skills --skill scenario-formats -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install scenario-labs/skills scenario-formats --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/scenario-formats .opencode/skills/scenario-formats && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "scenario-formats" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-formats into .opencode/skills/scenario-formats/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-formats", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
scenario-formats- GitHub stars
- 946
- Token cost
- ~1.7k tokens
- SKILL.md length
- 807 words
- Files
- 2 (incl. references)
- Skills in repo
- 146
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when one approved visual, image or video, must ship at many sizes or placements through Scenario: adapting a master to 1:1, 4:5, 9:16, or 16:9, social formats for feeds and…
- Works in 5 steps: Approve one master first, at the largest… → Derive every format from that master,… → Reframe and expand before grading and… → …
- One approved visual
- SKILL.md covers Overview, The decision ladder, Order of operations and Worked example: key art to…, plus 1 more section
- Calls npx
What it does
Scenario Formats is an agent skill from scenario-labs/skills. Use when one approved visual, image or video, must ship at many sizes or placements through Scenario: adapting a master to 1:1, 4:5, 9:16, or 16:9, social formats for feeds and stories, YouTube thumbnails, storefront capsules and app store graphics, marketplace product images, link previews, display banners, a website hero, or choosing between crop, resize, expand, and generative reframe. Keywords: aspect ratio, resize, reframe, outpaint, expand, derivative, safe zone, thumbnail, banner.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/placement-specs.md`).
It sits in Media & Creative, covering App store release. It works with YouTube. 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 approved visual
- Must ship at many sizes
- Placements through Scenario: adapting a master to 1:1
- Social formats for feeds and stories
Example prompts
- “/scenario-formats”
Requirements
- Node.js
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Approve one master first, at the largest clean size available, on a text-free plate (unattended, the task's named master or the brief's…
- Derive every format from that master, never from another derivative: derivative-of-derivative compounds re-rendering artifacts.
- Reframe and expand before grading and grain: generative canvas work re-renders the image, so finishing passes applied first come back…
- Verify by measurement before finishing: reframe ratio enums are approximate (a 4:5 request came back 29:36 at authoring time), so check…
- Letter last: re-overlay lettering per format with scenario-text-overlay, sized to each final canvas, since type scaled by a resize turns…
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 Formats loads about 1.7k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 127 tokens; SKILL.md has 807 words of instructions outside code blocks.
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). 807 words, ~1,672 tokens.
Download SKILL.mdSave it as
.claude/skills/scenario-formats/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- scenario-formats
- description
- Use when one approved visual, image or video, must ship at many sizes or placements through Scenario: adapting a master to 1:1, 4:5, 9:16, or 16:9, social formats for feeds and stories, YouTube thumbnails, storefront capsules and app store graphics, marketplace product images, link previews, display banners, a website hero, or choosing between crop, resize, expand, and generative reframe. Keywords: aspect ratio, resize, reframe, outpaint, expand, derivative, safe zone, thumbnail, banner.
- license
- MIT
Scenario Formats
Overview
Format adaptation is derivation, not regeneration: re-prompting the concept per placement makes five cousins, not five formats of one approved master. The failure modes are picking the wrong operation (a resize where canvas needed inventing, a crop that beheads the subject) and deriving in the wrong order. The canvas tools' exact contracts live in scenario-image-editing; this skill is the decision ladder and the order of operations around them, with per-placement ratios, pixel targets, and safe zones in references/placement-specs.md. A video master climbs the same ladder: video resize versus generative reframe lives in scenario-video-editing, and far ratios recompose per scenario-video. Connection and the core loop: see the scenario skill. Lettering per format: scenario-text-overlay. 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 decision ladder
Per target format, take the first rung that fits. Each rung is a model_run on a model found with search (target="models", public=true), never a dedicated MCP tool of its own:
| The target needs | Operation |
|---|---|
| Same ratio, other pixels | Resize: exact, scales pixels, invents nothing |
| A tighter ratio, edges expendable | Resize with fit: "cover": exact, center-crops the overflow; only when the subject clears the cut |
| More canvas, composition intact | Expand or uncrop: exact pixels, fills outward |
| Another ratio, recomposed around the subject | Generative reframe; the text-protecting variant when lettering or marks are on the plate |
| A far ratio or a new visual hierarchy | Recompose natively: a fresh run per scenario-image with the master as reference (scenario-consistency), composed for that ratio |
The last rung applies more often than it looks: 16:9 key art seldom survives to 9:16 by any amount of outpainting, which is why the director siblings (scenario-video-ads) design each delivery ratio as its own composition.
Order of operations
- Approve one master first, at the largest clean size available, on a text-free plate (unattended, the task's named master or the brief's own description stands in for the approval).
- Derive every format from that master, never from another derivative: derivative-of-derivative compounds re-rendering artifacts.
- Reframe and expand before grading and grain: generative canvas work re-renders the image, so finishing passes applied first come back partly reinterpreted (
scenario-image-editingholds the pipeline order). A video reframe also precedes any upscale: it renders at its own resolution tier whatever the input carries (1080p at most at authoring time), so an upscale ahead of it is discarded; upscale the reframed clip to delivery size. - Verify by measurement before finishing: reframe ratio enums are approximate (a 4:5 request came back 29:36 at authoring time), so check output dimensions, land exact with a resize, and batch-check that subjects survived with
asset_analyze(scenario-asset-analysis). - Letter last: re-overlay lettering per format with
scenario-text-overlay, sized to each final canvas, since type scaled by a resize turns soft and each placement has its own safe area. Keep critical content and text away from the edges platform UI covers: each placement's target and safe zone is in references/placement-specs.md as an authoring-time value, so confirm contractual specs with the user (unattended, task instructions win over the reference, and the delivery report states which was used).
Show full SKILL.md (272 more words)Show less
Worked example: key art to story, feed, and thumbnail
- Master: 16:9 text-free key art, approved.
- 1:1 feed: generative reframe with a prompt naming what must stay ("the knight centered, both banners visible"), then a resize pass to the exact deliverable pixels.
- 9:16 story: a far ratio, so recompose natively: one run per
scenario-imagewith the master as reference and a 9:16 composition clause; the master holds palette and subject on-look. - Thumbnail: readability rules the crop, so reframe tight on the face or product, land exact with a resize, then
asset_displaythe result and judge it small: thumbnails are seen at a tenth of their size. - Verify dimensions against the deliverable list and batch-check that subjects survived with one
asset_analyzepass, then overlay the title card per format onto each final canvas and file the set in a collection.
Common mistakes
- Re-prompting per format: five generations of one prompt are five different images; derive from the master.
- Stretching into a new ratio with a resize (
fit: "stretch"): it distorts. A ratio change isfit: "cover"when the edges are expendable, else reframe, expand, or recomposition. - Grading and grain before reframing: the order is reshape, then grade, then texture.
- Deriving from the lettered master: generative operations re-render type; keep a text-free plate and re-overlay per format.
- Trusting a ratio enum: measure the output and resize to exact.
- Center-cropping toward 9:16 because it is cheap: it is also how subjects lose their heads; the ladder exists to be climbed.
- Skipping
dry_runon reframes: generative canvas work is the expensive step in the chain, tens of times an effect's price (scenario-image-editing).
© 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 1 other file (references) in skills/scenario-formats of scenario-labs/skills.
- SKILL.md
- references/placement-specs.md
Open the folder on GitHubat commit f6f8ab7
Compare with similar skills
Scenario Formats 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scenario Formats this skillscenario-labs/skills | 946 | — | ~1.7k | Automated safety check: Pass | MIT | |
| App Promo Materialsglifxyz/glif-mcp-server | 213 | — | ~1.7k | Automated safety check: Pass | MIT | |
| App Preview Videoappeeky/aso-skills | 2.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Native Subtitle Quote Imagechengyi-ai/native-subtitle-quote-image | 2.6k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Video Spec Builderfeicaiclub/video-spec-builder | 1k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Video Dataoxylabs/agent-skills | 875 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
App Preview Video
appeeky/aso-skills
When the user wants to plan, script, produce, or optimize App Store Preview videos or Google Play promo videos — the autoplay videos that show in App Store/Play Store search and product pages.
Native Subtitle Quote Image
chengyi-ai/native-subtitle-quote-image
将本地视频或用户有权处理的在线视频，经过来源获取、文字稿定位、选题选句、精确取帧、紧凑裁切、拼图和逐张质检，制作成 3:4 或保留画面原比例的视频字幕长图。支持两种明确分开的输出：保留画面内已烧录字幕的原生字幕模式，以及把已审核的时间点与台词绘制到真实视频帧上的脚本字幕模式。用户要求原生字幕截图、字幕帧拼图、YouTube…
Video Spec Builder
feicaiclub/video-spec-builder
当用户说想做一个视频、宣传片、产品演示、动画短片、抖音/YouTube 内容，或者说要改分镜、调节奏、换镜头、调字幕、加配音、改转场时使用。通过苏格拉底式追问收集视频需求，主动激发渲染层的全部能力（TTS / 字幕 / 3D / shader / 音频反应等），输出标准化的 video-spec.md 用于渲染。
Video Data
oxylabs/agent-skills
YouTube data extraction API and high-bandwidth proxy downloads.
Motion Video in Remotion
ooiyeefei/ccc
Builds marketing and explainer videos in Remotion from rendered scenes, with one real product capture as proof, and cuts them for each platform's formats.
More from scenario-labs/skills
All 146 skills in this repoScenario 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…
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.
Scenario Blender Lighting Rendering
scenario-labs/skills
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…
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…
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…
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…
Related
Works with
Categories
Questions about Scenario Formats
What does Scenario Formats do?
A skill your agent uses when one approved visual, image or video, must ship at many sizes or placements through Scenario: adapting a master to 1:1, 4:5, 9:16, or 16:9, social formats for feeds and…. Scenario Formats is an agent skill from scenario-labs/skills. Use when one approved visual, image or video, must ship at many sizes or placements through Scenario: adapting a master to 1:1, 4:5, 9:16, or 16:9, social formats for feeds and stories, YouTube thumbnails, storefront capsules and app store graphics, marketplace product images, link previews, display banners, a website hero, or choosing between crop, resize, expand, and generative reframe.
When should I use Scenario Formats?
Scenario Formats fits situations like: one approved visual; must ship at many sizes; placements through Scenario: adapting a master to 1:1; social formats for feeds and stories.
How do I install Scenario Formats in Claude Code?
Run `npx skills add scenario-labs/skills --skill scenario-formats -a claude-code`. Or copy the skill folder (skills/scenario-formats in scenario-labs/skills) into .claude/skills/scenario-formats in your project. Claude Code loads it when a task matches its description.
How do I install Scenario Formats in Codex?
Run `npx skills add scenario-labs/skills --skill scenario-formats -a codex`. Or copy the skill folder (skills/scenario-formats in scenario-labs/skills) into .agents/skills/scenario-formats in your project. Codex loads it when a task matches its description.
Can I use Scenario Formats 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-formats -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-formats, .gemini/skills/scenario-formats, .github/skills/scenario-formats and .opencode/skills/scenario-formats in your project.
What does Scenario Formats need to run?
Going by SKILL.md and its folder, Scenario Formats needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Scenario Formats 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 Formats 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 Formats use?
Scenario Formats 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 Formats use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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.8k tokens, read only when the agent opens those files.
What are the alternatives to Scenario Formats?
Skills that share tags, products or a category with Scenario Formats: App Promo Materials (glifxyz/glif-mcp-server, 213 stars), App Preview Video (appeeky/aso-skills, 2.2k stars), Native Subtitle Quote Image (chengyi-ai/native-subtitle-quote-image, 2.6k stars) and Video Spec Builder (feicaiclub/video-spec-builder, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scenario Formats?
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.