Agent skill

Scenario Video Editing

by scenario-labs in scenario-labs/skills

A skill your agent uses when editing footage that already exists on Scenario through MCP with a tool model instead of a new generation: 3D LUT grading, color correction, film grain, vignette, blur…

MITAuto-check passedMedia & Creative

Install Scenario Video Editing

skills CLI
$ npx skills add scenario-labs/skills --skill scenario-video-editing -a claude-code

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

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

At a glance

A skill your agent uses when editing footage that already exists on Scenario through MCP with a tool model instead of a new generation: 3D LUT grading, color correction, film grain, vignette, blur…

  • Works in 6 steps: asset_get the master and read… → Trim: model_scenario-video-cut with… → Reshape: model_scenario-resize-video,… → …
  • Editing footage that already exists on Scenario through MCP with a tool model instead of a new generation: 3D LUT grading
  • SKILL.md covers Overview, The twin rule, Quick reference and Cost follows the clip, so trim…, plus 4 more sections
  • Calls npx

What it does

Scenario Video Editing is an agent skill from scenario-labs/skills. Use when editing footage that already exists on Scenario through MCP with a tool model instead of a new generation: 3D LUT grading, color correction, film grain, vignette, blur, sharpen, glow, tint, desaturate, posterize, solarize, cubism, crystallize, oilify, chromatic aberration or dodge and burn on a clip; trimming to a time range, splitting at cut points, reversing, resizing, re-encoding, frame extraction, image sequences, background removal, segmentation masks, subjects as layers.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Media & Creative, covering Video production and Image editing. It works with Model Context Protocol. 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

  • Editing footage that already exists on Scenario through MCP with a tool model instead of a new generation: 3D LUT grading
  • Color correction
  • Chromatic aberration
  • Dodge and burn on a clip

Example prompts

  • “/scenario-video-editing”

Requirements

  • Node.js

Workflow steps

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

  1. asset_get the master and read properties.duration before choosing times.
  2. Trim: model_scenario-video-cut with startTime and endTime in seconds. Going first is what makes every later step cheaper.
  3. Reshape: model_scenario-resize-video, video as a one-item array, width and height at the delivery size, videoOutputFormat: "mp4". fit…
  4. Grade: model_schema_get, then the LUT twin with lutIntensity near 0.6.
  5. Texture: model_schema_get, then the Grain twin with grainProfile (a 22-value enum, default kodak_portra_400 at authoring time) on that…
  6. asset_display the result's firstFrame to confirm the look, then asset_download with no format.

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 Video Editing loads about 2.3k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 1,244 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
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); 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). 1,244 words, ~2,318 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-video-editing/SKILL.md (or your agent's skills folder).
name
scenario-video-editing
description
Use when editing footage that already exists on Scenario through MCP with a tool model instead of a new generation: 3D LUT grading, color correction, film grain, vignette, blur, sharpen, glow, tint, desaturate, posterize, solarize, cubism, crystallize, oilify, chromatic aberration or dodge and burn on a clip; trimming to a time range, splitting at cut points, reversing, resizing, re-encoding, frame extraction, image sequences, background removal, segmentation masks, subjects as layers.
license
MIT

Scenario Video Editing

Overview

Every image post-processing effect has a video twin, and each is a model_run on a tool model: one clip in, a few numbers, one clip out. Generating or restyling footage, lipsync, dubbing and upscaling are scenario-video; concatenating, compositing and captioning a cut are scenario-video-assembly; the still-image side is scenario-image-editing. Connection and the core loop: scenario. 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 twin rule

A video effect's id is the image id with -video appended, its file field is video rather than image, and the knobs are identical: model_scenario-postprocessing-lut-video takes the same lutStyle enum and lutIntensity as model_scenario-postprocessing-lut. All eighteen have twins, from blur and color correction through oilify, posterize and vignette.

One twin differs: Dissolve (Video) blends the clip with a still dissolveImage, not a second clip; crossfading two clips is a concat transition.

Quick reference

NeedModel or query
Grade or stylizefilters={"tags": ["Post Processing"]}, plus the effect name as query
Trim to a rangemodel_scenario-video-cut (startTime, endTime)
Cut into segmentsmodel_scenario-video-split (cutPoints; N points give N+1 clips)
Rescale or re-encodemodel_scenario-resize-video
Play a clip backwardsmodel_reverse-video
Frames out, frames inmodel_scenario-video-to-image-seq, model_scenario-image-seq-to-video
Subjects as layersmodel_scenario-video-layers-extractor
Masks, cutoutsrecommend with the need in the user's own words
Pull the audio trackmodel_scenario-audio-extract

Extracted frames carry no index and share one createdAt, so their order exists only in the job row's assetIds, and that list has come back out of time order (a confirmed defect at authoring time). The extractor takes a scalar video; every frame is extractAllFrames: true, and frameInterval (default 24 at authoring time, about one frame a second on a 24 fps clip) applies only when that flag is off. Check that the row holds exactly the clip's nbFrames ids (asset_get reports it beside frameRate; a short row is a dropped frame, which no reordering fixes), then, before reassembling with model_scenario-image-seq-to-video or handing frames on, lay the returned ids into model_scenario-grid-maker in that order (a fixed first-party id: Scenario's single grid tool; its images field takes an array of 1 to 100 ids and ignores a bare id while the run still succeeds, so past 100 frames sheet in batches or raise frameInterval; set columns, default 3 and up to 20, so a batch reads as a near-square sheet) and read the sheet against the clip's free firstFrame and lastFrame and its motion; a frame that breaks continuity is out of place, and the corrected order travels as your own id list from then on. Never rebuild order from listings or timestamps, and a preview that runs backwards on a clean sheet is the assembler's pingpong flag, not the order.

A cutout with transparency never ships as mp4: at authoring time the removal models carried alpha only as WebM or ProRes 4444 MOV, so read the output-format enum off model_schema_get and agree the container with the user before pricing the run.

Effect lookups go through search, target="models", public=true. The model_scenario- ids are constants: each is Scenario's single deterministic tool for its operation, so discovery would only re-derive it. model_reverse-video sits outside that set and is an authoring-time hit: re-discover it by name (search query="video reverse").

Cost follows the clip, so trim first

On the video twins the video input carries cost_impact: true, which the image versions do not: price tracks the footage rather than the settings. Trim to the frames that ship, then grade; dry_run=true prices a payload before it runs. Video tools also outlast model_run's wait window, so launch with wait=false and follow with jobs_wait, re-calling it with the returned pending_job_ids. A client-side timeout on jobs_wait is as harmless as the server's own: re-call it with the same ids rather than treating the job as lost.

Checking costs nothing: asset_get returns firstFrame and lastFrame as their own asset ids, so asset_display one to confirm a grade before chaining another billable run onto it.

Field names drift between neighbors

  • Video Cut and the effect twins take a scalar video. Resize Video takes video as an array: true field capped at one item, where a bare id is dropped silently; its size is width and height in pixels, both optional, and one alone keeps the aspect ratio.
  • The output format field is outputFormat on cut and split, videoOutputFormat on resize.
  • preserveAudio defaults to true on cut, split and resize; the effects expose no audio field and pass the track through.
  • Enum values are copied, not retyped: one lutStyle string contains a space.
  • asset_download takes no format for a video: it converts image formats only. A GIF from the sequence tool is an image asset and takes format: "gif"; the png default flattens it to one frame.
Show full SKILL.md (443 more words)Show less

Resizing is not reframing

No tool model repaints a video's canvas. Resize Video takes fit: contain (default) fits the clip inside the target, stretch forces the size and distorts, cover fills the target and center-crops the rest. cover is the cheap way to an exact ratio when losing the edges is acceptable, but none of them gives a 16:9 clip a vertical frame with the whole picture kept, so that brief needs a decision before any spend, between two routes an order of magnitude apart in price.

  • Generative reframe (query="reframe", Luma Ray 3.2 Reframe and Wan 2.2 Reframe, scenario-video territory) outpaints past the frame and keeps the whole picture, at by far the highest price in such a job. Resolution ceilings bite: a schema can allow a vertical ratio and its top resolution tier separately yet reject the pair at run time.
  • Compositor (Video Studio, cropping or pillarboxing onto a vertical canvas) is cheap but throws away width or adds bars, and its layer geometry is scenario-video-assembly's contract rather than a one-line setting.

dry_run prices a payload without validating it, so either route can bill for a run that fails outright or returns a mis-composed frame at exactly the right dimensions.

Worked example: a graded cutdown

Launch every model_run below with wait=false and retire it with jobs_wait before the next step reads its asset.

  1. asset_get the master and read properties.duration before choosing times.
  2. Trim: model_scenario-video-cut with startTime and endTime in seconds. Going first is what makes every later step cheaper.
  3. Reshape: model_scenario-resize-video, video as a one-item array, width and height at the delivery size, videoOutputFormat: "mp4". fit settles the shape at this step rather than later: cover lands an exact ratio once the edges are spendable, and a shape that has to keep the whole picture is the reframe decision above.
  4. Grade: model_schema_get, then the LUT twin with lutIntensity near 0.6.
  5. Texture: model_schema_get, then the Grain twin with grainProfile (a 22-value enum, default kodak_portra_400 at authoring time) on that output, last, so its grain is sized for the delivered frame rather than resampled by a later resize.
  6. asset_display the result's firstFrame to confirm the look, then asset_download with no format.

Common mistakes

  • Grading each source clip and then concatenating: grade the finished master once, or the shots drift apart.
  • Reaching for local ffmpeg, or for an MCP tool named video_edit: the surface is model_run on tool models.
  • Polling job_get in a loop instead of jobs_wait, whose timeout is not an error.
  • Trusting a Grain profile to add grain: the 22 profiles are looks, not intensities, and some soften the picture instead. Compare a frame against the input.

© 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

Just SKILL.md in skills/scenario-video-editing of scenario-labs/skills.

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Video Editing 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 Video Editing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Video Editing this skillscenario-labs/skills946—~2.3kAutomated safety check: PassMIT
Audio And Videoglifxyz/glif-mcp-server213—~1.6kAutomated safety check: PassMIT
Web Visualsglifxyz/glif-mcp-server213—~1.5kAutomated safety check: PassMIT
Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills8.5k6 repos~3.2kAutomated safety check: NotesApache-2.0
Taisly Social Media Postingtaisly/agent2171 repos~1.5kAutomated safety check: PassMIT
CapCut Video Directorsun-guannan/VectCutAPI2.3k—~1.7kAutomated safety check: PassApache-2.0

Similar skills

  • Audio And Video

    glifxyz/glif-mcp-server

    Make or edit audio and video with Glif, from a text brief or from a reference image, video or audio file.

    213 GitHub stars~1.6k tokensUpdated 2 days ago
    Media & CreativeAuto-check passed
  • Web Visuals

    glifxyz/glif-mcp-server

    Make images, textures, illustrations and background video for a website or app you are building, with Glif, and wire them into the code.

    213 GitHub stars~1.5k tokensUpdated 2 days ago
    Media & CreativeAuto-check passed
  • Stitch to Remotion Walkthrough Videos

    google-labs-code/stitch-skills

    Official

    Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.

    8.5k GitHub starsUsed in 6 repos~3.2k tokens
    Media & CreativeAuto-check: notes
  • Free AI-first short-form video publishing to TikTok, Instagram Reels, YouTube Shorts, X, and Facebook from AI agents through Taisly.

    217 GitHub starsUsed in 1 repo~1.5k tokens
    Media & CreativeAuto-check passed
  • CapCut Video Director

    sun-guannan/VectCutAPI

    Guides an agent in building and polishing CapCut Desktop video projects through the CapCut MCP server and direct timeline file edits, including vertical canvas, subtitles and audio.

    2.3k GitHub stars~1.7k tokensUpdated 8 days ago
    Media & CreativeAuto-check passed
  • Media Processing

    ynulihao/AgentSkillOS

    Process multimedia files with FFmpeg (video/audio encoding, conversion, streaming, filtering, hardware acceleration), ImageMagick (image manipulation, format conversion, batch processing, effects…

    618 GitHub stars~817 tokensUpdated 7 mo ago
    Media & CreativeAuto-check: notes

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 Video Editing

What does Scenario Video Editing do?

A skill your agent uses when editing footage that already exists on Scenario through MCP with a tool model instead of a new generation: 3D LUT grading, color correction, film grain, vignette, blur…. Scenario Video Editing is an agent skill from scenario-labs/skills. Use when editing footage that already exists on Scenario through MCP with a tool model instead of a new generation: 3D LUT grading, color correction, film grain, vignette, blur, sharpen, glow, tint, desaturate, posterize, solarize, cubism, crystallize, oilify, chromatic aberration or dodge and burn on a clip; trimming to a time range, splitting at cut points, reversing, resizing, re-encoding, frame extraction, image sequences, background removal, segmentation masks, subjects as layers.

When should I use Scenario Video Editing?

Scenario Video Editing fits situations like: editing footage that already exists on Scenario through MCP with a tool model instead of a new generation: 3D LUT grading; color correction; chromatic aberration; dodge and burn on a clip.

How do I install Scenario Video Editing in Claude Code?

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

How do I install Scenario Video Editing in Codex?

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

Can I use Scenario Video Editing 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-video-editing -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-video-editing, .gemini/skills/scenario-video-editing, .github/skills/scenario-video-editing and .opencode/skills/scenario-video-editing in your project.

What does Scenario Video Editing need to run?

Going by SKILL.md and its folder, Scenario Video Editing needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Scenario Video Editing 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 Video Editing 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 Video Editing use?

Scenario Video Editing 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 Video Editing use?

About 2.3k tokens (SKILL.md is roughly 9.3k 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 Video Editing?

Skills that share tags, products or a category with Scenario Video Editing: Audio And Video (glifxyz/glif-mcp-server, 213 stars), Web Visuals (glifxyz/glif-mcp-server, 213 stars), Stitch to Remotion Walkthrough Videos (google-labs-code/stitch-skills, 8.5k stars) and Taisly Social Media Posting (taisly/agent, 217 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Video Editing?

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.