CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-combat

Orchestrate the combat team — game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, qa-tester — design through implement and validate.

Quality

69%

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 ./.claude/skills/team-combat/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a strongly engineered orchestrator skill: literal agent prompts, return contracts, a per-phase artifact path table, gated transitions with mode-specific behavior, and an error-recovery protocol with real artifact verification. Its weaknesses are redundancy — the write-authorization exception is restated four times and several multi-paragraph justifications could be consolidated or moved to a reference file — and a comparatively vague Phase 4 (Integration) that lacks the concreteness of the other phases.

Suggestions

State the bounded write exception once (in File Write Protocol) and reference it elsewhere in one line; the current four restatements cost tokens without adding instruction.

Make Phase 4 concrete: name the integrating agent, the steps (apply engine notes, wire audio/VFX event hooks, expose tuning knobs in data), and how integration is verified before the gate.

Move the team.size collapse rationale and Collaboration-Protocol justification into a reference doc (e.g., references/write-authorization.md) and keep a two-line rule plus pointer in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious orchestration rules rather than concepts Claude already knows, but it is noticeably repeated: the bounded write exception is stated four times (return-contract paragraph, path table, 'Why this does not violate the Collaboration Protocol' blockquote, and File Write Protocol), the 'surfaced not silent' principle three times, and multi-paragraph meta-commentary about sibling skills ('team-release names ten and runs one...') is rationale, not instruction. It fits anchor 3 — mostly efficient but could be tightened — and is not padded enough for anchor 2.

3 / 5

Actionability

Most guidance is copy-paste ready: literal AskUserQuestion prompts with option labels, an exact return contract to append to every agent prompt, a concrete path table per phase, an executable Phase 0 hook command, and exact spawn types per role. The gap is Phase 4 Integration — 'Wire together gameplay code, AI, VFX, and audio' and 'Ensure all tuning knobs are exposed' are high-level direction with no executor, steps, or verification method named — which keeps it below anchor 5.

4 / 5

Workflow Clarity

Six phases are explicitly sequenced, each with named outputs and destination paths; every transition has an AskUserQuestion decision point with defined behavior per automation mode; validation is explicit ('a named artifact that is not on disk is a failed phase') with a feedback loop (resume the agent naming the unmet contract); skipped checks must be recorded ('Engine validation: NOT ASSESSED'); and terminal verdicts (COMPLETE / NEEDS WORK / BLOCKED) are defined with conditions. This matches the anchor-5 example: clear sequence, explicit validation, error-recovery feedback loops.

5 / 5

Progressive Disclosure

Structure is good: clear section headers, a path table, and bulky detail correctly offloaded one level deep to clearly-signaled project docs ('Full procedure: .claude/docs/error-recovery-protocol.md', '.claude/docs/automation-modes.md', config-resolution and GDD template docs) — no nested reference chains. It misses anchor 5 because there is no bundle references/ directory at all and a meaningful share of inline content (the team.size rationale, the bounded-exception justification prose) is the kind of material that could live in a reference file to keep SKILL.md lean.

4 / 5

Total

16

/

20

Passed

Description

53%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 claims a clear, well-differentiated niche — orchestrating a named combat development team — and lists the team roles concretely. However, it omits any 'use when' trigger guidance, so discoverability rests almost entirely on the single word "combat", and the action verbs (design/implement/validate) are generic rather than concrete. Adding an explicit trigger clause covering combat features, fighting mechanics, weapons, and enemy AI would lift both completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user asks to design or implement a combat feature — melee or ranged weapons, parry/dodge mechanics, enemy AI behaviors, hit feedback (VFX/audio) — end to end.'

Replace the generic verb chain 'design through implement and validate' with concrete deliverables (design document, architecture sketch, implemented mechanic, test cases and bug reports) to sharpen specificity.

Include natural synonyms users would say (fighting system, battle mechanics, weapons, NPC AI, hit reactions) so the skill triggers on phrasings that never use the word 'combat'.

DimensionReasoningScore

Specificity

The description names the domain concretely ("Orchestrate the combat team") and enumerates six specific roles ("game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, qa-tester"), but the actions reduce to the generic verb chain "design through implement and validate" with no objects or concrete deliverables. It sits above anchor 2 (domain named, minimal actions) but the actions themselves are not comprehensive or specific enough for anchor 4.

3 / 5

Completeness

The 'what' is present and reasonably clear (orchestrate a named team through design, implementation, and validation), but there is no 'when' — no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

"combat" is a strong natural keyword and the role names (game-designer, ai-programmer, sound-designer) add some trigger surface, but common variations users would actually say are missing — "fighting system", "weapons", "melee", "ranged", "enemy AI", "VFX", "game feature". This matches anchor 3: some relevant keywords, missing common variations and synonyms.

3 / 5

Distinctiveness Conflict Risk

"combat" carves out a clear niche that distinguishes it from sibling orchestration skills (team-narrative, team-level, team-release, team-polish are referenced in the body), giving minimal conflict risk on combat queries. It falls short of anchor 5 only because the trigger surface is a single discriminator word, leaving minor overlap risk with closely related skills whose scopes touch combat-adjacent work (VFX/audio polish, combat formula balancing).

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/team-combat/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.