CtrlK
BlogDocsLog inGet started
Tessl Logo

onboarding-cro

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is well-organized, concise, and uses progressive disclosure effectively with a single verified reference. It is weaker on actionability and workflow clarity, where strategic framing and implicit checkpoints dominate over fully executable, validated step sequences.

Suggestions

Convert abstract principles (e.g., "Time-to-Value Is Everything") into concrete, step-by-step actions Claude should take, so guidance is executable rather than strategic.

Add an explicit validation/iterate checkpoint to the workflow, e.g., after drafting recommendations, verify against the activation definition and revise before producing the final output.

For the Onboarding Audit output format, specify the exact fields and a worked example so the deliverable is copy-paste ready rather than a high-level schema.

DimensionReasoningScore

Conciseness

The body is bullet- and table-driven with no preamble explaining concepts Claude already knows, and every section earns its place; it assumes Claude's competence throughout. Not a 2 because it avoids padding and verbosity despite its length.

3 / 3

Actionability

Mixes strong concrete specifics ("3-7 items," "24h, 72h," "days 3, 7, 14," "Finding → Impact → Recommendation → Priority") with abstract strategic framing ("Remove every step between signup and experiencing core value," "One Goal Per Session"). Not a 3 because much of the guidance describes strategy rather than giving fully executable steps; not a 1 because concrete tactical details are present.

2 / 3

Workflow Clarity

A sequence is present (Initial Assessment → recommendations → Output Format, with a Measurement feedback loop), but there is no explicit validation/iterate checkpoint binding the steps together. Not a 3 because checkpoints are implicit; not a 1 because the steps are clearly listed and sequenced.

2 / 3

Progressive Disclosure

The body is an overview with exactly one clearly signaled, one-level-deep reference ("See references/experiments.md"), which I verified is a real file, with no nested references. Matches the clear-overview-with-well-signaled-references anchor.

3 / 3

Total

10

/

12

Passed

Description

100%

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 third-person, concise, and strong across all dimensions: it states concrete capabilities, lists natural trigger terms, answers both what and when, and disambiguates from neighboring skills. No changes needed.

DimensionReasoningScore

Specificity

Names several concrete capability areas ("optimize post-signup onboarding, user activation, first-run experience, or time-to-value") rather than a vague domain, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (optimize onboarding/activation/first-run/time-to-value) and when via a clear "Also use when the user mentions..." trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Provides extensive natural quoted triggers users would actually say ("onboarding flow," "activation rate," "aha moment," "empty states," "new user experience"), giving strong coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (post-signup onboarding/activation) and actively reduces conflict with explicit disambiguation pointers to signup-flow-cro and email-sequence.

3 / 3

Total

12

/

12

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.

Validation15 / 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
freekmurze/dotfiles
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.