CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brainstorm

Guides the user through finding and choosing a game concept. Use when the user wants game ideas, a new concept, a game jam idea, or to explore other directions, including dropping the current idea and starting over.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary instruction-only skill body: concrete paths, commands, verbatim user-facing strings, and explicit confirmation/re-ask checkpoints make the workflow fully executable, and the single conditional reference file is textbook progressive disclosure. The only weakness is mild — a handful of dense rationale clauses that could be trimmed for token efficiency.

DimensionReasoningScore

Conciseness

The body is dense, prescriptive instruction with no explanation of concepts Claude already knows (no "what a design brief is" padding) and every section carrying rules (e.g. "More than 7 items: push back", "Keep stays empty: it fills after they play"). A few rationale clauses could be trimmed ("a typed /brainstorm runs its turn on this skill's model, and the build must run on the session's"), matching 'Efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place ideal of a 5.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact paths ("design/game-brief.md", ".claude/docs/templates/game-brief.md", "project.yaml"), exact follow-on commands (/prototype, /create-stories, /dev-story), copy-paste-ready user-facing strings ("Type `/prototype <the picked concept, in their words>` to build it..."; "Verdict: COMPLETE — game brief written; next stop is code."), and concrete field-by-field brief instructions with marking rules (*(guessed)*, *(provisional)*). This matches 'Fully executable; copy-paste ready... specific examples cover the common cases'.

5 / 5

Workflow Clarity

The Lean Brief flow is an explicitly numbered 4-step sequence with decision branches (engine set vs. absent/empty/web) and explicit validation checkpoints: "Write only on an explicit yes to this question; agreeing to a cut or saying 'go on' is not a yes", the full-brief review before writing, and feedback loops for recovery ("A skipped or dismissed question is not an answer: ask again"; "On a revision, change the named field, show it before and after, and ask again"). This matches 'Clear sequence with explicit validation steps; feedback loops for error recovery'. The operation is conversational, not destructive/batch, so no cap applies.

5 / 5

Progressive Disclosure

The bundle structure is used well: the common minimal path is fully inline, and the full flow is delegated to exactly one real, verified, one-level-deep reference ("read `references/full-concept.md` and follow it") that is conditionally loaded ("do not load references/full-concept.md" at minimal tier), with a clear tier dispatch up front. This matches 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

19

/

20

Passed

Description

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

A strong description with an explicit, well-phrased 'Use when' trigger clause covering natural user language including edge cases like abandoning the current idea. The 'what' side is thinner — it names only the find-and-choose action and misses that the skill also produces a written brief/design, which keeps specificity at the middle anchor.

Suggestions

Add 1-2 more concrete outcome actions to the 'what' half, e.g. '...and writes a one-page game brief or full concept document the next step builds from', to lift specificity from naming the domain to listing several specific actions.

Consider adding 'brainstorm' or 'come up with a game idea' as trigger synonyms, since users may phrase the request that way.

DimensionReasoningScore

Specificity

"Guides the user through finding and choosing a game concept" names the domain and the concrete action pair (finding, choosing), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — it omits downstream actions the skill actually performs (e.g., writing a design brief). Not a 2: the action is more concrete than 'Processes PDF files'; not a 4: coverage is not 'several specific actions'.

3 / 5

Completeness

It explicitly answers both: what — "Guides the user through finding and choosing a game concept"; when — "Use when the user wants game ideas, a new concept, a game jam idea, or to explore other directions". This matches the anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases'; a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

"game ideas, a new concept, a game jam idea, or to explore other directions, including dropping the current idea and starting over" gives good natural-phrase coverage a user would actually say. Not a 5 because common variations like "brainstorm", "come up with a game", or "pitch" are absent; clearly above 3 since multiple relevant natural terms are present.

4 / 5

Distinctiveness Conflict Risk

"game concept", "game jam idea", "dropping the current idea and starting over" carve out a clear ideation niche with distinct triggers and minimal conflict risk, matching the anchor 'Clear niche with distinct triggers; minimal conflict risk'. Not a 4: no meaningful overlap with adjacent build/design skills is implied by these triggers.

5 / 5

Total

17

/

20

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.

Validation — 14 / 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

Path

.claude/skills/brainstorm/SKILL.md

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.