playtest-report

Structured playtest report template, or turn existing playtest notes into structured feedback.

Quality

77%

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/playtest-report/SKILL.md

Quality

Content

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

The body is a strong example of skill writing: fully concrete guidance with explicit checkpoints, fallback behavior for missing inputs, and permission gating before the write. Its only weaknesses are minor — a marginally trimmable template section and no bundle split for the large report template.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes competence (e.g. "Resolved above — use as-is; `--review` overrides `review_mode` for this run"), but the ~60-line inlined template and a few explanatory asides (e.g. "A director gate handed silence about pillars will invent them") could be marginally trimmed.	4 / 5
Actionability	Fully executable throughout: a verbatim report template, exact user-facing phrases ("Verdict: COMPLETE — blank template output; nothing saved"), exact routing commands (/propagate-design-change, /balance-check, /bug-report), and an exact save path pattern.	5 / 5
Workflow Clarity	The phased sequence (1, 2A/2B, 3, 3b, 4, 5) is explicit with validation checkpoints: mode fallback via AskUserQuestion, a review-mode gate before spawning the director, conditional handling for missing game-concept.md, and a permission ask before any write.	5 / 5
Progressive Disclosure	Clear phase headers and clearly signaled external references (.claude/docs/director-gates.md, automation-modes.md) with a deliberate one-level rule ("the spawned agent reads its own gate file; do not read it in the parent session"), but the full report template is inlined rather than split into a bundle file — a minor organization gap.	4 / 5
	Total	18 / 20 Passed

Description

57%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 concise and distinctive, clearly communicating a niche capability, but it lacks any "when to use" trigger guidance and only partially enumerates what the skill does. Adding a use-when clause with natural trigger terms would substantially raise both completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions a playtest, playtesting session, playtester feedback, or wants playtest notes turned into a structured report."

Broaden the stated capabilities beyond template/structuring — e.g. mention categorizing findings (design changes, balance, bugs, polish) and creative-director review.

Include natural synonyms such as "game testing" or "playtester notes" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Structured playtest report template, or turn existing playtest notes into structured feedback" names the domain and two concrete actions (generate template, structure existing notes), but coverage is not comprehensive — no mention of categorizing findings, routing, or director review.	3 / 5
Completeness	The "what" is clear (template generation or note structuring) but there is no "Use when..." or equivalent trigger clause, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"playtest", "playtest notes", and "structured feedback" are natural terms, but common variations and synonyms (e.g. "game testing", "playtester", "QA session") are missing.	3 / 5
Distinctiveness Conflict Risk	"playtest" is a sharp, domain-specific term with a clear niche; it is unlikely to trigger for the wrong skill and has minimal overlap risk.	5 / 5
	Total	14 / 20 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: b21fa0f

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.