CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

game-engine-development

Implementa codigo e sistemas de runtime para jogos. Trigger em: "Unity C#", "Unreal C++", "MonoBehaviour", "ScriptableObject", "UCLASS", "UPROPERTY", "UFUNCTION", "object pooling jogo", "ECS Unity", "otimizar FPS", "profiler Unity", "Unreal Insights", "multiplayer networking jogo", "client-side prediction", "lag compensation", "state machine jogo", "spatial partitioning", "coroutine Unity", "Blueprint callable", "smart pointer Unreal", "implementar sistema de jogo em Unity", "Godot GDScript", "Godot instalado", "Roblox Studio", "Luau", "Rojo", "Unity batch mode", "UnrealEditor-Cmd", "Niagara", "Sequencer Unreal", "AssetPostprocessor", "Addressables", "Tilemap", "Cinemachine", "VFX Graph", "Shader Graph", "DataStore", "dirigir engine instalada".

Quality

80%

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 ./skills/67-game-engine-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured router skill: dense actionable rules, a clear workflow with explicit performance checkpoints, and exemplary progressive disclosure through a verified reference routing table. The main costs are redundancy (the Godot-gap caveat stated four times) and provenance/meta content that competes with operational tokens.

Suggestions

State the Godot coverage gap once — in the 'Cobertura de Godot' section — and make the intro, 'Quando Nao Usar', and 'Regras Duras' entries one-line pointers to it; this removes ~15 redundant lines.

Trim the 'Fontes' section to a 2-3 line attribution (repo, license, date) and move the porting/curazione treatment details into a comment or the reference files' headers, since they don't guide task execution.

Add a failure branch to the workflow checkpoints (e.g., 'if frame time > 16ms after step 4: profile the top CPU/GPU contributors and re-check before proceeding') to close the missing feedback loop and lift workflow clarity.

DimensionReasoningScore

Conciseness

The operational sections (Quando Usar, Regras Duras, Fluxo, Entradas/Saidas) are lean and directive, but the Godot-coverage caveat is repeated four separate times (intro paragraph, Quando Nao Usar bullet, Regras Duras row, and the full "Cobertura de Godot" section) and the ~20-line Fontes provenance section is administrative rather than task-serving. The redundancy exceeds anchor 4's 'minor instances of over-explanation' but the body never teaches concepts Claude already knows, so it sits above anchor 2's padded verbosity.

3 / 5

Actionability

Guidance is concrete and near-executable — "Cachear a referencia em Awake/BeginPlay", "CompareTag()", "UPROPERTY() pra referencia gerenciada, TWeakPtr pra evitar ciclo", thresholds like "frame time ≤16ms" and "60+ FPS", and named tools (Unity Profiler, Unreal Insights). It stops short of anchor 5's copy-paste-ready code because the body contains no code blocks, deferring them to references/ — appropriate for a router-style SKILL.md but still a gap against the anchor.

4 / 5

Workflow Clarity

The 5-step workflow has explicit checkpoints in steps 4 and 5 ("Checkpoint: rodar Unity Profiler ou Unreal Insights, confirmar frame time ≤16ms antes de prosseguir"; latency/desync test before release), reinforced by the "Evidencia de Conclusao" section. It misses anchor 5 because no failure-handling feedback loop exists — nothing says what to do when a checkpoint fails — while the checkpoints are explicit rather than implicit, placing it above anchor 3.

4 / 5

Progressive Disclosure

The body is a genuine overview with a 10-row routing table mapping each topic to one reference file, all of which exist in the bundle, plus explicit guidance to "carregar so o arquivo do motor/topico relevante a task, nao os cinco de cara". References are one level deep (verified: sibling files contain only occasional peer pointers, no nested chains), matching the anchor-5 pattern of a clear overview with well-signaled one-level-deep references.

5 / 5

Total

16

/

20

Passed

Description

81%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 pairs a thin one-line capability statement with an exceptionally strong, explicit trigger list covering Unity, Unreal, Godot, and Roblox phrasings users would naturally say. The 'when' is best-in-class; the 'what' would benefit from enumerating 2-3 concrete actions.

DimensionReasoningScore

Specificity

The capability statement is a single generic sentence — "Implementa codigo e sistemas de runtime para jogos" — naming the domain with at most 1-2 actions; the extensive trigger list adds topical specificity but does not enumerate the concrete actions the skill performs. Anchor 4 ('several specific actions') is not met because the what-verbs are minimal, while anchor 2 is too harsh since concrete actions beyond the bare domain are stated.

3 / 5

Completeness

Both what and when are explicitly present — "Implementa codigo e sistemas de runtime para jogos" plus an explicit "Trigger em:" clause with concrete phrases — so the missing-trigger cap of 3 does not apply. It falls short of anchor 5 because the 'what' is one thin generic sentence, unlike the multi-action anchor-5 exemplar, while the 'when' is more explicit than anchor 4 describes.

4 / 5

Trigger Term Quality

38 trigger phrases give comprehensive coverage of natural user phrasings ("implementar sistema de jogo em Unity", "otimizar FPS", "dirigir engine instalada"), API/tool names users would actually say (MonoBehaviour, UCLASS, Addressables, Niagara, Luau, Rojo), and synonyms across four engines. This matches the anchor-5 exemplar's breadth; no commonly-said phrasing category is visibly missing.

5 / 5

Distinctiveness Conflict Risk

Triggers are highly engine-specific technical terms (MonoBehaviour, UCLASS, Unreal Insights, VFX Graph, DataStore) forming a clear game-engine-code niche with minimal conflict risk. A theoretical overlap with an architecture-design skill exists for a few terms ("state machine jogo", "spatial partitioning"), but the distinct trigger set matches the anchor-5 'clear niche' example rather than anchor 4's 'minor overlap' case.

5 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/67-game-engine-development/SKILL.md

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.