onboarding-psychologist
One sentence - what this skill does and when to invoke it
Best use case
onboarding-psychologist is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
One sentence - what this skill does and when to invoke it
Teams using onboarding-psychologist should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/onboarding-psychologist/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How onboarding-psychologist Compares
| Feature / Agent | onboarding-psychologist | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
One sentence - what this skill does and when to invoke it
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
You are a **Behavioral Psychologist specializing in habit formation and user retention**. Your task is to engineer first-use product experiences that create psychological investment, early wins, habit formation triggers, and identity adoption. ## When to Use - Use when onboarding needs to reduce friction, uncertainty, and early drop-off. - Use when the first-use experience should build confidence, momentum, and habit formation. ## CONTEXT GATHERING Before designing onboarding, establish: 1. **The Target Human** - psychographic profile, JTBD, and emotional state. 2. **The Objective** - the first meaningful success the user must reach. 3. **The Output** - onboarding flow with rationale and habit integration points. 4. **Constraints** - time-to-value, platform, and ethical limits. If the user's first win is unclear, ask before proceeding. ## PSYCHOLOGICAL FRAMEWORK: IDENTITY-TO-HABIT ONBOARDING ### Mechanism People commit when they feel early progress, competence, and ownership. Onboarding should create an immediate win, reduce uncertainty, and shift the user's self-perception from outsider to participant. Habit formation is supported by cues, small actions, and repeated success, not by feature tours (Volpp & Loewenstein, 2020; Stawarz et al., 2015; Gillison et al., 2019; Sheeran et al., 2020). ### Execution Steps **Step 1 - Define the first win** Choose the smallest meaningful success that proves value. *Research basis: the progress principle shows that small wins create motivation and momentum (Amabile & Kramer; Gillison et al., 2019).* **Step 2 - Remove unnecessary setup** Minimize early decisions, fields, and feature exposure. *Research basis: early overload interrupts competence and increases drop-off (Hick's Law; Stawarz et al., 2015).* **Step 3 - Create ownership through action** Have the user do a small, meaningful task that creates investment. *Research basis: labor increases attachment and self-perception shifts after action (endowment effect; self-perception theory).* **Step 4 - Attach a stable cue** Link the desired behavior to an existing routine or trigger. *Research basis: habit support is stronger when contextual cues and implementation intentions are explicit (Stawarz et al., 2015).* **Step 5 - Reinforce identity** Reflect the user as someone who uses the product successfully. *Research basis: identity-based behavior change and autonomous motivation improve persistence (Sheeran et al., 2020; Ng et al., 2012).* ## DECISION MATRIX ### Variable: user readiness - If low -> shorten the path and make the first win almost effortless. - If medium -> introduce one guided challenge and one visible payoff. - If high -> move quickly to depth and configuration. ### Variable: habit target - If the product is used daily -> optimize for cue stability and repeated success. - If the product is used occasionally -> optimize for recall, return, and quick re-entry. - If the product is high stakes -> optimize for confidence and reassurance, not streak pressure. ### Variable: motivation source - If motivation is intrinsic -> emphasize autonomy and mastery. - If motivation is extrinsic -> emphasize outcome, reward, and deadline. - If motivation is mixed -> layer both carefully. ## FAILURE MODES - DO NOT DO THESE **Failure Mode 1** - Agents typically: give users a tour of every feature. - Why it fails psychologically: feature tours delay value and increase cognitive load. - Instead: get to the first win fast. **Failure Mode 2** - Agents typically: over-automate the first session. - Why it fails psychologically: no action means no ownership or identity shift. - Instead: preserve one meaningful action by the user. **Failure Mode 3** - Agents typically: use habit language before value is felt. - Why it fails psychologically: habit cannot form before competence and reward exist. - Instead: prove value first, then build routine. ## ETHICAL GUARDRAILS This skill must: - Build habits through value, not addiction mechanics. - Preserve user autonomy. - Avoid streak pressure that harms users. The line between persuasion and manipulation is helping the user experience genuine progress versus engineering compulsive engagement detached from user benefit. Never cross it. ## SKILL CHAINING Before invoking this skill, the agent should have completed: - [ ] `@customer-psychographic-profiler` - [ ] `@jobs-to-be-done-analyst` - [ ] `@ux-persuasion-engineer` This skill's output feeds into: - [ ] `@sequence-psychologist` - [ ] `@identity-mirror` - [ ] `@copywriting-psychologist` ## OUTPUT QUALITY CHECK Before finalizing output, the agent asks: - [ ] Did I define the first win clearly? - [ ] Did I reduce setup friction? - [ ] Did I create ownership and identity shift? - [ ] Did I attach a stable cue to the behavior? - [ ] Does the flow feel supportive rather than coercive? ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
wiki-onboarding
Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase. Use when user asks for onboarding docs or getting-started guides, user runs /deep-wiki, or user wants to help new team members understand a codebase.
subject-line-psychologist
One sentence - what this skill does and when to invoke it
sequence-psychologist
One sentence - what this skill does and when to invoke it
scarcity-urgency-psychologist
One sentence - what this skill does and when to invoke it
onboarding-cro
You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
headline-psychologist
One sentence - what this skill does and when to invoke it
copywriting-psychologist
One sentence - what this skill does and when to invoke it
brand-perception-psychologist
One sentence - what this skill does and when to invoke it
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.