CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onboarding

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," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

Quality

90%

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

86%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.

A well-structured, highly actionable reference for onboarding CRO. The aha-moment methodology is unusually rigorous about correlation vs. causation and cohort maturity, and progressive disclosure is exemplary. The main costs are mild verbosity in the psychology explanations and a top-level workflow that is implied by section order rather than made explicit.

Suggestions

Compress the Onboarding Psychology bullets to one-line definitions with the applied detail (e.g., keep '+40% completion' and the boosters/blockers framing, drop the general explanations of Peak-End Rule and Goldilocks Rule) to cut tokens without losing guidance.

State the overall procedure explicitly as a numbered sequence at the top (Initial Assessment → Define activation → Design flow/checklist/empty states → Coordinate email triggers → Handle stalled users → Measure and report), so the workflow order doesn't have to be inferred from section order.

Add a validation checkpoint before recommending changes: confirm analytics instrumentation exists for each funnel step and that activation metrics can actually be measured, mirroring the rigor the aha-moment section already applies.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no filler, but the Onboarding Psychology section explains broadly known behavioral concepts (Peak-End Rule, Goldilocks Rule, BJ Fogg) at a length that could be trimmed to one-line definitions with the applied CRO detail kept.

4 / 5

Actionability

Concrete guidance throughout: '3-7 items', 'Max 3-5 steps per tour', email triggers at '24h, 72h, days 3, 7, 14', output templates (Finding → Impact → Recommendation → Priority), and a fully specified 5-step cohort methodology for finding the aha moment. For an instruction-only skill, this covers the common cases with copy-ready specifics.

5 / 5

Workflow Clarity

A logical assess→define-activation→design→multi-channel→measure sequence is present, and the aha-moment method includes explicit validation ('confirm the definition on a later mature cohort before adopting it') and a causation check. The top-level flow is implied by section order rather than stated as an explicit ordered procedure with checkpoints.

4 / 5

Progressive Disclosure

All three referenced files exist, are exactly one level deep, and are signaled twice — inline at point of use ('See references/activation-models.md for the 5 models...') and in a References section with one-line content summaries. The body stays at overview altitude with detail (experiments, models, MPTV benchmarks) correctly split out.

5 / 5

Total

18

/

20

Passed

Description

90%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 with best-in-class trigger coverage, explicit what/when, and proactive boundary disambiguation. The only gap is capability specificity: it says the domain and the goal ('optimize') but not the concrete outputs the skill delivers.

DimensionReasoningScore

Specificity

'optimize post-signup onboarding, user activation, first-run experience, or time-to-value' names specific domains but relies on a single generic action verb; the description never lists the concrete deliverables the skill produces (onboarding audit, flow design, checklist patterns, experiment plan). Not anchor 4 (no list of several specific actions) and not anchor 2 (the domains themselves are specific, not minimal).

3 / 5

Completeness

Explicitly answers both: what ('optimize post-signup onboarding, user activation, first-run experience, or time-to-value') and when, via three explicit trigger constructions ('When the user wants to...', 'Also use when the user mentions...', 'Use this whenever users are signing up but not sticking around'). Third-person voice throughout, so no penalty applies.

5 / 5

Trigger Term Quality

Comprehensive natural-language coverage including colloquial phrasings users would actually say: 'onboarding flow', 'aha moment', 'users aren't activating', 'nobody completes setup', 'users sign up but don't use the product', 'time to value', plus the synonym pairs ('first-run experience' / 'first session experience' / 'new user experience').

5 / 5

Distinctiveness Conflict Risk

Clear post-signup/activation niche with distinct triggers, plus explicit disambiguation against the nearest neighbors ('For signup/registration optimization, see signup. For ongoing email sequences, see emails.'), minimizing wrong-skill triggering.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/onboarding/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.