CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claude-coach

Personal coach that teaches users to become Claude power users. Use this skill the FIRST time a user asks to "learn Claude", "be a power user", "coach me", "teach me Claude tricks", "what can Claude do", "make me better at prompting", or any variation. After activation, also use it on EVERY subsequent turn to detect missed optimization opportunities (vague prompts, ignored capabilities, manual work Claude could automate) and surface a single power-user tip. Trigger generously — most users do not know what they do not know, so err on the side of coaching.

65

Quality

82%

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

67%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 operational core (activation flow, coaching rules, tip and rating templates) is concrete and well-sequenced, with real, clearly signaled one-level-deep bundle files. The main defects are the duplicated README-style tail sections that restate the frontmatter and trigger list, and script/feature mentions (5-gate decision tree, 'stop with the tips') that lack operational detail in the body proper.

Suggestions

Delete the trailing '## Name', '## Description', '## Usage', and '## Features' sections that duplicate the frontmatter and the 'When to invoke this skill' section, keeping at most the '## Examples' and '## Scripts' material.

Add a rule in the 'Ongoing coaching mode' section for the 'stop with the tips' turn-off that the Features section promises, and briefly state how the rules map to the 5-gate decision tree in references/coaching-rules.md.

For each script in '## Scripts', give a one-line invocation example (e.g. how and when to run prompt_rater.py during a 'rate that prompt' request) so the bundle is actually reachable.

DimensionReasoningScore

Conciseness

The core coaching rules are lean and imperative, but the trailing '## Name', '## Description', '## Features', '## Usage', and '## Examples' sections (~60 lines) largely duplicate the YAML frontmatter and the earlier 'When to invoke this skill' section. This is more than the 'minor instances of over-explanation' of anchor 4, fitting anchor 3: mostly efficient but includes unnecessary content that could be trimmed.

3 / 5

Actionability

The body gives copy-paste-ready templates for the tip format, prompt rating, and glossary entry format, plus an exact first-activation question and sequence. It falls short of anchor 5 because the three scripts are listed with no invocation commands, and behaviors like 'stops coaching when the user says stop with the tips' and the '5-gate decision tree' are mentioned only in the duplicated tail without operational detail.

4 / 5

Workflow Clarity

The first-activation flow is clearly sequenced (Step 1 to Step 3) with an explicit skip condition ('If the user already mentioned their use case... skip this question'), and ongoing coaching rules are ordered with do/don't trigger lists. Anchor 5 is not reached because the connection between the rules and the deferred 5-gate decision tree in references/coaching-rules.md is not spelled out, and the user-initiated turn-off ('stop with the tips') is absent from the rule set.

4 / 5

Progressive Disclosure

Both references exist and are one level deep with clear read conditions ('Read on first activation and consult when surfacing tips', 'Read if uncertain whether a moment is coachable'), and the three scripts are listed with one-line purposes. Minor gaps keep it from anchor 5: the scripts section gives no usage/navigation guidance, and the duplicated tail sections blur the overview's focus.

4 / 5

Total

15

/

20

Passed

Description

91%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: third-person voice, explicit first-activation and ongoing-turn trigger guidance, and a rich set of natural user phrasings. The only softness is that the capability list omits a few of the skill's features (glossary delivery, prompt rating, progress check), keeping specificity and distinctiveness at 4 rather than 5.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('teaches users to become Claude power users', 'detect missed optimization opportunities (vague prompts, ignored capabilities, manual work Claude could automate)', 'surface a single power-user tip'), with minor gaps such as no mention of the glossary delivery, prompt rating, or progress check. It is above anchor 3 (only 1-2 concrete actions) but not the comprehensive coverage of anchor 5.

4 / 5

Completeness

It explicitly answers both 'what' (teaches users to become power users; detects missed optimization opportunities; surfaces a single tip) and 'when' ('Use this skill the FIRST time a user asks to... ' plus 'After activation, also use it on EVERY subsequent turn'). This clearly matches the anchor for explicitly answering both what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes comprehensive natural trigger phrases with synonyms a user would actually say: '"learn Claude"', '"be a power user"', '"coach me"', '"teach me Claude tricks"', '"what can Claude do"', '"make me better at prompting"', 'or any variation'. This matches the anchor for comprehensive coverage of natural terms including synonyms.

5 / 5

Distinctiveness Conflict Risk

The coaching niche ('Claude power user', 'coach me') is mostly distinct from other skills, but 'use it on EVERY subsequent turn' after activation and the trigger 'what can Claude do' carry minor overlap risk with general capability questions. It sits between anchor 4 (minor overlap risk) and anchor 5 (minimal conflict risk).

4 / 5

Total

18

/

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

alirezarezvani/claude-skills

Path

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