CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

next-step

Names the one next step: make a game, change it after play, grow it, or the next studio-mode step. Use when asked what to do next, or stuck.

Quality

77%

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/next-step/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-validated decision-tree skill with exact commands, status mappings, and output templates — its operating procedure is essentially executable as written. Its weaknesses are verbosity from dense qualification asides and a monolithic single-file structure that inlines branching logic (especially the minimal path) that would be better split into reference files.

Suggestions

Move the Step 4m minimal-path decision tree (~80 lines) into a references/ file (e.g. references/minimal-path.md) and keep a short routing summary in SKILL.md, enabling progressive disclosure.

Tighten the long parenthetical qualifications and multi-clause sentences (e.g. the 'When the person asks for a change...' bullet) into shorter atomic rules; the same conditions are often restated across steps.

Extract the status-mapping table and output shape templates into a reference file so the core routing logic in SKILL.md stays lean.

DimensionReasoningScore

Conciseness

The body is packed with project-specific procedural detail rather than concepts Claude already knows, but it is noticeably over-written: long parenthetical asides, repeated exceptions, and multi-clause sentences (e.g. the 'When the person asks for a change to a made game...' bullet) could be substantially tightened. It is mostly efficient but includes unnecessary qualification padding, matching anchor 3 rather than anchor 4's minor trims.

3 / 5

Actionability

Guidance is fully executable: exact commands with invocation constraints ('bash .claude/scripts/artifact-check.sh --phase [current-phase]' run 'from the project root, with the relative path'), a deterministic status-mapping table, a concrete marker regex for session-state parsing, and complete copy-ready output templates for both workflow shapes. This matches anchor 5's copy-paste-ready coverage of the common cases.

5 / 5

Workflow Clarity

Steps 1-9 are explicitly sequenced with deterministic validation (the artifact-check script), explicit status-to-report mappings, and user-confirmation checkpoints for MANUAL steps. However, Step 4m's deeply nested numbered sub-cases with further nested bullets make some flows hard to trace, a clarity gap that keeps it below anchor 5.

4 / 5

Progressive Disclosure

The skill is a single ~460-line monolith with no bundle files; all branching logic is inlined, including the ~80-line minimal-path decision tree in Step 4m that clearly belongs in a separate reference file. Section headers and explicit external doc paths provide some structure, matching anchor 3 ('content that should be separate is inline') rather than anchor 4's mostly-appropriate placement.

3 / 5

Total

15

/

20

Passed

Description

75%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 concise, well-formed description that clearly states both capability and trigger conditions using natural user phrasing. Its main weakness is thin trigger coverage (only two "when" scenarios) and one vaguely specified action ("the next studio-mode step").

Suggestions

Expand the 'Use when' clause with additional natural trigger variations users say in this situation (e.g. 'lost', 'not sure what to do', 'just finished X') to strengthen trigger coverage.

Replace or qualify the generic 'next studio-mode step' action with a concrete example of what such a step looks like, so every named action is equally specific.

Briefly distinguish this skill from the overlapping re-orientation skills (/project-stage-detect, /start) to reduce wrong-skill triggering.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("make a game, change it after play, grow it, or the next studio-mode step"), but "the next studio-mode step" is generic compared to the others, leaving minor gaps in coverage. It sits above anchor 3 (which covers only 1-2 actions) but below anchor 5's comprehensive, uniformly concrete action list.

4 / 5

Completeness

Both "what" ("Names the one next step: make a game, change it after play, grow it...") and "when" ("Use when asked what to do next, or stuck") are explicitly present. The when-clause covers only two trigger scenarios, so it is not the fully concrete, comprehensive trigger set of anchor 5.

4 / 5

Trigger Term Quality

"Use when asked what to do next, or stuck" supplies natural phrases users would actually say ("what to do next", "stuck"). Common variations like "lost", "where am I", or "what now" are missing, placing it just below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear orientation niche (naming the single next step in a game-development workflow), distinct from build/design skills. Minor overlap risk remains with the re-orientation skills it coexists with (/project-stage-detect, /start), keeping it below anchor 5's minimal-conflict profile.

4 / 5

Total

16

/

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/next-step/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.