CtrlK
BlogDocsLog inGet started
Tessl Logo

onboarding

Optimize post-signup onboarding, user activation, first-run experiences, empty states, and time-to-value. Use when users sign up but do not reach the product's aha moment or continue using it.

57

Quality

66%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 is a competent strategic advisory skill that provides good frameworks and mental models for onboarding CRO, but it lacks the concrete, executable specificity that would make it highly actionable. It over-explains some concepts Claude already understands (like general UX principles) while under-delivering on specific templates, example outputs, and copy-paste ready artifacts. The workflow is logically organized but would benefit from explicit sequencing and validation steps.

Suggestions

Add a concrete example audit output showing a real Finding → Impact → Recommendation → Priority entry, so Claude knows exactly what format to produce.

Include specific, copy-paste ready templates for key deliverables like onboarding email copy, empty state copy, or checklist specifications rather than just describing best practices.

Add an explicit numbered workflow (Step 1: Read context → Step 2: Ask remaining questions → Step 3: Audit current state → Step 4: Produce recommendations) with validation checkpoints between steps.

Trim general UX principles Claude already knows (e.g., 'Progress Creates Motivation', 'Do, Don't Show') to brief reminders or remove them entirely to improve token efficiency.

DimensionReasoningScore

Conciseness

The skill is reasonably structured but includes several sections that explain concepts Claude already knows (e.g., what empty states are, general principles like 'Time-to-Value Is Everything'). Tables and lists are efficient but there's padding in explanations of obvious concepts like 'Interactive > Tutorial' and 'Progress Creates Motivation.' Could be tightened by ~30%.

3 / 5

Actionability

The skill provides structured frameworks (checklists, tables, output formats) but remains largely at the strategic/advisory level without concrete, executable artifacts. There are no copy-paste ready templates, no specific code snippets, no example audit outputs, and no concrete email copy examples. The guidance is directional rather than executable.

3 / 5

Workflow Clarity

There's a logical sequence implied (assess → define activation → design flow → measure), and the output format section provides structure for deliverables. However, there are no explicit validation checkpoints, no feedback loops for iterating on recommendations, and the workflow between sections is implicit rather than explicitly sequenced with numbered steps.

3 / 5

Progressive Disclosure

The content is well-organized with clear section headers, tables, and a logical hierarchy. It references related skills at the bottom and checks for external context files. Without bundle files, the content length (~200 lines) is reasonable for a single file. Minor improvement could come from splitting detailed patterns (e.g., email sequences, empty state examples) into separate reference files.

4 / 5

Total

13

/

20

Passed

Description

78%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 is a solid description with a clear 'Use when' clause and good trigger term coverage for the onboarding/activation domain. Its main weakness is that the 'what' portion lists topic areas rather than concrete actions the skill performs (e.g., 'audit onboarding flows', 'design empty states', 'map activation metrics'). Adding specific deliverables or actions would strengthen the specificity dimension.

Suggestions

Replace the generic verb 'Optimize' with specific actions the skill performs, e.g., 'Audit onboarding flows, design empty states, define activation metrics, and map user journeys from signup to aha moment.'

Add a few more trigger synonyms such as 'welcome flow', 'setup wizard', 'new user retention', or 'drop-off after signup' to improve keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (onboarding/activation) and lists several related concepts (post-signup onboarding, user activation, first-run experiences, empty states, time-to-value), but these are more like sub-topics than concrete actions. The only action verb is 'Optimize', which is generic. It doesn't specify what concrete outputs or steps the skill performs.

3 / 5

Completeness

Clearly answers both 'what' (optimize post-signup onboarding, user activation, first-run experiences, empty states, and time-to-value) and 'when' ('Use when users sign up but do not reach the product's aha moment or continue using it'). The 'when' clause is explicit and provides a concrete trigger scenario.

5 / 5

Trigger Term Quality

Includes several natural terms users might use: 'onboarding', 'user activation', 'first-run experiences', 'empty states', 'time-to-value', 'aha moment', 'sign up'. Missing some common synonyms like 'welcome flow', 'setup wizard', 'retention', 'churn', 'conversion funnel', or 'FTUE'.

4 / 5

Distinctiveness Conflict Risk

Fairly distinct with its focus on post-signup onboarding and activation specifically. Could have minor overlap with broader UX/product design skills or retention/growth skills, but the specific focus on the signup-to-activation journey and 'aha moment' language narrows it well.

4 / 5

Total

16

/

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.