CtrlK
BlogDocsLog inGet started
Tessl Logo

onboard

Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly.

81

1.10x
Quality

61%

Does it follow best practices?

Impact

94%

1.10x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./archived/legacy-companion/.agents/skills/onboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-3

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

The body is a thorough, well-structured onboarding design guide with some concrete examples, but it is verbose with concepts Claude already knows, lacks explicit validation checkpoints, and keeps everything inline without progressive disclosure to separate files.

Suggestions

Trim general UX explanations (onboarding principles, 'aha moment') that Claude already knows, keeping only skill-specific patterns and the concrete examples.

Add explicit validation checkpoints in the workflow (e.g., after drafting an onboarding flow, check skip-rate and completion-rate thresholds before finalizing).

Move the detailed implementation patterns and library references into a separate reference file (e.g., IMPLEMENTATION.md) and link to it from the overview to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is well-organized but spends many tokens explaining general UX concepts Claude already knows (e.g., 'Show, Don't Tell', 'Time to Value', 'aha moment', progressive disclosure), so it is mostly efficient but could be tightened.

2 / 3

Actionability

It offers some concrete guidance (an empty-state copy example, a localStorage snippet, named libraries like Tippy.js and Intro.js), but much of the body remains abstract principle/checklist direction rather than fully concrete patterns.

2 / 3

Workflow Clarity

There is a clear assess -> design -> verify sequence and a verification checklist with metric interpretations, but validation checkpoints are implicit rather than explicit gated steps, leaving it just below the top anchor.

2 / 3

Progressive Disclosure

The content is well-organized into clear sections, but it is a single ~230-line monolithic file with no bundle files or one-level-deep references; the under-50-line simple-skill exemption does not apply, so it sits at the 'could be better organized' anchor.

2 / 3

Total

8

/

12

Passed

Description

72%Weight 40%Scale 1-3

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 specific and distinct with good trigger terms, but it is held back by imperative voice in the first sentence and the absence of an explicit 'Use when' trigger clause.

Suggestions

Rewrite the first sentence in third person (e.g., 'Designs or improves onboarding flows...') to avoid the voice penalty.

Add an explicit 'Use when...' clause naming trigger situations (e.g., 'Use when designing onboarding flows, empty states, or first-time user experiences').

Tighten the second sentence into concrete trigger guidance rather than a restatement of purpose.

DimensionReasoningScore

Specificity

The phrase 'Design or improve onboarding flows, empty states, and first-time user experiences' names multiple concrete capabilities, which would normally anchor at 3, but the first sentence uses imperative/second-person voice ('Design or improve') rather than third person, triggering the one-point specificity penalty per the rubric.

2 / 3

Completeness

It clearly answers 'what' (design/improve onboarding flows, empty states, first-time UX) but lacks an explicit 'Use when...' trigger clause; the second sentence states a goal rather than when Claude should invoke the skill, capping completeness at 2.

2 / 3

Trigger Term Quality

Terms like 'onboarding flows', 'empty states', 'first-time user experiences', and 'get started' are natural keywords a product designer would actually say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The onboarding/empty-state/first-time-UX niche is distinct and unlikely to trigger for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

10

/

12

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.

Validation15 / 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
The-Vibe-Company/companion
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.