Agent skill

Unity Build Pipeline

by gamedev-skills in 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…

Apache-2.0Auto-check passedGame Development

Install Unity Build Pipeline

skills CLI

$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-build-pipeline -a claude-code

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

GitHub CLI

$ gh skill install gamedev-skills/awesome-gamedev-agent-skills unity-build-pipeline --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/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/unity/unity-build-pipeline .claude/skills/unity-build-pipeline && 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/

Paste into Claude Code

Install the "unity-build-pipeline" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/skills/unity/unity-build-pipeline into .claude/skills/unity-build-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unity-build-pipeline", 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

$skill-installer install https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/skills/unity/unity-build-pipeline

Type 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.

skills CLI

$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-build-pipeline -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install gamedev-skills/awesome-gamedev-agent-skills unity-build-pipeline --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/unity/unity-build-pipeline .agents/skills/unity-build-pipeline && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "unity-build-pipeline" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/skills/unity/unity-build-pipeline into .agents/skills/unity-build-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unity-build-pipeline", 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.

skills CLI

$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-build-pipeline -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install gamedev-skills/awesome-gamedev-agent-skills unity-build-pipeline --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/unity/unity-build-pipeline .cursor/skills/unity-build-pipeline && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "unity-build-pipeline" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/skills/unity/unity-build-pipeline into .cursor/skills/unity-build-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unity-build-pipeline", 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

$ gemini skills install https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git --path skills/unity/unity-build-pipeline

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-build-pipeline -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install gamedev-skills/awesome-gamedev-agent-skills unity-build-pipeline --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/unity/unity-build-pipeline .gemini/skills/unity-build-pipeline && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "unity-build-pipeline" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/skills/unity/unity-build-pipeline into .gemini/skills/unity-build-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unity-build-pipeline", 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.

GitHub CLI

$ gh skill install gamedev-skills/awesome-gamedev-agent-skills unity-build-pipeline

Installs 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).

skills CLI

$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-build-pipeline -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/unity/unity-build-pipeline .github/skills/unity-build-pipeline && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "unity-build-pipeline" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/skills/unity/unity-build-pipeline into .github/skills/unity-build-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unity-build-pipeline", 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.

skills CLI

$ npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-build-pipeline -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install gamedev-skills/awesome-gamedev-agent-skills unity-build-pipeline --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/unity/unity-build-pipeline .opencode/skills/unity-build-pipeline && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "unity-build-pipeline" agent skill from https://github.com/gamedev-skills/awesome-gamedev-agent-skills/tree/main/skills/unity/unity-build-pipeline into .opencode/skills/unity-build-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unity-build-pipeline", 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: unity-build-pipeline
GitHub stars: 1.4k
Token cost: ~1.5k tokens
SKILL.md length: 498 words
Files: 2 (incl. references)
Skills in repo: 53
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

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…

Works in 3 steps: Scripted build with a result check → Headless / CI invocation → Protect stripped code with link.xml
Automating a build
SKILL.md covers When to use, Core workflow, Patterns and Pitfalls, plus 2 more sections
Reaches docs.unity3d.com

What it does

Unity Build Pipeline is an agent skill from 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 CI/headless builds. Use when configuring or automating a build, choosing a scripting backend, shrinking build size, or when the user mentions Unity build, player settings, IL2CPP, code stripping, or Addressables.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/ci-build-script.md`).

It sits in Game Development, covering Game development and CI/CD. The repository describes itself as: 74 game-dev skills for AI coding agents — Godot, Unity, Unreal, Phaser, PixiJS, three.js, Bevy, pygame, LÖVE, Roblox. Portable SKILL.md Agent Skills (the format Anthropic… The licence is Apache-2.0.

When your agent uses it

Automating a build
Choosing a scripting backend
Shrinking build size
The user mentions Unity build

Example prompts

“/unity-build-pipeline”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Scripted build with a result check
Headless / CI invocation
Protect stripped code with link.xml

What it can do on your machine

Read from SKILL.md and the folder at commit 0a70cfc. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are csharp, bash and xml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- docs.unity3d.com
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

Unity Build Pipeline loads about 1.5k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 498 words of instructions outside code blocks.

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

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 gamedev-skills/awesome-gamedev-agent-skills at commit 0a70cfc, republished under its Apache-2.0 licence (© gamedev-skills). 498 words, ~1,462 tokens.

Download SKILL.mdSave it as .claude/skills/unity-build-pipeline/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: unity-build-pipeline
description: 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 CI/headless builds. Use when configuring or automating a build, choosing a scripting backend, shrinking build size, or when the user mentions Unity build, player settings, IL2CPP, code stripping, or Addressables.

Unity Build Pipeline

Configure, script, and automate Unity 6.3 LTS player builds: scenes, platform target, scripting backend, stripping, and headless/CI builds. Targets Unity 6.3 LTS (6000.3).

When to use

Use when setting up Build Settings/Profiles, choosing a platform and scripting backend (Mono vs IL2CPP), reducing build size with managed stripping, scripting a repeatable build with BuildPipeline.BuildPlayer, or wiring a CI/headless build.
Use when the project has ProjectSettings/EditorBuildSettings.asset or a CI build script.

When not to use: authoring a CI service config end-to-end is DevOps; this skill covers the Unity-side build API and settings. Console/platform certification specifics are platform-NDA territory. Storefront submission → steam-publish / itch-publish.

Core workflow

List the scenes to build (File → Build Profiles/Settings → Scene List, or EditorBuildSettings.scenes). Only listed, enabled scenes ship; scene 0 is the start scene.
Pick the platform target and switch the active build target if needed (BuildTarget / EditorUserBuildSettings).
Choose the scripting backend (Player Settings): Mono (fast iteration, desktop) vs IL2CPP (AOT C++; required for many platforms, better perf, harder to reverse). IL2CPP needs the platform's C++ toolchain installed. (Forward note: Unity is developing a CoreCLR backend as a modern .NET runtime successor to Mono, but it is experimental, desktop-only, and not production-ready as of Unity 6.7 — so for 6.3 LTS the choice stays Mono vs IL2CPP.)
Tune size/perf: set Managed Stripping Level (Disabled → Minimal → Low → Medium → High) and protect reflection-only code with a link.xml. Set Quality Settings per platform.
Script the build with BuildPipeline.BuildPlayer(BuildPlayerOptions) and inspect the returned BuildReport — a non-Succeeded result must fail your pipeline.
Run headless for CI with -batchmode -quit -executeMethod, and check the exit code.
Verify the actual output runs (launch the player), not just that the build returned without throwing.

Patterns

1. Scripted build with a result check

csharp

using UnityEditor;
using UnityEditor.Build.Reporting;
using UnityEngine;

public static class BuildScript
{
    [MenuItem("Build/Windows x64")]
    public static void BuildWindows()
    {
        var options = new BuildPlayerOptions
        {
            scenes = new[] { "Assets/Scenes/Main.unity", "Assets/Scenes/Level1.unity" },
            locationPathName = "Builds/Windows/Game.exe",
            target = BuildTarget.StandaloneWindows64,
            options = BuildOptions.None,            // add BuildOptions.Development for a dev build
        };

        BuildReport report = BuildPipeline.BuildPlayer(options);
        BuildSummary summary = report.summary;

        if (summary.result != BuildResult.Succeeded)
            throw new System.Exception($"Build failed: {summary.totalErrors} errors");
        Debug.Log($"Build OK: {summary.totalSize} bytes in {summary.totalTime}");
    }
}

2. Headless / CI invocation

bash

# Exit code is 0 on success; -quit ensures the editor closes; -nographics for build servers.
Unity -batchmode -quit -nographics \
  -projectPath "/path/to/Project" \
  -executeMethod BuildScript.BuildWindows \
  -logFile -

Show full SKILL.md (200 more words)Show less

3. Protect stripped code with `link.xml`

xml

<!-- Assets/link.xml — keep types the linker can't see are used (reflection, JSON, plugins). -->
<linker>
  <assembly fullname="MyGameRuntime" preserve="all"/>
</linker>

Pitfalls

A scene loads in the Editor but is missing in the build — it isn't in the Build Settings scene list (or is disabled). SceneManager.LoadScene only sees listed scenes.
IL2CPP build fails on a fresh machine — the platform C++ toolchain (e.g. Windows build tools, Android NDK) isn't installed. Mono has no such requirement.
MissingMethodException/TypeLoadException only in the build — managed stripping removed reflection-only code. Lower the stripping level or add a link.xml preserve entry.
Treating "BuildPlayer returned" as success — always check BuildReport.summary.result; it can return with errors.
Addressables content is stale/missing — Addressables (com.unity.addressables) need a separate content build (Build → Addressables) and a profile pointing at the right load path; a player build alone doesn't rebuild them.
Shipping a Development build — BuildOptions.Development enables the profiler/debugging and is slower; use BuildOptions.None for release.

References

For a complete multi-platform CI build script (target switching, version stamping, argument parsing, exit codes) and an Addressables content-build call, read references/ci-build-script.md.
Primary docs: ScriptReference/BuildPipeline.BuildPlayer, Unity Manual build sections (player settings, managed code stripping). For the forward-looking CoreCLR backend, see the experimental note at https://docs.unity3d.com/6000.7/Documentation/Manual/scripting-backends-coreclr.html.

steam-publish / itch-publish — distributing the player you just built.
unity-csharp-scripting — editor scripting conventions used by build scripts.

Files

SKILL.md and 1 other file (references) in skills/unity/unity-build-pipeline of gamedev-skills/awesome-gamedev-agent-skills.

SKILL.md
references/ci-build-script.md

Open the folder on GitHubat commit 0a70cfc

Compare with similar skills

Unity Build Pipeline 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.

Unity Build Pipeline compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Unity Build Pipeline this skillgamedev-skills/awesome-gamedev-agent-skills	1.4k	—	~1.5k	Automated safety check: Pass	Apache-2.0	2 days ago
Export Pipelinejame581/GodotPrompter	805	—	~3.5k	Automated safety check: Pass	MIT	yesterday
Scenario Unity Pipeline Automationscenario-labs/skills	946	—	~5k	Automated safety check: Pass	MIT	yesterday
Godot Export Buildsthedivergentai/GD-Agentic-Skills	821	—	~3k	Automated safety check: Pass	LGPL-3.0	1 mo ago
Godot Gdscript Patterns925236118/AlphaAgent	103	10 repos	~5k	Automated safety check: Pass	MIT	3 days ago
Sprite Genaldegad/sprite-gen	2.7k	—	~4.9k	Automated safety check: Pass	Apache-2.0	yesterday

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 yesterday
Game DevelopmentAuto-check passed
Scenario Unity Pipeline Automation
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…
946 GitHub stars~5k tokensUpdated yesterday
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 Patterns
925236118/AlphaAgent
Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization.
103 GitHub starsUsed in 10 repos~5k tokens
Game DevelopmentAuto-check passed
Sprite Gen
aldegad/sprite-gen
Generates images and game sprites through GPT or Grok with guided provider choices, separate saved defaults, automatic cleanup and optional curation.
2.7k GitHub stars~4.9k tokensUpdated yesterday
Game DevelopmentAuto-check passed
2D Map and Scene Generator
0x0funky/agent-sprite-forge
Plans and builds 2D game maps and scenes, from tilemaps and parallax backgrounds to HD-2D plates, with collision checks, a playable HTML preview and Tiled, Godot or LDtk export.
4.4k GitHub stars~2.9k tokensUpdated 4 days ago
Game DevelopmentAuto-check passed

More from gamedev-skills/awesome-gamedev-agent-skills

All 53 skills in this repo

Create Game Assets
gamedev-skills/awesome-gamedev-agent-skills
Plan, generate, source, normalize, and validate cohesive visual game assets.
1.4k GitHub stars~2k tokensUpdated 2 days ago
Auto-check passed
Roblox UI
gamedev-skills/awesome-gamedev-agent-skills
Build production Roblox interfaces with ScreenGui/PlayerGui lifecycle, responsive UDim2 layouts, safe insets, reusable editable Instances, cross-device input and selection, restrained motion…
1.4k GitHub stars~2.9k tokensUpdated 2 days ago
Auto-check passed
AI Behavior Trees Utility AI
gamedev-skills/awesome-gamedev-agent-skills
Build a production behavior-tree runtime (Blackboard, action/condition leaves, sequence/selector/parallel composites, decorators) and a Utility AI system (response curves — linear, exponential…
1.4k GitHub stars~2k tokensUpdated 2 days ago
Auto-check passed
Bevy Ecs
gamedev-skills/awesome-gamedev-agent-skills
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the…
1.4k GitHub stars~2.5k tokensUpdated 2 days ago
Auto-check passed
Card Game
gamedev-skills/awesome-gamedev-agent-skills
Build a card game: card data, deck/hand/discard zones, draw/shuffle/reshuffle, a turn structure, costs, and effect resolution.
1.4k GitHub stars~1.6k tokensUpdated 2 days ago
Auto-check passed
Fps Shooter
gamedev-skills/awesome-gamedev-agent-skills
Build a first-person shooter: move+mouse-look controller, hitscan or projectile shooting, weapons, health, and enemy AI.
1.4k GitHub stars~1.5k tokensUpdated 2 days ago
Auto-check passed

Questions about Unity Build Pipeline

What does Unity Build Pipeline do?

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…. Unity Build Pipeline is an agent skill from gamedev-skills/awesome-gamedev-agent-skills.BuildPlayer, and CI/headless builds.

When should I use Unity Build Pipeline?

Unity Build Pipeline fits situations like: automating a build; choosing a scripting backend; shrinking build size; the user mentions Unity build.

How do I install Unity Build Pipeline in Claude Code?

Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-build-pipeline -a claude-code`. Or copy the skill folder (skills/unity/unity-build-pipeline in gamedev-skills/awesome-gamedev-agent-skills) into .claude/skills/unity-build-pipeline in your project. Claude Code loads it when a task matches its description.

How do I install Unity Build Pipeline in Codex?

Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-build-pipeline -a codex`. Or copy the skill folder (skills/unity/unity-build-pipeline in gamedev-skills/awesome-gamedev-agent-skills) into .agents/skills/unity-build-pipeline in your project. Codex loads it when a task matches its description.

Can I use Unity Build Pipeline 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 gamedev-skills/awesome-gamedev-agent-skills --skill unity-build-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/unity-build-pipeline, .gemini/skills/unity-build-pipeline, .github/skills/unity-build-pipeline and .opencode/skills/unity-build-pipeline in your project.

What does Unity Build Pipeline need to run?

SKILL.md names no scripts, command-line tools or credentials: Unity Build Pipeline is instructions for the agent only.

Does Unity Build Pipeline access the network?

SKILL.md names 1 domain. In commands or code: docs.unity3d.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

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

Unity Build Pipeline is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Unity Build Pipeline use?

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

What are the alternatives to Unity Build Pipeline?

Skills that share tags, products or a category with Unity Build Pipeline: Export Pipeline (jame581/GodotPrompter, 805 stars), Scenario Unity Pipeline Automation (scenario-labs/skills, 946 stars), Godot Export Builds (thedivergentai/GD-Agentic-Skills, 821 stars) and Godot Gdscript Patterns (925236118/AlphaAgent, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Unity Build Pipeline?

gamedev-skills (a GitHub organization) maintains it in gamedev-skills/awesome-gamedev-agent-skills, which has 1,389 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on October 9, 2026.

Source: gamedev-skills/awesome-gamedev-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Unity Build Pipeline

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Unity Build Pipeline

When to use

Core workflow

Patterns

1. Scripted build with a result check

2. Headless / CI invocation

3. Protect stripped code with link.xml

Pitfalls

References

Related skills

Files

Compare with similar skills

Similar skills

More from gamedev-skills/awesome-gamedev-agent-skills

Related

Questions about Unity Build Pipeline

3. Protect stripped code with `link.xml`