Skip to content
SkillModel-led1,821 tokens in use

unity-build-pipeline

Helps an agent configure, script and automate Unity 6.3 player builds: scene lists, Build Profiles, IL2CPP vs Mono, code stripping, Addressables and CI.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/unity/unity-build-pipeline
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing unity-build-pipeline costs

86tokens idle
1,821tokens in use
3,428tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure23/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 88

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill helps an agent set up repeatable Unity player builds. It covers the scene list and platform target, the choice between Mono and IL2CPP, managed stripping with a link.xml, and a scripted BuildPlayer call whose result is checked so a failed build fails the pipeline.

It includes a headless command line for CI, a pattern for building a saved Build Profile, and a reference with a parameterised build method that stamps a version and sets exit codes. A gotchas list covers scenes missing from a build, errors that appear only in the player and stale Addressables content.

What You Get

  • A seven-step core workflow from the scene list to verifying that the built player runs
  • Four patterns: a scripted build with a result check, a headless command, a Build Profile build and a link.xml
  • A reference with a CI build method that parses arguments, stamps a version and exits with a code
  • A gotchas list covering missing scenes, toolchain failures, stripped reflection code, stale Addressables and platform defines

Common Use Cases

  • Setting up a repeatable command-line build for a build server
  • Fixing a MissingMethodException that only appears in the built player
  • Building one saved Build Profile from the command line
  • Making a pipeline fail when BuildPlayer returns errors

What Makes It Unique

The skill spells out batch-mode limits, such as picking the platform with the buildTarget flag since switching targets inside a running method is unavailable, and it warns that Addressables content may be skipped on a clean runner. It stays on the Unity side and sends size work and store uploads to sibling skills.

Under The Hood

The agent loads the SKILL.md and, for CI work, one reference with a complete build script. It edits C# editor scripts, link.xml and project settings files. It can run the Unity Editor on the command line in batch mode with an execute-method flag to build a player and read the exit code and log, and the skill shows how to launch the built player to check it. It warns against putting license credentials in command arguments, shell history or logs. Nothing is fetched from the web during normal use; documentation pages are named for re-checking.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers