team-level

Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/team-level/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a highly actionable, well-sequenced orchestration playbook with explicit gates and error recovery; its only weakness is length and some repetition that could be tightened for token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured with no padding about concepts Claude already knows, but it is long and repetitive across the gated steps and re-describes delegation mechanics that could be tightened.	2 / 3
Actionability	It gives concrete, executable guidance throughout — specific subagent_type mappings, exact Task spawning instructions ('issue all three Task calls before waiting'), concrete file paths (design/levels/[level-name].md), and explicit AskUserQuestion option labels.	3 / 3
Workflow Clarity	The five-step sequence is clearly ordered with explicit 'Gate' checkpoints at each transition, validation steps (adjacent area dependency check, BLOCKING accessibility concern handling), and a full error-recovery feedback loop for blocked agents.	3 / 3
Progressive Disclosure	No bundle files are provided (references/scripts/assets are absent), and the body is well-organized into clearly signaled sections and phases, so for a self-contained skill the structure earns a top score.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 distinctive, clearly naming the orchestrated roles and the deliverable, but it lacks an explicit 'Use when...' trigger clause and has only partial coverage of natural user phrasings.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing a new level or area, creating a dungeon/zone, or building out a level design team workflow.'

Include common natural phrasings users would say, such as 'design a level', 'build a dungeon', or 'create a zone', to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and roles — 'Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation' enumerates the specific subagents and the concrete deliverable (complete area/level creation).	3 / 3
Completeness	It clearly states what the skill does (orchestrates the named team for area/level creation) but provides no explicit 'Use when...' trigger guidance, so the 'when' is only implied — capping completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	It uses domain terms a user might say ('level', 'area', 'level design') but omits common variations like 'design a level', 'build a dungeon', 'create a zone', or 'level design team', so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The very specific role roster and 'area/level creation' niche make it clearly distinguishable from other skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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-level/SKILL.md
Commit: 984023d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.