team-narrative

Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.

Quality

72%

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-narrative/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 body is a well-structured, actionable orchestration pipeline with clear sequencing, validation gates, and error-recovery feedback loops; its main weakness is redundant duplication of the role descriptions across two sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and free of concept-explanation filler, but the six role descriptions are duplicated nearly verbatim across 'Team Composition' (lines 33-38) and 'How to Delegate' (lines 43-48), so it 'includes some unnecessary explanation or could be tightened'.	2 / 3
Actionability	Provides concrete executable guidance: named subagent_types, per-phase deliverables, numeric constraints ('all lines under 120 characters', 'German/Finnish typically +30%'), and explicit AskUserQuestion options, fully matching the 'fully executable / copy-paste ready' anchor for an instruction-only skill.	3 / 3
Workflow Clarity	A clearly sequenced Phase 0-5 pipeline with explicit validation checkpoints (Decision-Point approval gates, Phase 4 consistency review, Phase 5 polish) and a feedback-loop Error Recovery Protocol, matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the body is organized into well-signaled sections (phases, team, delegation, error recovery, output) with no nested references, satisfying the 'well-organized sections' criterion for a self-contained orchestration skill.	3 / 3
	Total	11 / 12 Passed

Description

60%

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 clearly states what the skill orchestrates and names concrete deliverables, but it lacks an explicit 'Use when...' trigger clause and uses a somewhat narrow vocabulary that could overlap with sibling game-dev skills.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating or revising game story content, dialogue, lore, cutscenes, or narrative-driven levels.'

Broaden trigger vocabulary to include natural user terms like 'dialogue', 'cutscene', 'cinematic', 'quest', and 'faction lore'.

Distinguish the orchestrator role from sibling single-purpose skills (e.g. 'coordinates the narrative team' rather than doing level design directly) to reduce conflict risk.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions across distinct domains — 'coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant domain terms ('story content', 'world lore', 'level design', 'narrative') but omits common variations a user would naturally say such as 'dialogue', 'cutscene', 'cinematic', 'quest', or 'faction', so it lands at 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	It is a distinct orchestrator niche, but its trigger terms ('level design', 'world lore') overlap with plausible sibling single-purpose skills, so it 'could still overlap with similar skills' rather than being unmistakably distinct.	2 / 3
	Total	9 / 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-narrative/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.