CtrlK
BlogDocsLog inGet started
Tessl Logo

onboarding-cro

You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.

33

Quality

29%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/onboarding-cro/SKILL.md

The canonical home for this skill is onboarding-cro in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

38%Scale 1-5

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

This skill reads more like a comprehensive onboarding strategy guide or textbook than a focused skill for Claude. It extensively explains concepts Claude already knows (habit loops, empty states, tooltips, progress indicators) without providing the specific, executable guidance that would make it actionable. The content would benefit greatly from aggressive trimming of explanatory material and splitting detailed sections (experiments, product-type patterns) into separate reference files.

Suggestions

Cut the content by 50-60% by removing explanations of concepts Claude already knows (habit loops, what empty states are, tooltip best practices) and focus on the specific decision framework and output templates.

Move the 'Experiment Ideas' section (~80 lines) and 'Common Patterns by Product Type' into separate bundle files referenced from the main skill.

Add a clear numbered workflow with validation steps: e.g., '1. Gather context via questions → 2. Define activation metric → 3. Map current funnel with drop-offs → 4. Validate findings with user → 5. Design flow → 6. Define measurement plan'.

Include at least one concrete, complete example output (e.g., a sample onboarding audit for a fictional SaaS product) so Claude has a clear template to follow.

DimensionReasoningScore

Conciseness

The skill is significantly verbose at ~350+ lines, extensively covering concepts that Claude already understands (what empty states are, what tooltips are, basic product types, habit loop theory). Much of the content reads like a textbook on onboarding rather than actionable instructions Claude needs. Sections like 'Core Principles' and 'Engagement Loops' explain well-known concepts without adding novel, specific guidance.

2 / 5

Actionability

The skill provides structured frameworks and checklists (e.g., onboarding audit format, checklist item structure) but lacks concrete, executable examples. Most guidance is conceptual ('Remove every step between signup and that moment') rather than specific. The experiment ideas section is a useful list but remains at the level of suggestions rather than step-by-step executable instructions. No code, no specific tool commands, no copy-paste ready deliverables.

3 / 5

Workflow Clarity

There is a rough workflow implied: Initial Assessment → Define Activation → Design Flow → Measure. The funnel analysis section shows a clear sequence. However, there are no explicit validation checkpoints or feedback loops for the overall process. The 'Output Format' section defines deliverables but doesn't tie them into a clear step-by-step workflow with verification steps.

3 / 5

Progressive Disclosure

The content is a monolithic wall of text with no bundle files to offload detailed sections. The experiment ideas section alone is ~80 lines that could easily be a separate reference file. Common patterns by product type, multi-channel onboarding details, and the extensive experiment catalog all belong in separate files. References to related skills exist but no actual supporting files are provided or referenced for the bulk content.

2 / 5

Total

10

/

20

Passed

Description

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

This description reads as a persona prompt ('You are an expert...') rather than a skill description, using first/second person framing and abstract goals instead of concrete capabilities. It lacks specific actions, trigger terms, and a 'Use when...' clause, making it very difficult for Claude to distinguish this skill from others or know when to select it.

Suggestions

Replace the persona framing with concrete actions in third person, e.g., 'Designs user onboarding flows, writes welcome email sequences, creates in-app tutorials, and maps activation metrics.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about onboarding flows, welcome sequences, first-time user experience, signup funnels, activation rates, or reducing churn.'

Remove abstract buzzwords like 'aha moment' and 'long-term retention' and replace with specific deliverables or outputs the skill produces.

DimensionReasoningScore

Specificity

The description uses entirely vague, abstract language like 'aha moment', 'establish habits', and 'long-term retention' without naming any concrete actions. There are no specific capabilities listed—no mention of what it actually does (e.g., design onboarding flows, write welcome emails, create tutorials).

1 / 5

Completeness

The 'what' is vague ('help users reach their aha moment') and there is no explicit 'when' clause or trigger guidance. The description reads more like a persona definition than a skill description, and the lack of a 'Use when...' clause caps this at 3 at best, but the weak 'what' brings it to 2.

2 / 5

Trigger Term Quality

The terms 'user onboarding' and 'activation' are relevant domain keywords, but they are limited and miss many natural phrases users might say such as 'welcome flow', 'signup experience', 'first-time user', 'tutorial', 'walkthrough', or 'churn'.

2 / 5

Distinctiveness Conflict Risk

The description is broad enough to overlap with many skills related to UX design, product strategy, growth, retention, or user experience. 'Onboarding' and 'activation' provide some domain focus but the vague framing creates high overlap risk.

2 / 5

Total

7

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.