CtrlK
BlogDocsLog inGet started
Tessl Logo

soak-test

Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

60

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/soak-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable and well-sequenced with explicit validation and feedback loops, scoring strongly on actionability and workflow clarity. It loses points on conciseness and progressive disclosure because the large protocol template is embedded inline rather than referenced as a separate file.

Suggestions

Move the full protocol template (Section 5) into a references file such as references/protocol-template.md and keep SKILL.md as an overview that links to it, improving both conciseness and progressive disclosure.

Tighten the repeated checkpoint tables in the template — the T+[N] block already instructs to repeat per checkpoint, so avoid re-stating identical column structures multiple times.

DimensionReasoningScore

Conciseness

The ~275-line body is mostly efficient with no library-tutorial fluff, but embeds a large (~120-line) fill-in protocol template and repeats checkpoint structures, which could be tightened rather than earning every token its place.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: specific timed checkpoints, engine-specific commands (Godot Performance.get_monitor, Unity Memory Profiler path, Unreal 'stat memory'), and explicit alert thresholds, matching the fully-executable score-3 anchor.

3 / 3

Workflow Clarity

A clear numbered sequence (Parse → Load → Checkpoints → Generate → Document → Write) with explicit validation checkpoints (ask-before-writing approval gate) and a feedback loop (FAIL verdict → re-run /smoke-check), satisfying the score-3 anchor.

3 / 3

Progressive Disclosure

Well-organized into clear numbered sections, but the full protocol template is embedded inline rather than split into a one-level-deep reference file, and no bundle/reference files exist; content that could be separate is inline.

2 / 3

Total

10

/

12

Passed

Description

67%

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 specific and well-differentiated, naming concrete actions and a clear niche. Its main weakness is the 'when' guidance: it relies on phase names rather than explicit, natural 'Use when...' triggers a user would actually say.

Suggestions

Add an explicit 'Use when ...' clause with natural user trigger phrasing (e.g., 'Use when the user asks to run a soak/endurance test, check for memory leaks over long sessions, or validate stability during extended play').

Replace or supplement the phase-based 'Primarily used in Polish and Release phases' with trigger terms a user would naturally say, so it triggers on intent rather than project phase.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Generate a soak test protocol', 'Defines what to observe, measure, and log') and specific surfaced phenomena (slow leaks, fatigue effects, edge cases), matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers 'what' (generate protocol, observe/measure/log) but the 'when' is only a phase reference with no explicit 'Use when...' trigger clause, which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

Includes the natural term 'soak test' and 'extended/long play sessions', but the only trigger guidance is phase-based ('Primarily used in Polish and Release phases') rather than natural user utterances, missing common 'Use when...' phrasing.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche — soak/endurance test protocols for extended play — distinct from smoke checks and playtests, making conflict with other skills unlikely.

3 / 3

Total

10

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.