CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

help

Old name of /next-step. Prints one line, then runs /next-step.

Quality

79%

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

Quality

Content

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

The body is an exemplary minimal redirect skill: exact output text, exact delegation instruction with argument passthrough, explicit ordering, and a scope guard, with zero padding. It fully leverages the simple-skill exceptions in the rubric.

DimensionReasoningScore

Conciseness

Thirteen lean lines: one sentence of rename context ("Most AI tools keep /help for a command of their own..."), the exact line to print, the delegation instruction, and a closing scope guard. Every token earns its place and nothing explains concepts Claude already knows.

5 / 5

Actionability

The guidance is fully executable: the output line is given verbatim ("/help is now /next-step. Running /next-step."), the tool to call is named ("Run the next-step skill with the Skill tool"), and argument passthrough is specified precisely ("passing these arguments unchanged (none, if this is empty): $ARGUMENTS"). Per the scoring notes, an instruction-only skill with this specificity earns full marks.

5 / 5

Workflow Clarity

Two numbered steps with an explicit ordering constraint ("as the first line of your reply") and a scope guard ("Do nothing else here: /next-step does the work"). The simple-skill exception applies: the single action is unambiguous, and no destructive or batch operations require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well organized (header, one sentence of context, numbered steps, scope guard); no bundle files exist. Per the guideline, this earns a 5 with just well-organized sections.

5 / 5

Total

20

/

20

Passed

Description

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

The description is concise and accurately states the skill's two concrete behaviors, with a tightly scoped niche. Its main weaknesses are the complete absence of its own command name "/help" as a trigger term and any "Use when..." guidance, leaving the "when" only weakly implied.

Suggestions

Include the "/help" command name in the description itself (e.g., "Old name of /next-step, kept for the /help command") so the primary user-facing trigger term is present.

Add an explicit trigger clause such as "Use when the user types /help" to satisfy the "when" half of completeness.

Briefly state what the user gets (e.g., "...runs /next-step to suggest what to work on next") so the redirect target's purpose is understandable from the description alone.

DimensionReasoningScore

Specificity

"Prints one line, then runs /next-step" names two concrete actions that fully cover this redirect skill's behavior. Anchor 3's "not comprehensive" defect does not apply, but "several specific actions" (anchor 4) overstates a two-action description, so it sits just at 4.

4 / 5

Completeness

The "what" is clear (prints one line, then delegates to /next-step), but there is no "Use when..." clause; the "when" is only weakly implied by "Old name of /next-step". Per the guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

The only keyword is "/next-step" (mentioned twice); the description never names "/help", the very command that invokes this skill and the phrase a user would naturally type. This matches "one or two keywords; missing the natural phrases users say" rather than anchor 3, which presumes a relevant keyword set with only synonyms missing.

2 / 5

Distinctiveness Conflict Risk

"Old name of /next-step" carves out a clear niche tied to one specific command, so overlap risk is minor. It falls short of anchor 5 because distinctiveness rests on naming the target command rather than explicit distinct trigger phrases.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/help/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.