CtrlK
BlogDocsLog inGet started
Tessl Logo

unity-version-split

Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A focused, actionable skill body with concrete code examples, a clear step sequence, and a verification step. Minor redundancy in the API mapping tables and an implicit error-recovery loop keep it just short of top marks.

Suggestions

De-duplicate the EntityId/int and GetEntityId/GetInstanceID mappings between "When to Use" and the Step 2 table, keeping the detailed table only in Step 2.

Make the verify step an explicit feedback loop: after console-get-logs, state 'if errors, fix the offending file and re-run assets-refresh + console-get-logs'.

Consider noting that the listed Reference Files are existing codebase examples to consult, so the pointer intent is unambiguous.

DimensionReasoningScore

Conciseness

Mostly lean with efficient tables and no padding of basic concepts, but the EntityId/int and GetEntityId/GetInstanceID mappings appear redundantly in both "When to Use" and the Step 2 table.

4 / 5

Actionability

Provides copy-paste-ready preprocessor guards, a concrete file-naming table, a real before/after C# example, and specific tool commands (assets-refresh, console-get-logs) covering the common cases.

5 / 5

Workflow Clarity

A clear five-step sequence with a verification checkpoint (Step 5, console-get-logs) and a "Both files must" checklist, but the error-recovery feedback loop (fix and re-verify on compile failure) is only implicit.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections (When to Use, File Naming, Steps, Example, Reference Files) with one-level pointers to existing codebase examples; no bundle files exist, so structure is single-file but appropriately sectioned.

4 / 5

Total

17

/

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 concise, well-targeted description that clearly states the action and the trigger conditions with concrete API examples. It avoids fluff and distinguishes itself from generic file-handling skills.

DimensionReasoningScore

Specificity

Names the concrete action ("Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants") and backs it with specific API examples (EntityId vs int, GetEntityId vs GetInstanceID), giving several specific details with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (split a C# file into two Unity-version variants) and when ("Use when a file needs different implementations for different Unity versions due to API changes") with concrete trigger phrases and examples.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ("C# file", "Unity 6.5", "different Unity versions", "API changes") with good coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow, clearly defined niche (Unity 6.5 version splitting with named APIs) that is unlikely to trigger for unrelated skills.

5 / 5

Total

18

/

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
IvanMurzak/Unity-MCP
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.