CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onboard

Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.

Quality

69%

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 ./templates/skills/impeccable/onboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 a well-organized catalog of onboarding design patterns, but much of it restates UX knowledge Claude already possesses and repeats itself (empty states covered twice). It lacks executable validation steps and keeps all pattern detail inline instead of splitting it into reference files.

Suggestions

Trim or remove sections that restate common UX knowledge (tooltip dismissal behavior, modal focus-trap basics, the localStorage snippet) and eliminate the duplicated empty-state guidance between "Feature Discovery & Adoption" and "Empty State Design".

Replace abstract principles with concrete, checkable guidance: example welcome-screen copy, a tour-step specification, or a definition-of-done checklist Claude can verify against before finishing.

Move the pattern catalogs (guided tours, interactive tutorials, empty-state types, implementation libraries) into references/ files and keep SKILL.md as a concise overview that links to them one level deep.

DimensionReasoningScore

Conciseness

Much of the body teaches UX knowledge Claude already has (tooltip patterns, "Focus trap, backdrop, ESC to close", trivial localStorage snippets) and the empty-state guidance is repeated in both "Feature Discovery & Adoption" and "Empty State Design". This matches the "several unnecessary explanations or padded sections" anchor rather than the mostly-efficient anchor 3.

2 / 5

Actionability

There are concrete anchors (empty-state copy example, named libraries like Intro.js/Shepherd.js, a metrics checklist), but most guidance is abstract principle ("Teach 20% that delivers 80% of value", "Respect user intelligence") without example deliverables. This sits between minimal-hints (2) and mostly-executable guidance (4).

3 / 5

Workflow Clarity

A sequence exists (mandatory preparation, Assess Onboarding Needs 1-3, design patterns, verify), but checkpoints are missing or non-executable — "Verify Onboarding Quality: Test with real users" is something Claude cannot run, so the sequence has no executable validation step. This matches anchor 3; the destructive/batch cap does not apply to this design-only skill.

3 / 5

Progressive Disclosure

A single ~240-line monolithic file with no references/ split — pattern catalogs (tours, tutorials, empty-state types) that belong in separate files are inlined. Clear one-level headers keep it above anchor 2, but with no bundle files and heavy inlining it cannot reach 4.

3 / 5

Total

11

/

20

Passed

Description

83%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: it states concrete capabilities in third person and pairs them with an explicit, well-phrased "Use when..." trigger clause covering multiple natural synonyms. Minor gaps in trigger coverage (sign-up, welcome, tour) keep trigger quality and distinctiveness just below top marks.

DimensionReasoningScore

Specificity

"Designs and improves onboarding flows, empty states, and first-run experiences" names the domain plus several concrete capabilities. It stays below 5 because it omits deliverables like guided tours, tooltips, or checklists, and above 3 because it goes beyond 1-2 generic actions.

4 / 5

Completeness

It explicitly answers both questions: the "what" ("Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly") and the "when" ("Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows").

5 / 5

Trigger Term Quality

"onboarding, first-time users, empty states, activation, getting started, or new user flows" gives good natural-phrase coverage with synonyms. Not 5 because common user phrasings like "sign-up flow", "welcome screen", and "product tour" are missing.

4 / 5

Distinctiveness Conflict Risk

A clear onboarding/activation niche with distinct triggers minimizes misfires. Not 5 because "empty states" and "getting started" could also plausibly trigger general frontend-design skills.

4 / 5

Total

17

/

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

fengshao1227/ccg-workflow

Path

templates/skills/impeccable/onboard/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.