CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

climb

Work out where a teammate, the champion, or a team is on the steps of AI adoption, and what to try next. Use when a champion wants to help someone move up a step.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/champion-kit/skills/climb/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.

This is a highly actionable, well-validated conversational skill: it prescribes exact questions, consent gates, output checks, and per-step coaching moves. Its weaknesses are redundancy and density in long paragraphs, and heavy inline validation detail that a reference file could absorb.

Suggestions

Remove the duplicated 'never use them to rank people' sentence (keep it in one place) and tighten the long 'How to ask' paragraph into short bullet rules.

Move the scout output contract (regex checks, name list, category list) into a references/ file and point to it from the body, keeping SKILL.md as a lean overview.

Reorder the 'Then' section so the step definitions appear before the transcript-counting protocol that depends on them.

DimensionReasoningScore

Conciseness

The body is mostly efficient plain-language instruction with little padding of concepts Claude already knows, but it repeats rules ('Steps describe how someone works, not how good they are, so never use them to rank people' appears twice) and several long paragraphs could be tightened. This fits 'mostly efficient but could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact AskUserQuestion option sets, explicit defaults, a per-step 'What's in the way / To reach the next step' playbook, copy-paste validation regexes, and a precise name list for counting tools. Specific guidance covers the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The flow is clearly sequenced (guided questions one at a time, transcript handling, step assessment, next move, follow-up) with strong checkpoints: consent questions before any read, and a validate-each-value / discard-the-whole-return feedback loop for scout output. It falls short of 5 because section ordering interleaves the transcript protocol before the step definitions it supports and a few transitions are implicit.

4 / 5

Progressive Disclosure

The body is well-headered ('## Start here', '## Then') but runs roughly 75 lines with the scout output contract, regex checks, and tool name list all inlined — content that plausibly belongs in a separate reference file. No bundle files exist and no references split the material out, fitting 'some structure but content that should be separate is inline'.

3 / 5

Total

15

/

20

Passed

Description

73%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, uses an appropriate imperative/third-person voice, and includes an explicit 'Use when...' trigger clause covering a well-defined niche. Its main limitations are modest action coverage and a 'when' clause that names only one of the audiences described in the 'what'.

Suggestions

Add one or two more concrete actions to the 'what' (e.g., 'name the guardrails to put in place first') to raise specificity.

Broaden the 'Use when' clause to cover the team case, e.g., 'Use when a champion or lead wants to help a teammate, themselves, or the team move up a step.'

DimensionReasoningScore

Specificity

The description names the domain ('steps of AI adoption') and two concrete actions ('Work out where... is on the steps' and 'what to try next'), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions, so it falls short of 4.

3 / 5

Completeness

It answers both 'what' (work out someone's step and what to try next) and 'when' ('Use when a champion wants to help someone move up a step') explicitly. The 'when' covers only the champion-helping-someone scenario while the 'what' also names the team, so it is not fully comprehensive as required for 5.

4 / 5

Trigger Term Quality

Natural keywords like 'AI adoption', 'steps', 'champion', 'teammate', and 'move up a step' give good coverage of what the intended user would say. Common synonyms such as 'maturity' or 'adoption level' are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear ('steps of AI adoption', 'champion', 'move up a step') with distinct trigger phrases, so it is unlikely to fire for unrelated skills. It matches the clear-niche anchor with minimal conflict risk.

5 / 5

Total

16

/

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

anthropics/claude-plugins-official

Path

plugins/champion-kit/skills/climb/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.