Soak Test

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Soak Test" for me. The skill itself generates the observation protocol and analysis harness for a soak test — an extended play session of 30 minutes, 1, 2 or 4 hours, focused on memory, stability, balance or all three — designed to surface slow memory leaks, performance drift, state accumulation bugs, fun fatigue and content exhaustion. The human does the actual playing: the skill never attempts to run a soak test automatically. It loads context (engine and performance budgets from project.yaml, falling back to .claude/docs/technical-preferences.md; the intended session length and core loop from design/gdd/game-concept.md or the one-page design/game-brief.md; the most recent playtest and QA plan under production/qa/), defines timed checkpoints for the chosen duration, and generates the protocol document: pre-session setup, a T+0 baseline table, a checkpoint log (memory and stability items with engine-specific monitoring guidance for Godot's Debugger Monitors, Unity's Memory Profiler and Unreal's stat memory — names the file flags as NOT SOURCEABLE from the template's engine reference docs, to confirm in the user's own editor), balance and fatigue items, and a post-session analysis with verdict PASS, PASS WITH CONCERNS, NOT ASSESSED or FAIL. A short or unexecuted soak cannot return PASS: a protocol document is not a result. It presents the protocol summary, then asks "May I write this soak test protocol to production/qa/soak-test-[date]-[duration].md?" and writes only after approval. It resolves the automation and workflow modes by running the template's hooks/yaml-helper.sh, outside this skill's folder. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/soak-test/ folder at the pinned commit: 1 file in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/soak-test/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 cd1ad9ab08b98b978f7dc5188822597b602e4f8170a811f0ca2ccab2f7f96122 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file: SKILL.md only. Nothing in the folder is a program; it is instructions the agent follows at use time. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is audited, read or modified. - Integrated-system reality, from the file: at use time the skill runs the template's hooks/yaml-helper.sh to resolve the automation and workflow modes, follows .claude/docs/automation-modes.md, and reads my project's project.yaml, design/gdd/game-concept.md (or design/game-brief.md) and the latest files under production/qa/ — files that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time its only persistent output is the protocol file in production/qa/, written only after its "May I write" ask; the soak itself is played and logged by a human, and the skill runs no game, test or engine command. No third-party service, account or credential is named in the file. - Do not generate a soak protocol, do not run any play session or template hook, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole soak-test folder into the agent's skills directory, in a folder named exactly "soak-test", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: soak-test), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it resolves its modes through the template's yaml-helper hook and reads the template's project.yaml, design and production/qa/ files), and that at use time it only generates a protocol for a human to play, writing that protocol only after asking). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.