test-helpers

Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.

Quality

72%

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/test-helpers/SKILL.md

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 content is highly actionable with executable, multi-engine helper code and a well-sequenced workflow including validation checkpoints. It is constrained by its monolithic inline structure — three full engine implementations live in SKILL.md with no bundle-file offloading — which limits both conciseness and progressive disclosure.

Suggestions

Move each engine's full helper templates into per-engine bundle files (e.g. references/godot-helpers.gd, references/unity-helpers.cs, references/unreal-helpers.h) and keep SKILL.md as an overview with one-level-deep links.

Trim the inline code to the minimal representative snippet per engine and reference the complete templates externally to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with substantial executable code, but ~390 lines is heavy: full inline code blocks for three engines (Godot, Unity, Unreal) and a system example could be condensed or referenced rather than reproduced verbatim.	2 / 3
Actionability	Provides fully executable, copy-paste-ready helper code for Godot/GDScript, Unity/C#, and Unreal/C++ plus a concrete combat-system example, with specific file paths and usage comments throughout.	3 / 3
Workflow Clarity	A clear six-step numbered sequence with explicit validation checkpoints: engine-not-configured guard (step 2), 'ask before writing' confirmation, 'never overwrite existing files' rule, and a COMPLETE verdict after writing.	3 / 3
Progressive Disclosure	The skill has no bundle files (references/, scripts/, assets/ absent), so the three full engine code blocks are inlined as a monolithic wall; content that would naturally split into per-engine reference files is kept inline with no one-level-deep navigation.	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-scoped, naming concrete outputs (assertion utilities, factory functions, mock objects) and a clear niche. It is held back by the absence of an explicit 'Use when...' trigger clause, which caps both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when scaffolding test helpers for a new system or when test files repeat setup/assertion boilerplate.'

Surface natural user phrasings (e.g. 'test boilerplate', 'test setup helpers', 'factory functions for tests') so the description matches how a user would actually request the skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects" — naming both the output artifact and its specific contents.	3 / 3
Completeness	Clearly answers 'what does this do' but the 'when' is only weakly implied ("Reduces boilerplate in new test files"); there is no explicit 'Use when...' trigger clause, capping completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Includes some natural terms ("test helper libraries", "test suite", "test files", "assertion utilities") but lacks the phrasings a user would actually say when requesting this (e.g. "test boilerplate", "factory functions for tests", "test helpers") and uses no 'Use when...' trigger clause.	2 / 3
Distinctiveness Conflict Risk	The niche is distinct — "engine-specific test helper libraries ... tailored to the project's systems" with a specific output path (tests/helpers/) — making it unlikely to trigger for other skills like /test-setup or /dev-story.	3 / 3
	Total	10 / 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/test-helpers/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.