CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

game-architecture-design

Projeta e revisa arquitetura e sistemas de jogos. Trigger em: "arquitetura de jogo", "design de sistema de combate", "sistema de skill de jogo", "GDD", "game design document", "revisar mecanica de jogo", "balancear economia do jogo", "curva de progressao", "drop rate", "pity system", "loot table", "metagame", "PvP balance", "paradigma de arquitetura de jogo", "ECS vs OOP para jogo", "sistema de IA de jogo", "procedural content generation", "PCG", "revisao de design de jogo", "avaliar proposta de balance", "diagnosticar desbalanceamento", "economia de jogo mobile", "sistema de buff e debuff".

Quality

89%

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

78%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-engineered instruction-only skill: concrete protocols, explicit hard rules, a simulation feedback-loop checkpoint, and exemplary progressive disclosure with a verified one-level-deep references/ structure. Remaining gaps are minor — some duplication between the outputs and completion-evidence sections, no inline worked example of a finding or balance calculation, and no validation checkpoint on the architecture front.

Suggestions

Merge "Saidas Esperadas" and "Evidencia de Conclusao" into one section (they list the same three deliverables) and compress the "Fontes" provenance note to 1-2 lines.

Add one compact worked example of a filled 6-field finding (observacao through validacao) so the review output format is shown, not just described.

Give the architecture front the same checkpoint the balance front has, e.g. an explicit step to pressure-test the paradigm decision table against the stated team/scope constraints.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no explanation of concepts Claude already knows, but "Saidas Esperadas" and "Evidencia de Conclusao" repeat nearly the same three-item list (arquitetura/review/balance deliverables), and the "Fontes" section spends ~10 lines narrating licensing provenance rather than instructing. Not 5 because these redundancies could be trimmed; not 3 because padding is minor relative to ~180 lean lines covering three fronts.

4 / 5

Actionability

Concrete, executable protocol guidance: the 6-field finding structure ("observacao, mecanismo, status de evidencia, impacto, recomendacao, validacao"), four named review modes with a selection rule ("escolher o mais estreito que resolve o pedido"), a balance relation taxonomy, and a never/instead-of hard rules table. Not 5 because there is no worked example of a filled 6-field finding or a numeric balance case inline — the common cases are described but not shown.

4 / 5

Workflow Clarity

The review workflow is explicitly sequenced ("Toda review nomeia o objeto, declara a decisao em jogo, constroi baseline de evidencia, e fecha com achados + menor intervencao + experimento de validacao") and balance has an explicit feedback loop checkpoint ("rodar a simulação → ... ajustar o parâmetro específico apontado pela simulação → rodar de novo"). Not 5 because the architecture front has no equivalent validation checkpoint — the decision table is specified but not how to verify it.

4 / 5

Progressive Disclosure

A subject-to-file table maps each topic to its file with an explicit load-on-demand instruction ("carregar sob demanda pelo assunto da task, nao a arvore inteira"), each summary section carries a "Ver references/..." pointer, and all five referenced files exist in references/ with no nested references — one level deep, easy to navigate. (Cross-references to sibling skills like skills/67 are routing pointers, not content disclosure.)

5 / 5

Total

17

/

20

Passed

Description

95%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 a strong example: a concise third-person what-statement paired with an exhaustive, natural-language trigger list covering architecture, design review, and balance with synonyms and domain jargon. The only weakness is that the what-sentence names two verbs while the skill actually covers three fronts, leaving balance implied through triggers rather than stated.

DimensionReasoningScore

Specificity

"Projeta e revisa arquitetura e sistemas de jogos" names the domain with two concrete action verbs, and the trigger list explicitly names further actions ("balancear economia do jogo", "diagnosticar desbalanceamento"), giving several specific actions with a minor gap — balance modeling is absent from the what-sentence itself. Not 3 because coverage goes beyond 1-2 generic actions; not 5 because the core capability statement omits the balance/front third of the skill's scope.

4 / 5

Completeness

Explicitly answers both: what ("Projeta e revisa arquitetura e sistemas de jogos", in third person) and when ("Trigger em:" followed by 23 concrete trigger phrases). Matches the anchor example's structure of clear what + explicit trigger clause.

5 / 5

Trigger Term Quality

Comprehensive natural terms with synonyms and abbreviations: "GDD" + "game design document", "procedural content generation" + "PCG", plus "pity system", "loot table", "drop rate", "curva de progressao", "ECS vs OOP para jogo" — phrases a game designer would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear game-design niche with distinct triggers ("PvP balance", "pity system", "sistema de buff e debuff", "revisar mecanica de jogo") that are unlikely to fire for non-game skills. Even the architecture terms are game-qualified ("arquitetura de jogo", "ECS vs OOP para jogo"), keeping conflict risk minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

felvieira/claude-skills-fv

Path

skills/66-game-architecture-design/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.