onboard-new-user

Guides first-run Codex setup through role selection, context retrieval, and artifact creation.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill onboard-new-user-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard-new-user
Source: https://github.com/AarnavBaddam/skills/tree/main/onboard-new-user
Command: npx skills add https://github.com/AarnavBaddam/skills --skill onboard-new-user-aarnavbaddam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New users often face a blank workspace with no clear path to their first useful result. This Skill runs a structured onboarding flow that personalizes setup by role, connects relevant context sources, and produces a real first artifact instead of leaving the user with an empty account. ## Core Features & Use Cases - Role-Based Personalization: Detects roles from launch context or asks the user, then applies role-specific task and context defaults for product, engineering, marketing, sales, design, data science, operations, finance, and students. - Context Retrieval and Candidate Discovery: Searches connected sources like Drive, Slack, GitHub, Gmail, and local folders to find concrete task anchors before asking the user to type locators. - Guided Artifact Creation: Runs a substance pass over retrieved context, asks refinement questions, then creates a real deliverable such as a document, spreadsheet, deck, or GitHub issue. - Use Case: A product manager signs in, selects a launch plan task, connects Drive and Slack, picks a discovered initiative, answers two refinement questions, and receives a grounded launch brief document. ## Quick Start Start the onboarding flow and walk me through setting up my workspace around my role and a first real task.

Frequently Asked Questions about onboard-new-user

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

FAQPage Schema
How do I onboard a new user to an AI workspace assistant?

Run a structured flow: detect or ask for the user's role, pick a first real task, connect relevant context sources, retrieve concrete content, ask refinement questions, then create a real artifact. Avoid generic templates when actual context is available.

How do I personalize onboarding based on user role?

Use launch-context roles as authoritative when supplied, otherwise ask once. Apply role-specific defaults for tasks and context sources, such as GitHub and Linear for engineering or Drive and Slack for product management.

What context sources can be connected during onboarding?

Supported source types include Google Drive, Notion, Slack, Gmail, GitHub, Linear, Calendar, Figma, and local folders. The flow retrieves task-relevant content from selected sources rather than treating a source container as sufficient context.

What happens if selected context is empty or unreadable during setup?

The flow does not finish setup on empty context. It asks one recovery question with two to three concrete options, including a recommended path and an option to create a starter template instead.

When should onboarding create a starter template instead of a real artifact?

Only when the user explicitly chooses a starter template, explicitly skips context, or no context source was selected. Otherwise the flow requires retrieved context, a task anchor, and refinement answers before creating the artifact.