How do I install the Playtest Report skill?

Run npx skillmds add majiayu000/playtest-report in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Playtest Report safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Playtest Report?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Playtest Report free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Playtest Report?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Playtest Report by majiayu000 — Agent Skill

Name: Playtest Report
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

When invoked with new, generate this template:

# Playtest Report

## Session Info
- **Date**: [Date]
- **Build**: [Version/Commit]
- **Duration**: [Time played]
- **Tester**: [Name/ID]
- **Platform**: [PC/Console/Mobile]
- **Input Method**: [KB+M / Gamepad / Touch]
- **Session Type**: [First time / Returning / Targeted test]

## Test Focus
[What specific features or flows were being tested]

## First Impressions (First 5 minutes)
- **Understood the goal?** [Yes/No/Partially]
- **Understood the controls?** [Yes/No/Partially]
- **Emotional response**: [Engaged/Confused/Bored/Frustrated/Excited]
- **Notes**: [Observations]

## Gameplay Flow
### What worked well
- [Observation 1]
- [Observation 2]

### Pain points
- [Issue 1 -- Severity: High/Medium/Low]
- [Issue 2 -- Severity: High/Medium/Low]

### Confusion points
- [Where the player was confused and why]

### Moments of delight
- [What surprised or pleased the player]

## Bugs Encountered
| # | Description | Severity | Reproducible |
|---|-------------|----------|-------------|

## Feature-Specific Feedback
### [Feature 1]
- **Understood purpose?** [Yes/No]
- **Found engaging?** [Yes/No]
- **Suggestions**: [Tester suggestions]

## Quantitative Data (if available)
- **Deaths**: [Count and locations]
- **Time per area**: [Breakdown]
- **Items used**: [What and when]
- **Features discovered vs missed**: [List]

## Overall Assessment
- **Would play again?** [Yes/No/Maybe]
- **Difficulty**: [Too Easy / Just Right / Too Hard]
- **Pacing**: [Too Slow / Good / Too Fast]
- **Session length preference**: [Shorter / Good / Longer]

## Top 3 Priorities from this session
1. [Most important finding]
2. [Second priority]
3. [Third priority]

When invoked with analyze, read the raw notes, cross-reference with existing design documents, and fill in the template above with structured findings. Flag any playtest observations that conflict with design intent.

---name: playtest-reportdescription: Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.--- When invoked with `new`, generate this template: ```markdown # Playtest Report ## Session Info - **Date**: [Date] - **Build**: [Version/Commit] - **Duration**: [Time played] - **Tester**: [Name/ID] - **Platform**: [PC/Console/Mobile] - **Input Method**: [KB+M / Gamepad / Touch] - **Session Type**: [First time / Returning / Targeted test] ## Test Focus [What specific features or flows were being tested] ## First Impressions (First 5 minutes) - **Understood the goal?** [Yes/No/Partially] - **Understood the controls?** [Yes/No/Partially] - **Emotional response**: [Engaged/Confused/Bored/Frustrated/Excited] - **Notes**: [Observations] ## Gameplay Flow ### What worked well - [Observation 1] - [Observation 2] ### Pain points - [Issue 1 -- Severity: High/Medium/Low] - [Issue 2 -- Severity: High/Medium/Low] ### Confusion points - [Where the player was confused and why] ### Moments of delight - [What surprised or pleased the player] ## Bugs Encountered | # | Description | Severity | Reproducible | |---|-------------|----------|-------------| ## Feature-Specific Feedback ### [Feature 1] - **Understood purpose?** [Yes/No] - **Found engaging?** [Yes/No] - **Suggestions**: [Tester suggestions] ## Quantitative Data (if available) - **Deaths**: [Count and locations] - **Time per area**: [Breakdown] - **Items used**: [What and when] - **Features discovered vs missed**: [List] ## Overall Assessment - **Would play again?** [Yes/No/Maybe] - **Difficulty**: [Too Easy / Just Right / Too Hard] - **Pacing**: [Too Slow / Good / Too Fast] - **Session length preference**: [Shorter / Good / Longer] ## Top 3 Priorities from this session 1. [Most important finding] 2. [Second priority] 3. [Third priority] ``` When invoked with `analyze`, read the raw notes, cross-reference with existing design documents, and fill in the template above with structured findings. Flag any playtest observations that conflict with design intent.

Frequently asked questions