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," "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-flow-cro. For ongoing email sequences, see email-sequence.

86

1.00x
Quality

81%

Does it follow best practices?

Impact

92%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%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-organized, actionable onboarding CRO reference that keeps the framework inline and splits experiment detail into a clearly signaled one-level-deep reference. Its main weakness is workflow clarity: the material reads as a topical framework rather than a sequenced procedure with validation checkpoints.

Suggestions

Add an explicit step-by-step procedure section (e.g., 1. Read product-marketing context → 2. Confirm activation definition → 3. Audit drop-off → 4. Propose flow changes → 5. Define metrics) so Claude follows a clear sequence rather than browsing topics.

Insert validation checkpoints into the workflow, such as confirming the activation event with the user before designing flow changes and verifying that proposed metrics map to measurable events.

Tighten the Core Principles section by merging self-evident principles into a single concise list, since the current four short subsections restate expertise Claude already has.

DimensionReasoningScore

Conciseness

The body is efficient and avoids explaining concepts Claude already knows, relying on tight tables and bullet lists; a few core principles (e.g., "Time-to-Value Is Everything — Remove every step between signup and experiencing core value") are somewhat self-evident for an expert and could be trimmed.

4 / 5

Actionability

It gives concrete, specific guidance throughout ("3-7 items," "Max 3-5 steps per tour," email triggers at "24h, 72h," and an output template "Finding → Impact → Recommendation → Priority"), with only minor sections drifting into abstraction such as "Find Your Aha Moment."

4 / 5

Workflow Clarity

The skill is organized as a topical reference framework (assessment, principles, design, measurement) rather than a crisply sequenced procedure, and the loose implicit flow (assess → define activation → design → measure) lacks explicit validation checkpoints.

3 / 5

Progressive Disclosure

The SKILL.md serves as a clear overview with well-organized sections and a single, clearly signaled one-level-deep reference to references/experiments.md (a real bundle file) for comprehensive experiment ideas, with content appropriately split.

5 / 5

Total

16

/

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, well-structured description that clearly answers both what and when with an exhaustive set of natural trigger phrases and explicit boundary guidance to related skills. The only soft spot is specificity, where the capability is framed as abstract goals rather than concrete actions.

DimensionReasoningScore

Specificity

The description names the domain ("optimize post-signup onboarding, user activation, first-run experience, or time-to-value") but frames it as abstract goals rather than the concrete actions an agent would perform (e.g., audit funnels, design activation flows, write empty-state copy), matching the anchor that lists the domain with only 1–2 concrete actions.

3 / 5

Completeness

It explicitly answers both what ("optimize post-signup onboarding, user activation, first-run experience, or time-to-value") and when (an extensive "Also use when the user mentions..." trigger list plus "Use this whenever users are signing up but not sticking around").

5 / 5

Trigger Term Quality

It provides comprehensive natural phrasings users would actually say, including synonyms and colloquial variants like "users aren't activating," "nobody completes setup," "aha moment," and "users sign up but don't use the product."

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (post-signup onboarding/activation) and explicitly disambiguates adjacent skills ("For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence."), minimizing conflict risk.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MapleTechLabs/maple
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.