CtrlK
BlogDocsLog inGet started
Tessl Logo

onboarding-optimization

When the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy.

74

Quality

91%

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

83%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 content is a well-structured, highly actionable onboarding playbook with strong templates and benchmarks. It is mostly lean and well-organized, with only minor opportunities to tighten prose and add an explicit verification step in the audit output loop.

Suggestions

Add an explicit validation/review checkpoint to the audit workflow (e.g., 'Re-check the revised flow: does every remaining screen directly serve the activation event?') to close the feedback loop.

Trim lightly padded framing sentences like 'Permissions are the #1 drop-off point' where the timing table already conveys the point.

Consider moving the Funnel Benchmarks and Personalization Questions sections into a referenced file if the skill grows, keeping SKILL.md as a tighter overview.

DimensionReasoningScore

Conciseness

The body is dense with actionable tables and tight prose that mostly respects Claude's competence, but some repeated framing ('Permissions are the #1 drop-off point') and inline benchmarks add mild padding that could be trimmed.

4 / 5

Actionability

Provides concrete, executable guidance throughout — a screen-flagging scheme, scoring tables, permission-timing rules, onboarding flow templates, benchmark thresholds, and a copy-paste-ready output format template covering common cases.

5 / 5

Workflow Clarity

The Initial Assessment and four-step Onboarding Audit Framework give a clear sequence, but the audit is diagnostic rather than destructive so strict validation checkpoints are less critical; it lacks an explicit verify/retry loop for the revised-flow output.

4 / 5

Progressive Disclosure

Well-organized into clearly signaled sections with one-level-deep cross-skill references ('See monetization-strategy', 'See app-analytics'); no bundle files exist, so most referenceable detail stays inline, which is acceptable for this overview-style skill.

4 / 5

Total

17

/

20

Passed

Description

100%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 excellent: it states concrete capabilities, provides a rich set of natural trigger terms, answers both what and when explicitly, and scopes itself against neighboring skills to avoid conflicts.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, optimize the first-run flow' — with comprehensive coverage of the onboarding domain.

5 / 5

Completeness

Explicitly answers both 'what' (optimize onboarding to increase activation/reduce drop-off) and 'when' (a 'Use when...' clause with concrete trigger phrases), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural terms including synonyms and phrasings users actually say — 'onboarding', 'first-run', 'activation', 'tutorial', 'day 1 retention', 'new user flow', 'permission prompts', 'sign-up conversion', 'onboarding funnel', 'users dropping off early'.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct onboarding-specific triggers and explicit handoffs to sibling skills ('For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy'), minimizing conflict risk.

5 / 5

Total

20

/

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
Eronred/aso-skills
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.