CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

41

Quality

41%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/unity-developer/SKILL.md

The canonical home for this skill is unity-developer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

17%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 is a verbose persona/capability dump with no executable guidance, no validation checkpoints, and a broken reference path, scoring low across conciseness, actionability, workflow clarity, and progressive disclosure.

Suggestions

Replace the capability catalog with concise, actionable guidance: concrete C# snippets, profiler commands, and copy-paste-ready examples for the common Unity tasks listed in 'Example Interactions'.

Fix the reference path (use 'references/implementation-playbook.md' and create the file) or remove the pointer, and split the long capability lists into a bundled reference file so the SKILL.md body stays a lean overview.

Add a real workflow with explicit validation checkpoints (e.g. 'Profile with the Unity Profiler; if a frame exceeds budget, iterate on the bottleneck') instead of the abstract 4-step Instructions sequence.

DimensionReasoningScore

Conciseness

The body is a padded ~200-line capability resume cataloging concepts Claude already knows (Observer pattern, Singleton, C# 9.0+ features), noticeably verbose even though it is section-organized rather than prose padding.

2 / 5

Actionability

It only describes capabilities ('Unity Profiler mastery', 'Implement ECS architecture') with no concrete code, commands, or executable steps anywhere, matching the 'entirely vague or abstract; only describes rather than instructs' anchor.

1 / 5

Workflow Clarity

The Instructions and Response Approach sections give a rough generic sequence with no validation checkpoints or feedback loops, fitting the 'rough sequence present but many gaps; validation absent' anchor.

2 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the sole reference to 'resources/implementation-playbook.md' is a broken path, while capability lists that belong in separate files are inlined, matching the 'minimal structure; content that belongs in separate files is inlined' anchor.

2 / 5

Total

7

/

20

Passed

Description

66%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.

The description is specific and clearly Unity-scoped with good keyword coverage, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness at 3 and slightly weakens trigger-term and distinctiveness scores.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers, e.g. 'Use when building or optimizing Unity games, writing C# gameplay code, or targeting Unity 6 LTS / URP / HDRP.'

Include common user phrasings like 'Unity shader', 'mobile game', or 'Unity multiplayer' to broaden natural trigger coverage.

Tighten toward comprehensive action coverage (e.g. name asset-bundle/Addressables and networking actions) to move specificity from 4 toward 5.

DimensionReasoningScore

Specificity

Lists several concrete actions (optimized C# scripts, efficient rendering, asset management) plus specific systems (Unity 6 LTS, URP/HDRP, cross-platform), matching the 'several specific actions; minor gaps' anchor rather than the more comprehensive 5.

4 / 5

Completeness

It has a clear 'what' but no 'Use when...' trigger clause; per the judging guidelines a missing explicit 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Covers natural Unity terms ('Unity games', 'C# scripts', 'rendering', 'URP/HDRP', 'cross-platform deployment') but omits some common user phrasings like 'Unity shader' or 'mobile game', fitting the 'good coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The Unity 6 LTS / URP / HDRP framing carves a clear niche with minimal overlap risk; not a 5 only because the trigger phrasing is not maximally distinctive.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.