CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

80%

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

68%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, mostly lean advisory skill with concrete patterns, timings, and output formats. Its main weakness is that the sections read as a reference handbook rather than an explicitly sequenced workflow with checkpoints, and a few best-practice bullets and mid-file sections could be trimmed or split out.

Suggestions

Add an explicit end-to-end workflow (e.g., Initial Assessment → Define activation → Audit current flow → Propose redesign → Define metrics) that ties the existing sections into an ordered process with a checkpoint such as 'verify each proposed step against the defined activation event before recommending it'.

Trim or consolidate generic best-practice bullets that restate knowledge Claude already has (e.g., 'No dead ends', 'Start with quick wins', 'Dismissable at any time') to free token budget for the skill's distinctive content.

Since the Output Format section promises empty state copy and checklist items, add one short worked example (e.g., sample empty-state copy or a filled-in audit entry) so the deliverables are copy-paste ready rather than only structurally described.

DimensionReasoningScore

Conciseness

The body is lean — tables, short bullets, no prose explaining what onboarding is — and most specifics (email timing 24h/72h, checklist size 3-7, tour length 3-5) earn their place. A few generic best-practice bullets ("Dismiss option", "No dead ends", "Start with quick wins") restate knowledge Claude already has, keeping it at anchor 4 rather than 5.

4 / 5

Actionability

For an instruction-only skill the guidance is largely concrete: a defined audit output structure ("Finding → Impact → Recommendation → Priority"), specific email triggers with timings, a funnel analysis format with example percentages, and example aha-moments per product type. It falls short of anchor 5 because it never provides ready-to-use artifacts (e.g., sample checklist copy or empty-state copy) for the common cases it names.

4 / 5

Workflow Clarity

A rough sequence exists ("Before providing recommendations, understand: 1-3", then design guidance, then measurement, plus Task-Specific Questions and an Output Format), but the middle sections are presented as parallel reference material rather than an ordered process, and there are no checkpoints (e.g., verifying a proposed flow against the defined activation metric before delivering it). This matches anchor 3: sequence present but checkpoints missing or implicit.

3 / 5

Progressive Disclosure

No bundle files exist, so the single-file structure is what counts: sections are well-organized with clear headers, tables, and no nested or buried references (`.agents/product-marketing.md` and the Related Skills list are clearly signaled one-level pointers). At ~210 lines, some sections (e.g., Multi-Channel Onboarding, Patterns by Product Type) could be offloaded to reference files, which is the minor gap that holds this at anchor 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

83%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: it explicitly states what the skill does and gives a concrete, natural-language 'Use when' trigger in third person. Its only weakness is that a single generic verb ("Optimize") carries all the listed capability areas, and a few common synonyms (e.g., 'welcome flow', 'getting started') are absent.

DimensionReasoningScore

Specificity

"Optimize post-signup onboarding, user activation, first-run experiences, empty states, and time-to-value" names several concrete capability areas with only minor gaps. It sits above anchor 3 (only 1-2 actions) via its breadth of facets, but below anchor 5 because a single generic verb ("Optimize") covers all of them, unlike the multiple distinct concrete verbs in the 5-star example.

4 / 5

Completeness

The description explicitly 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") with a concrete trigger phrase. This matches anchor 5; it is clearly more explicit than anchor 4's 'when could be more specific'.

5 / 5

Trigger Term Quality

Natural terms users would say are present: "onboarding", "sign up", "activation", "first-run", "empty states", "aha moment". A few common synonyms are missing (e.g., "welcome flow", "getting started", "new user"), matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Post-signup onboarding" and the activation-focused trigger carve a clear niche, but facets like "first-run experiences" and "empty states" overlap with adjacent UX/design and related marketing skills (signup, emails). Minor overlap risk with closely related skills — anchor 4, not the minimal-conflict clarity of anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/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.