playtest-report

Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%

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

A well-structured, highly actionable skill with a clear phased workflow, an explicit review gate with feedback handling, and clean one-level references. The only notable weakness is minor duplication of the review-mode logic across Phase 1 and Phase 3b.

Suggestions

Resolve the review mode once in Phase 1 and have Phase 3b reference that resolved value rather than re-stating the full/lean/solo skip rules, removing the duplication.

Reference `.claude/docs/director-gates.md` once (e.g., in Phase 1) and point back to it from Phase 3b instead of citing it again.

Dimension	Reasoning	Score
Conciseness	Prose is lean and assumes competence with no concept-teaching, but the review-mode resolution is stated in Phase 1 and re-derived per-mode in Phase 3b, and `.claude/docs/director-gates.md` is referenced twice — it could be tightened, matching the "mostly efficient but could be tightened" anchor.	2 / 3
Actionability	Provides exact slash commands, concrete file paths, a named gate (CD-PLAYTEST), and a full copy-paste report template — fully executable, specific guidance with no vague direction.	3 / 3
Workflow Clarity	Phases 1–5 are clearly sequenced, with the CD-PLAYTEST gate as an explicit validation checkpoint carrying an APPROVE/CONCERNS/REJECT feedback loop and a permission check before writing the report file.	3 / 3
Progressive Disclosure	No bundle files exist; the body is self-contained and well-organized into labeled phases, with only one-level-deep, clearly signaled references (director-gates.md, review-mode.txt, game-concept.md) and no nested indirection.	3 / 3
	Total	11 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities and an explicit use-trigger, occupying a distinct niche. Its main weakness is trigger-term breadth: every keyword is a variant of "playtest" with no synonyms a user might naturally say.

Suggestions

Broaden trigger terms to include natural variations like "playtesting", "playtester feedback", or "game testing notes" so the skill surfaces for more phrasings.

Consider adding a one-line scenario trigger (e.g., "Use after a playtesting session or when organizing QA feedback") to complement the purpose-style "Use this to" clause.

Dimension	Reasoning	Score
Specificity	Names two concrete actions — "Generates a structured playtest report template" and "analyzes existing playtest notes into a structured format" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly states what it does (generate template / analyze notes into structured format) and gives an explicit "Use this to" trigger for when to use it, satisfying both the what and the when.	3 / 3
Trigger Term Quality	Includes natural terms ("playtest report", "playtest notes", "playtest feedback") but all are variants of "playtest"; common variations a user might say ("playtesting", "playtester feedback", "game testing", "QA notes") are missing, fitting the "some relevant keywords but missing common variations" anchor.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (playtest reports) with distinct triggers unlikely to fire for unrelated skills; written in third person ("Generates", "analyzes"), so no voice penalty applies.	3 / 3
	Total	11 / 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/playtest-report/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.