- Home
- Skills
- Steveclarke
- Dotfiles
- I Onboard
i-onboard_skill
- Shell
31
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill steveclarke/dotfiles --skill i-onboard- SKILL.md8.1 KB
Overview
This skill designs or improves onboarding flows, empty states, and first-time user experiences to help users get started and reach the product's "aha moment" quickly. I focus on practical, time-to-value driven onboarding that is contextual, optional, and measurable. The goal is a lean, interactive path that teaches only what matters so users can succeed fast.
How this skill works
I follow a Context Gathering Protocol to learn user experience level, motivation, and the target "aha moment" before any design work. Then I assess where users get stuck and define the minimum success criteria. I produce concrete onboarding artifacts—welcome screens, empty states, tooltips, guided tours, and interactive tutorials—plus implementation patterns and analytics strategies to track completion and time-to-value.
When to use it
- When new users struggle to find the core value or abandon before first success
- When a feature area is empty, confusing, or frequently returns no results
- When launching a major UI change or a complex feature set
- When you need to reduce time-to-value for onboarding KPIs
- When converting users from a competitor or a different mental model
Best practices
- Show, don't tell: use real examples and interactive steps rather than long prose
- Make onboarding optional and skip-able for experienced users
- Front-load the 20% of features that deliver 80% of value
- Use progressive disclosure: teach features at point of need, not upfront
- Track seen/dismissed states and analytics to avoid repeating onboarding
Example use cases
- Design a welcome screen and first-success flow that gets users to create their first project in under 5 minutes
- Replace blank dashboards with contextual empty states that explain value and include a CTA and template
- Create contextual tooltips for a complex toolbar to surface only the next-most-important action
- Build a short guided tour (3–6 steps) for a major release with replay and skip options
- Implement a sandbox interactive tutorial to validate users can complete a high-value workflow
FAQ
No. Onboarding is optional, skip-able, and designed to get users to value fast, not teach everything.
How do you measure onboarding success?
Track completion rate, time-to-value, drop-off points, and skip rate. Use these signals to simplify or rework steps.