onboard

Design onboarding flows, empty states, and first-run experiences.

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/sandrasocial/sselfie-9g --skill onboard-sandrasocial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/sandrasocial/sselfie-9g/tree/main/.agents/skills/onboard
Command: npx skills add https://github.com/sandrasocial/sselfie-9g --skill onboard-sandrasocial

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams design onboarding flows, empty states, and first-run experiences that get users to meaningful value quickly, reduce confusion, and lower early drop-off by focusing on the minimum users must learn to succeed.

Core Features & Use Cases

  • Assess onboarding needs: Identify user goals, confusion points, drop-off moments, and the target "aha moment" to prioritize what to teach first.
  • Design principles & patterns: Apply show-not-tell, progressive disclosure, optional paths for experienced users, contextual tooltips, empty-state guidance, guided tours, and interactive tutorials.
  • Implementation guidance: Recommend content, microcopy, analytics to track completion and skip rates, storage patterns for seen states, and libraries/patterns for tooltips and tours to ensure robust behavior in product environments.
  • Use Case: Redesign a product's first-run experience to guide new users to create their first project and measure time-to-first-success.

Quick Start

Ask onboard to evaluate the current first-run flow for [product] and propose a concise redesign that gets users to their first meaningful action within five minutes.

Frequently Asked Questions about onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an onboarding flow that gets users to their aha moment quickly?

Designing effective onboarding flows requires identifying your target aha moment, gathering user context like experience level and success metrics, and applying progressive disclosure to guide users to their first value action. This approach minimizes confusion and lowers early drop-off rates.

What is the best way to improve empty states and first-run experiences for new users?

Improving empty states and first-run experiences involves using show-not-tell principles, contextual tooltips, and guided tours rather than overwhelming users. Empty-state messaging should provide actionable guidance that directs new users toward meaningful activation steps immediately.

How do I measure time-to-value and activation in a product's first-run experience?

Measuring time-to-value in a first-run experience requires tracking completion and skip rates for interactive tutorials and guided tours. You need to define success metrics and the desired aha moment beforehand to accurately assess if users reach their first meaningful action quickly.

What patterns work best for onboarding experienced users versus new users?

Onboarding experienced users effectively requires providing optional paths and allowing them to skip interactive tutorials, while new users need progressive disclosure and step-by-step guided tours. Differentiating these flows ensures both segments reach activation without unnecessary friction.

Do I need user research data before designing onboarding flows and interactive tutorials?

User research data is required before designing onboarding flows because a context-gathering protocol must be followed to understand experience levels, confusion points, and drop-off moments. This input ensures the first-run experience prioritizes the minimum users must learn to succeed.