Skip to content
SkillScript-led2,002 tokens in use

unity-csharp-scripting

Helps an agent write and fix Unity 6.3 C# gameplay scripts: MonoBehaviour lifecycle, serialization, .meta and GUID discipline, and command-line compile and tests.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/unity/unity-csharp-scripting
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-csharp-scripting costs

88tokens idle
2,002tokens in use
4,805tokens, 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 Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

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

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
  • Frontmatter8/15
  • Structure25/25
  • Examples12/15
  • Output10/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

No findings.

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 write correct MonoBehaviour scripts for Unity 6.3 LTS and keep the project’s .meta files intact. It reads the project’s versions and assembly definitions first, picks lifecycle callbacks by purpose, exposes tunables with private serialized fields and moves every file together with its .meta.

A Python checker reports duplicate or malformed GUIDs, files moved without their .meta and missing script references. A reference shows how to compile and run EditMode and PlayMode tests from a terminal, with or without the Unity CLI, and how to read the results.

What You Get

  • A seven-step workflow from reading project versions to proving behavior with a test
  • A project checker that reports GUID, .meta and missing-script errors without opening Unity
  • Patterns for serialized fields that survive renames and a coroutine that stops cleanly
  • A reference with CLI and batch-mode commands, test assembly files and how to read NUnit results

Common Use Cases

  • Fixing Missing script after a file was renamed or moved
  • Renaming a serialized field without losing scene values
  • Compiling a Unity project from a terminal and grepping for compile errors
  • Adding an EditMode or PlayMode test for a gameplay change

What Makes It Unique

The skill treats the .meta file as part of the code: it moves each file with its .meta and runs a checker that finds broken GUIDs before Unity does. It also covers command-line proof of behavior, including exit codes that tell a failed test from a run that never finished, and names Unity-specific traps such as null checks on destroyed objects.

Under The Hood

The agent loads the SKILL.md and, as needed, references on lifecycle and on command-line checks. It reads project version and package files, edits C# and assembly definition files, and runs a read-only Python script on the project folder. It can run the Unity Editor in batch mode to compile and run tests, and, when the Unity command line tool and a ready Editor exist, run commands that recompile, run tests and evaluate C# in the running Editor. A reference mentions installing that tool with a downloaded install script piped to a shell, and tells the agent to ask you first. Nothing else is fetched during normal use.

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