unity-developer

Build Unity games with optimized C# scripts, efficient rendering, and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and cross-platform deployment. Handles gameplay systems, UI implementation, and platform optimization. Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform builds.

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/unity-developer/SKILL.md

Quality

Content

21%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body reads as a persona/capability profile rather than actionable skill guidance: it enumerates Unity domain knowledge Claude already has without code, commands, or validation-gated workflows, and inlines everything in one file.

Suggestions

Replace the capability/knowledge bullet lists with a concise overview plus concrete, executable examples (e.g. profiler-driven optimization snippet, an Addressables loading pattern, a URP render feature) for the most common tasks.

Add a real multi-step workflow with validation checkpoints for risky operations (build/deploy, asset bundle generation) instead of the abstract Response Approach phases.

Move the long capability and knowledge-base enumerations into separate reference files (e.g. references/rendering.md, references/platforms.md) and link to them one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is a ~230-line enumeration of Unity capabilities, behavioral traits, and knowledge topics that largely restates what Claude already knows about Unity, with heavy padding via repeated capability bullet lists.	2 / 5
Actionability	No executable code or commands appear anywhere; sections like Instructions ("Apply relevant best practices and validate outcomes") and Response Approach ("Provide production-ready C# code") only describe rather than instruct.	1 / 5
Workflow Clarity	The numbered Response Approach gives a rough sequence (analyze, recommend, implement, test, deploy) but steps are abstract phases with no concrete commands and no validation checkpoints.	2 / 5
Progressive Disclosure	Clear section/subsection headers provide some structure, but no bundle files or external references exist and large capability lists that belong in separate references are fully inlined in one monolithic file.	3 / 5
	Total	8 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete, with an explicit "Use PROACTIVELY for..." trigger clause covering both what and when. Minor room to sharpen the action list and broaden trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("optimized C# scripts, efficient rendering, and proper asset management", "gameplay systems, UI implementation, and platform optimization") but "Masters..." and "Handles..." phrasing stays somewhat high-level rather than fully enumerating capabilities.	4 / 5
Completeness	Explicitly answers both what ("Build Unity games with optimized C# scripts, efficient rendering...") and when ("Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform builds") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform builds" surfaces natural user phrases, with good coverage of Unity-specific triggers though a few common synonyms (e.g. shaders, mobile builds) are absent.	4 / 5
Distinctiveness Conflict Risk	The Unity 6 LTS / URP / HDRP niche is well-scoped with distinct triggers, making conflict with non-Unity skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/unity-developer/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.