CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

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 ./.gemini/skills/claude-coach/SKILL.md

The canonical home for this skill is claude-coach in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured and highly actionable with concrete templates and explicit decision rules, but it is held back by redundancy (the frontmatter content is restated in several bottom sections) and by references to bundle files that are not actually present.

Suggestions

Remove the redundant "Name", "Description", "Features", and "Usage" sections at the bottom, which restate the frontmatter and the "When to invoke" trigger list already present above.

Either add the missing bundle files (references/cheat-codes.md, references/coaching-rules.md, scripts/cheat_code_filter.py, scripts/prompt_rater.py, scripts/coach_tip_classifier.py) or delete the references to them so navigation does not point to non-existent files.

Define the "5-gate decision tree" and "Tier 1–5" ranking that are referenced in the Features section, or relabel Rule 5's trigger/non-trigger bullet lists to match the terminology actually used.

DimensionReasoningScore

Conciseness

Mostly efficient and free of explanations of concepts Claude already knows, but it is noticeably redundant: the frontmatter description and trigger lists are restated in the body's "Description", "Name", "Features", and "Usage" sections, and the activation trigger phrases appear twice ("When to invoke" and "Usage").

3 / 5

Actionability

Provides copy-paste-ready format templates (the ⚡ tip block and the prompt-rating block) and explicit trigger/non-trigger conditions with concrete examples, but references a "5-gate decision tree" and a "Tier 1–5" ranking as if they are defined artifacts when neither is actually presented as such in the body.

4 / 5

Workflow Clarity

The first-activation flow is a clearly sequenced 3-step process with conditional skip-logic and the ongoing mode is governed by 7 ordered rules; no destructive or batch operation is present so the validation cap does not apply, but it lacks the explicit error-recovery feedback loops of the 5 anchor.

4 / 5

Progressive Disclosure

The in-body structure is well-organized with a clearly signaled References section, but the referenced bundle files (references/cheat-codes.md, references/coaching-rules.md, and three scripts) do not exist on disk, so the one-level-deep navigation leads to missing files and the progressive-disclosure promise is broken.

3 / 5

Total

14

/

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, explicit description that clearly states what the skill does and when to trigger it with a rich set of natural trigger phrases. The only weakness is minor overlap risk from the broad passive-coaching activation and the generic "what can Claude do" trigger.

DimensionReasoningScore

Specificity

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 abstraction, but stops short of the fully comprehensive, crisply concrete action list of the 5 anchor.

4 / 5

Completeness

Explicitly answers both what (coach that teaches, detects missed opportunities, surfaces one tip) and when ("Use this skill the FIRST time a user asks..." plus "on EVERY subsequent turn") with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural phrases users 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"), matching the 5 anchor for natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

The Claude-coaching framing is a clear niche with distinct triggers, but the passive every-turn activation and the broad "what can Claude do" trigger create minor overlap risk with general capability questions, fitting the 4 rather than 5 anchor.

4 / 5

Total

18

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

14

/

16

Passed

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