Agent skill

Scenario Unity Pipeline Automation

by scenario-labs in scenario-labs/skills

A skill your agent uses when automating a Unity 6.3 content pipeline or build: importing an art drop (FBX, PNG) with AssetPostprocessor rules and naming conventions, generating prefabs or editing…

MITAuto-check passedGame Development

Install Scenario Unity Pipeline Automation

skills CLI
$ npx skills add scenario-labs/skills --skill scenario-unity-pipeline-automation -a claude-code

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

GitHub CLI
$ gh skill install scenario-labs/skills scenario-unity-pipeline-automation --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/game-engines/unity/scenario-unity-pipeline-automation .claude/skills/scenario-unity-pipeline-automation && 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-unity-pipeline-automation
GitHub stars
946
Token cost
~5k tokens
SKILL.md length
1,995 words
Files
27 (incl. scripts, references)
Skills in repo
146
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when automating a Unity 6.3 content pipeline or build: importing an art drop (FBX, PNG) with AssetPostprocessor rules and naming conventions, generating prefabs or editing…

  • Works in 8 steps: Import rules are code that runs at… → An edit counts only if it goes through… → One AssetDatabase batch per stage,… → …
  • Automating a Unity 6.3 content pipeline
  • SKILL.md covers Stance (the expert delta), Establish first, Workflow and Numbers, plus 5 more sections
  • Runs C# scripts from its folder; calls git and npx

What it does

Scenario Unity Pipeline Automation is an agent skill from scenario-labs/skills. Use when automating a Unity 6.3 content pipeline or build: importing an art drop (FBX, PNG) with AssetPostprocessor rules and naming conventions, generating prefabs or editing scenes from script with correct Undo and SetDirty, Addressables groups, labels and content builds, content-validation tests, batch-mode, command-line or CI builds (Build Profiles, GameCI, GitHub Actions, Accelerator), editor tools; or when textures import wrong or reimport every run, a scripted edit vanishes, bundles duplicate assets, a…

Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 32 other files, including scripts and reference files (for example `references/critique.md`, `references/expert-notes.md` and `references/gui-paths.md`).

It sits in Game Development, covering Game development and CI/CD. It works with GitHub Actions. 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

  • Automating a Unity 6.3 content pipeline
  • Build: importing an art drop (FBX
  • PNG) with AssetPostprocessor rules and naming conventions
  • Generating prefabs

Example prompts

  • “/scenario-unity-pipeline-automation”

Requirements

  • Node.js

Workflow steps

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

  1. Import rules are code that runs at import, and deterministic, and you prove it. Settings in OnPreprocess*, GetVersion() bumped on every…
  2. An edit counts only if it goes through serialization, on the exact object. Record Undo on the component that changes, before the change…
  3. One AssetDatabase batch per stage, measured. StartAssetEditing / StopAssetEditing in try/finally (Abud Chavez [00:30:21]), and…
  4. Pack Addressables by loading condition, not by folder, in a stable order. Assets needed under exactly the same conditions share a group…
  5. Released is not unloaded, and references are loads. Memory returns when the bundle's refcount reaches zero (Addressables 2.9 manual); a…
  6. Fix the platform at launch, the same on every stage, and ship the content you built. Target switches inside a batch job do nothing…
  7. Tests are the gate. Content rules as parametric Edit Mode tests, one case per asset (Warnecke and Fine, wTiF2D0_vKA [00:24:28]), run…
  8. Release builds come from a clean tree, without debug defines, with provenance kept (docs digest checklist; Hopper, profile defines)…

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 9 files in scripts/ (C#, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • npx

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

  • Network

    No URLs in SKILL.md. Its commands use git and 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 Unity Pipeline Automation loads about 5k tokens when it runs, and up to ~36k if it reads all its reference files. Until then it costs about 153 tokens; SKILL.md has 1,995 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~153
When it runs · the whole SKILL.md, loaded when a task matches
~5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~36k

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,995 words, ~4,982 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-unity-pipeline-automation/SKILL.md (or your agent's skills folder). This skill also uses 26 other files; get the full folder from GitHub.
name
scenario-unity-pipeline-automation
description
Use when automating a Unity 6.3 content pipeline or build: importing an art drop (FBX, PNG) with AssetPostprocessor rules and naming conventions, generating prefabs or editing scenes from script with correct Undo and SetDirty, Addressables groups, labels and content builds, content-validation tests, batch-mode, command-line or CI builds (Build Profiles, GameCI, GitHub Actions, Accelerator), editor tools; or when textures import wrong or reimport every run, a scripted edit vanishes, bundles duplicate assets, a batch build ignores its defines, or CI cannot activate Unity.
license
MIT

Unity pipeline automation (tools and build engineer)

Expert level here means a pipeline that gives the same result on every machine and every run: rules applied at import time, edits made through serialization, content packed by when it loads, tests that gate the build, and a build that CI runs from a clean checkout. The stance: nothing is done by hand twice, nothing is trusted without a count, a test or a frame, and a second run changes nothing. 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.

REQUIRED BACKGROUND: scenario-unity-expert (channels, job protocol, review loop, 6.3 traps). Import its toolkit; this skill adds scripts/ut_pipeline.py and scripts/AgentKit/Pipeline/.

Status (2026-09-24, after the blind-grade refactor): every procedure ran in Unity 6000.3.21f1 on this Mac against a 200-FBX Blender drop: tests/code/unity-pipeline-automation/ (results in archive/tests/unity-pipeline-automation/live_results.jsonl).

Stance (the expert delta)

  1. Import rules are code that runs at import, and deterministic, and you prove it. Settings in OnPreprocess*, GetVersion() bumped on every code change, config declared before it is read (context.DependsOnSourceAsset), no clocks, no dictionary order, no asset writes in callbacks (6.3 Manual; Javier Abud Chavez, S2P9n5U9xVw [00:04:35], [00:19:29]). Proof: -consistencyCheck before trusting a shared cache or CI (Manual). Observed: 12,184 assets checked in 23.5 s; a random-pixel probe texture flagged, 0 of the 593 governed files. A bump or a new postprocessor reimports every asset of that importer type, packages included (1,513 textures).
  2. An edit counts only if it goes through serialization, on the exact object. Record Undo on the component that changes, before the change (Freya Holmér, pZ45O2hg_30 [03:01:01]). Observed: Undo.RecordObject(go) then a move is not undone; RecordObject(go.transform) is. A direct write on a prefab instance reverts at the next prefab update; a ScriptableObject is not saved without SetDirty.
  3. One AssetDatabase batch per stage, measured. StartAssetEditing / StopAssetEditing in try/finally (Abud Chavez [00:30:21]), and SaveAndReimport / ImportAsset inside it too. Count with the AssetDatabase counters, not the log (Abud Chavez [00:26:44]). Observed: two remap passes over 195 FBX, 19.0 s one by one vs 5.1 s batched.
  4. Pack Addressables by loading condition, not by folder, in a stable order. Assets needed under exactly the same conditions share a group; dependencies used by several groups are placed explicitly (Olle Axelsson, Valheim, Fzu2Das_1FU [00:23:08]). Unassigned shared dependencies are copied into every bundle [00:18:44]; observed, that includes URP's Lit.shader. Assign in ordinal order (6.3 Manual, Addressables determinism): 2.9.1 sorts groups and entries by GUID when it saves, but the label table keeps insertion order.
  5. Released is not unloaded, and references are loads. Memory returns when the bundle's refcount reaches zero (Addressables 2.9 manual); a build scene that references Addressable content loads it with the scene and again from the bundle (Code Monkey, C6i_JiRoIfk [00:03:32]; Axelsson [00:24:49]). Gate it; measure unloads in the player.
  6. Fix the platform at launch, the same on every stage, and ship the content you built. Target switches inside a batch job do nothing (Manual; Thom Hopper, BlVsi2cSJ88 [00:27:18]); build target is an import dependency (Abud Chavez [00:15:49]). Observed: one stage on Android reimported 1,717 assets in 52 s; switching back reused cached artifacts (60 imports). Addressables' default settings rebuild all content inside every player build.
  7. Tests are the gate. Content rules as parametric Edit Mode tests, one case per asset (Warnecke and Fine, wTiF2D0_vKA [00:24:28]), run synchronously in a pre-build callback that logs the pass [00:31:43]. Any logged error fails a test unless LogAssert.Expected (Manual); observed, that includes an import error logged by a reimport inside the test. Never -quit with -runTests.
  8. Release builds come from a clean tree, without debug defines, with provenance kept (docs digest checklist; Hopper, profile defines). Narrow named tools over generic execution (git-amend, VPjo-M6mPkE [00:03:54]; Unity, DgNrgZeJOxQ [00:07:41]).

Establish first

  • Drop contract: DCC and export settings, folder per category, suffixes, units. Default: Blender "FBX All" + "Apply Transform", _BaseColor/_Normal, a manifest.csv for extra labels.
  • Loading conditions: loaded as a set (level, biome) or one by one? Default: labels, key_by="label"; streaming uses key_by="root".
  • Targets and budgets: platforms (one -buildTarget per pipeline run), texture cap per platform, vertex budget, bundle budget per label. Defaults: 1024 px desktop, 512 mobile, 5,000 vertices.
  • Content updates: remote content after release? Archive addressables_content_state.bin per platform per release.
  • Channel and CI: is the user's editor open on the project (ut_live.channel(P))? Git repo? Accelerator? License: Personal (Hub sign-in only) or paid seat.

Workflow

  1. Preflight. ut_env.preflight(P); ut_pipeline.install(P). Editor open: the same jobs through ut_live.call or the [CliCommand] tools. Pipeline code a team's tests must call: its own Editor asmdef plus a test asmdef (install_asmdef_template). GATE: Echo ok, zero compile errors (one aborts every batch job).
  2. Scan the drop offline. up.scan_drop(drop), same rules JSON. GATE: every reject has a reason; duplicates reject every copy.
  3. Import. up.import_drop(P, drop, target=T): changed files into <root>/<Category>/<Name>/, one batch, audit. GATE: accepted = found - rejected; audit errors explained; after a postprocessor change, up.consistency_check(P, target=T) flags nothing under Assets/.
  4. Materials and prefabs. up.build_prefabs(P, target=T): URP Lit per prop, keywords by ShaderGUI.ValidateMaterial, FBX remaps with SaveAndReimport inside the batch, Prefab Variants built in a preview scene, saved only when a value changed. GATE: prefabs = accepted - size errors; a rerun rewrites 0 files (git status clean).
  5. Look at it. EditorEditJobs.BuildLineup then AgentCapture.CaptureViews with graphics=True, ut_review.review_capture, open the sheet. GATE: no magenta, black or blank flags; props upright, grounded, in scale.
  6. Addressables groups. up.assign_addressables(P, "condition", target=T). GATE: implicit_duplicates == 0; up.hard_references(P) ok.
  7. Content build. up.build_content(P, T): builder index >= 0, ClearCachedData + BuildCache.PurgeCache(false), DoNotBuildWithPlayer, layout read back, state archived. GATE: duplicated assets 0, bytes per label within budget.
  8. Tests. ut_run.run_tests(P, "EditMode", categories="PipelinePreBuild", extra_args=["-buildTarget", up.cli_target(T)]). GATE: failed 0, total equals the expected asset count.
  9. Player build. Profile copied from a committed template (PipelineBuild.CreateBuildProfile with template), ut_run.build(P, T, profile=...), or raw -activeBuildProfile ... -executeMethod AgentKit.Pipeline.PipelineBuild.BuildFromCommandLine. Release: -agentRelease (gate refuses debug defines), clean tree, up.release_ready(repo, app). GATE: AGENT_GATE ok with hard_references 0, BuildReport Succeeded.
  10. Smoke the player. up.player_smoke(app, label). GATE: loaded assets equal the manifest count; bundles unload after release.
  11. CI. up.write_ci(repo): ci/pipeline.sh (one process per stage, the same -buildTarget on each; ACCELERATOR=, CONSISTENCY=1, RELEASE=1) and GitHub Actions files. GATE: passes from a checkout without Library/; license returned if: always(); with Accelerator, the log's cache server= count above 0.
Show full SKILL.md (941 more words)Show less

Numbers

ValueRelative toSource
5.6 to 6.7 s593 files copied and imported in one batchobserved
19.0 s vs 5.1 stwo remap passes over 195 FBX (SaveAndReimport), one by one vs in one batchobserved
11 to 12 s197 materials, 197 FBX remaps, 196 Prefab Variants, in-editor timeobserved
1,717 imports, 52 s / 60 importsfirst launch on another platform / switching back (cached artifacts)observed
1,513 textures, 17 sreimported by one GetVersion() bump of a do-nothing texture postprocessorobserved
12,184 checked, 23.5 s-consistencyCheck of this project (7,390 skipped; 2 URP shaders flagged: baseline packages)observed
0 fileschanged by a second full run (import, prefabs, groups)observed
791 tests, 10 to 16 scontent tests for 196 prefabs, 396 textures, 197 modelsobserved
13.5 / 12.9 / 4.8 MBworst label load, category / isolate / condition layouts (3 biomes)observed
5duplicated assets in the category layout (2 textures, Lit.shader, 2 fallbacks)observed
0 to 63 msbundles still loaded after the last Release (7 player runs)observed
60 to 158 s / 5 to 23 sfirst macOS Mono player build / incremental rebuilds (shared machine); 127.4 MB playerobserved
0.4 to 1.2 s vs 10 to 17 sthe same job through a resident editor's bridge vs a batch job with editor startobserved
4 GBceiling per bundle for cross-platform compatibilityAddressables 2.9 manual
30,000 verticesexample FBX budget warningUnity tutorial, qZ5NmyoxKRk [00:03:55]
38%, about 110 MBValheim memory cut from streaming, then from fewer loaded bundlesAxelsson [00:03:02], [00:30:41]
179 s / 486 sgenerated ci/pipeline.sh from a checkout without Library/ (v0.2, quiet machine / v0.1, 6 to 8 other editors)observed
0 / 8 / 6unity test exit codes: pass / tests failed (never retry) / no verdict (retry)unity-cli skill

Quality gates

  • Measurable: envelope ok, no compile errors, active_target equal on every stage; ImportDrop counts; consistency check clean under Assets/; prefab count; rerun: copied 0, git status clean; implicit_duplicates 0 and duplicated_assets 0; per-label KB; no build scene hard-referencing Addressable content; NUnit failed 0 with the expected total; AGENT_GATE ok; BuildReport Succeeded; player smoke counts; release: clean tree, provenance source.dirty false, no forbidden defines; CI script exit 0 from a clean checkout.
  • Visual: lineup sheet opened: not magenta, normal maps shading, props upright, pivots on the ground, sizes plausible next to the 1.8 m capsule.

Common mistakes

MistakeWhat it looks likeFix
importer settings in OnPostprocessTexture; code changed, GetVersion() not bumpedold settings used; machines disagreeOnPreprocess*; bump the version; -consistencyCheck
non-import keys added to the rules JSONevery governed asset reimportsseparate file (pipeline_checks.json)
Undo.RecordObject(gameObject) before moving itmove not undoablerecord the Transform
direct write on a prefab instance or a ScriptableObjectreverts at the next prefab update / file unchangedRecordPrefabInstancePropertyModifications / SetDirty
StartAssetEditing without finally; SaveAndReimport per FBX outside a batchfrozen database; 4x slower remapstry/finally; reimport inside the batch
stages without the same -buildTargeteach stage reimports textures and shadersthe same target on every stage, tests included
one group per folder with shared texturesthe same texture and shader in every bundlecondition packing; build layout check
labels added in file or HashSet orderthe settings file differs between machinesordinal order
a build scene references an Addressable prefabloaded twice, bundles bypassedHardReferences in the gate
content built, then a default player buildcontent rebuilt, archived state staleDoNotBuildWithPlayer + gate
SetActiveBuildProfile in a batch job; profile from the internal APIold target or defines; breaks on upgrade-activeBuildProfile; copy a committed template
a test reimports an asset whose importer logs an error"Unhandled log message", test failsLogAssert.Expect
tests in a test asmdef calling code in Assembly-CSharp-EditorCS0103, every batch job abortspipeline code in its own Editor asmdef
-quit with Accelerator, no wait flag; server unreachableuploads lost; job passes silently-cacheServerWaitForUploadCompletion; check cache server=
release from a dirty treeprovenance dirty: true, the CLI still buildsclean tree, RELEASE=1, gitignore Addressables' link.xml
Blender default FBX exportroot rotated 90 degrees, scale 100FBX All + Apply Transform (scenario-blender-expert)
duplicate name resolved by orderthe wrong asset silently winsreject every copy, ask
Addressables settings created inside a jobthe next run rewrites the settings file onceset the two provider types after GetSettings(true)
-quit with -runTests; relative --output-pathno XML; build outside the projectomit -quit; absolute path

Handoffs

  • Receives: FBX and textures with export settings from scenario-blender-expert, scenario-maya-expert, scenario-3d, scenario-textures; code layout and asmdefs from scenario-unity-architecture; which props load together from scenario-unity-world-building.
  • Delivers: to scenario-unity-performance the build report, bundle sizes, per-label loads; to scenario-unity-mobile texture formats (this skill sets size caps only) and signed builds; to scenario-unity-web Web builds (no WaitForCompletion on WebGL); to scenario-unity-rendering-lighting lightmap UV needs; to the lead: rules JSON, props manifest, envelopes, NUnit totals, layout JSON, BuildReport, provenance, contact sheet.

Unity 6.3 notes

  • Addressables 2.9.1 is this editor's default (folder keys and await handle are 4.0); its postprocessor adopts any imported group asset into the default settings. Content Directories replace AssetBundle builds in 6.6.
  • IPreprocessBuildWithContext also fires for AssetBundle builds: filter with BuildPipeline.isBuildingPlayer.
  • No public profile-creation API before 6.5; AssetDatabase counters are public in UnityEditor.Experimental.AssetDatabaseExperimental.counters.
  • The Unity CLI is beta; unity build writes its provenance manifest inside the .app on macOS. Personal licenses activate only through Hub sign-in.

References

© 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 26 other files (scripts, references) in skills/game-engines/unity/scenario-unity-pipeline-automation of scenario-labs/skills.

  • SKILL.md
  • references/critique.md
  • references/expert-notes.md
  • references/gui-paths.md
  • references/procedures.md
  • references/sources.md
  • scripts/AgentKit/Pipeline/AddressablesJobs.cs
  • scripts/AgentKit/Pipeline/ArtDropJobs.cs
  • scripts/AgentKit/Pipeline/EditorEditJobs.cs
  • scripts/AgentKit/Pipeline/PipelineBuild.cs
  • scripts/AgentKit/Pipeline/PipelineChecks.cs
  • scripts/AgentKit/Pipeline/PipelineRules.cs
  • scripts/AgentKit/Pipeline/PropImportPostprocessor.cs
  • scripts/AgentKit/Pipeline/Tests/PipelineContentTests.cs
  • scripts/AgentKit/PipelineCli/AgentKit.PipelineCli.asmdef
  • … and 12 more

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Unity Pipeline Automation 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 Unity Pipeline Automation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Unity Pipeline Automation this skillscenario-labs/skills946—~5kAutomated safety check: PassMIT
Export Pipelinejame581/GodotPrompter805—~3.5kAutomated safety check: PassMIT
Godot Export Buildsthedivergentai/GD-Agentic-Skills821—~3kAutomated safety check: PassLGPL-3.0
Godot Gdscript Headless Testinggamedev-skills/awesome-gamedev-agent-skills1.4k—~2.3kAutomated safety check: PassApache-2.0
Unity Build Pipelinegamedev-skills/awesome-gamedev-agent-skills1.4k—~1.5kAutomated safety check: PassApache-2.0
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Export Pipeline

    jame581/GodotPrompter

    A skill your agent uses when exporting and distributing Godot games — export presets, platform settings, CI/CD with GitHub Actions

    805 GitHub stars~3.5k tokensUpdated 2 days ago
    Game DevelopmentAuto-check passed
  • Godot Export Builds

    thedivergentai/GD-Agentic-Skills

    Expert patterns for multi-platform exports including export templates (Windows/Linux/macOS/Android/iOS/Web), command-line exports (headless mode), platform-specific settings (codesign, notarization…

    821 GitHub stars~3k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Godot Gdscript Headless Testing

    gamedev-skills/awesome-gamedev-agent-skills

    Run GDScript test suites from the command line with godot --headless, using a SceneTree/MainLoop runner script that exits non-zero on failure so CI can gate merges.

    1.4k GitHub stars~2.3k tokensUpdated 2 days ago
    Game DevelopmentAuto-check passed
  • Unity Build Pipeline

    gamedev-skills/awesome-gamedev-agent-skills

    Build and ship Unity 6.3 LTS players: build settings and scenes, player/quality settings, the IL2CPP vs Mono scripting backend, managed code stripping, scripted BuildPipeline.BuildPlayer, and…

    1.4k GitHub stars~1.5k tokensUpdated 2 days ago
    Game DevelopmentAuto-check passed
  • Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed
  • Babysit PR To Pass CI

    sgl-project/sglang

    Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.

    37k GitHub starsUsed in 2 repos~3k tokens
    DevelopmentAuto-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

Works with

Questions about Scenario Unity Pipeline Automation

What does Scenario Unity Pipeline Automation do?

A skill your agent uses when automating a Unity 6.3 content pipeline or build: importing an art drop (FBX, PNG) with AssetPostprocessor rules and naming conventions, generating prefabs or editing…. Scenario Unity Pipeline Automation is an agent skill from scenario-labs/skills.

When should I use Scenario Unity Pipeline Automation?

Scenario Unity Pipeline Automation fits situations like: automating a Unity 6.3 content pipeline; build: importing an art drop (FBX; PNG) with AssetPostprocessor rules and naming conventions; generating prefabs.

How do I install Scenario Unity Pipeline Automation in Claude Code?

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

How do I install Scenario Unity Pipeline Automation in Codex?

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

Can I use Scenario Unity Pipeline Automation 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-unity-pipeline-automation -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-unity-pipeline-automation, .gemini/skills/scenario-unity-pipeline-automation, .github/skills/scenario-unity-pipeline-automation and .opencode/skills/scenario-unity-pipeline-automation in your project.

What does Scenario Unity Pipeline Automation need to run?

Going by SKILL.md and its folder, Scenario Unity Pipeline Automation needs C# for the scripts in its folder and the command-line tools its instructions call (git and npx). Our summary lists: Node.js.

Does Scenario Unity Pipeline Automation access the network?

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

Is Scenario Unity Pipeline Automation 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 Unity Pipeline Automation use?

Scenario Unity Pipeline Automation 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 Unity Pipeline Automation use?

About 5k tokens (SKILL.md is roughly 20k 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 31k tokens, read only when the agent opens those files.

What are the alternatives to Scenario Unity Pipeline Automation?

Skills that share tags, products or a category with Scenario Unity Pipeline Automation: Export Pipeline (jame581/GodotPrompter, 805 stars), Godot Export Builds (thedivergentai/GD-Agentic-Skills, 821 stars), Godot Gdscript Headless Testing (gamedev-skills/awesome-gamedev-agent-skills, 1.4k stars) and Unity Build Pipeline (gamedev-skills/awesome-gamedev-agent-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Unity Pipeline Automation?

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.