scenario-unity-pipeline-automation
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,…
Install / Use
npx skills add scenario-labs/skills --skill scenario-unity-pipeline-automationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of scenario-unity-pipeline-automation
scenario-unity-pipeline-automation scores 86/100 on our quality scale, 1795th of 2,758 Automation skills we index.
Its SKILL.md is 20 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 35 days ago, so scenario-unity-pipeline-automation is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-20. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-unity-pipeline-automation compared with similar skills
All 4 of these similar skills score higher than scenario-unity-pipeline-automation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-unity-pipeline-automation (this skill)by scenario-labs | 86 | 1.0k | 35d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 114.0k | today | CLAUDE.md |
| rufloby ruvnet | 100 | 82.3k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 40.6k | 12d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 104.9k | 5d ago | MCP Server |
Frequently asked questions
- How do I install scenario-unity-pipeline-automation?
- Run
npx skills add scenario-labs/skills --skill scenario-unity-pipeline-automation. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-unity-pipeline-automation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-unity-pipeline-automation safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-unity-pipeline-automation still maintained?
- The repository was last updated 35 days ago, so scenario-unity-pipeline-automation is actively maintained.
Skill content
View source on GitHubname: 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, load it with skill_get
(Scenario MCP) or ask the user to install it (https://github.com/scenario-labs/skills#install);
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)
- 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:-consistencyCheckbefore 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). - 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 withoutSetDirty. - One AssetDatabase batch per stage, measured.
StartAssetEditing/StopAssetEditingintry/finally(Abud Chavez [00:30:21]), andSaveAndReimport/ImportAssetinside 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. - 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. - 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.
- 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.
- 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-quitwith-runTests. - 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, amanifest.csvfor extra labels. - Loading conditions: loaded as a set (level, biome) or one by one? Default: labels,
key_by="label"; streaming useskey_by="root". - Targets and budgets: platforms (one
-buildTargetper 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.binper 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
- Preflight.
ut_env.preflight(P);ut_pipeline.install(P). Editor open: the same jobs throughut_live.callor the[CliCommand]tools. Pipeline code a team's tests must call: its own Editor asmdef plus a test asmdef (install_asmdef_template). GATE:Echook, zero compile errors (one aborts every batch job). - Scan the drop offline.
up.scan_drop(drop), same rules JSON. GATE: every reject has a reason; duplicates reject every copy. - 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 underAssets/. - Materials and prefabs.
up.build_prefabs(P, target=T): URP Lit per prop, keywords byShaderGUI.ValidateMaterial, FBX remaps withSaveAndReimportinside 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 statusclean). - Look at it.
EditorEditJobs.BuildLineupthenAgentCapture.CaptureViewswithgraphics=True,ut_review.review_capture, open the sheet. GATE: no magenta, black or blank flags; props upright, grounded, in scale. - Addressables groups.
up.assign_addressables(P, "condition", target=T). GATE:implicit_duplicates == 0;up.hard_references(P)ok. - 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. - 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. - Player build. Profile copied from a committed template (
PipelineBuild.CreateBuildProfilewithtemplate),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_GATEok withhard_references0, BuildReportSucceeded. - Smoke the player.
up.player_smoke(app, label). GATE: loaded assets equal the manifest count; bundles unload after release. - CI.
up.write_ci(repo):ci/pipeline.sh(one process per stage, the same-buildTargeton each;ACCELERATOR=,CONSISTENCY=1,RELEASE=1) and GitHub Actions files. GATE: passes from a checkout withoutLibrary/; license returnedif: always(); with Accelerator, the log'scache server=count above 0.
Numbers
| Value | Relative to | Source |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------- | -------------------------------------- |
| 5.6 to 6.7 s | 593 files copied and imported in one batch | observed |
| 19.0 s vs 5.1 s | two remap passes over 195 FBX (SaveAndReimport), one by one vs in one batch | observed |
| 11 to 12 s | 197 materials, 197 FBX remaps, 196 Prefab Variants, in-editor time | observed |
| 1,717 imports, 52 s / 60 imports | first launch on another platform / switching back (cached artifacts) | observed |
| 1,513 textures, 17 s | reimported by one GetVersion() bump of a do-nothing texture postprocessor | observed |
| 12,184 checked, 23.5 s | -consistencyCheck of this project (7,390 skipped; 2 URP shaders flagged: baseline packages) | observed |
| 0 files | changed by a second full run (import, prefabs, groups) | observed |
| 791 tests, 10 to 16 s | content tests for 196 prefabs, 396 textures, 197 models | observed |
| 13.5 / 12.9 / 4.8 MB | worst label load, category / isolate / condition layouts (3 biomes) | observed |
| 5 | duplicated assets in the category layout (2 textures, Lit.shader, 2 fallbacks) | observed |
| 0 to 63 ms | bundles still loaded after the last Release (7 player runs) | observed |
| 60 to 158 s / 5 to 23 s | first macOS Mono player build / incremental rebuilds (shared machine); 127.4 MB player | observed |
| 0.4 to 1.2 s vs 10 to 17 s | the same job through a resident editor's bridge vs a batch job with editor start | observed |
| 4 GB | ceiling per bundle for cross-platform compatibility
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
114.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.3k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
40.6kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
104.9k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
