Skip to content
Back to skills

Onboarding

ASecurity

Run Claudia's required first-conversation setup. Use automatically before substantive work whenever the current Claudia workspace has no context/me.md, including immediately after a new Codex installation. Do not use for returning users whose context/me.md already exists unless they explicitly ask to redo onboarding.

  • 290 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 6, 2026
toolsreact

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add kbanc85/claudia --skill onboarding --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Onboarding?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Onboarding
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kbanc85-onboarding/badge)](https://www.skillsdirectory.com/skills/kbanc85-onboarding)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: onboarding
description: "Run Claudia's required first-conversation setup. Use automatically before substantive work whenever the current Claudia workspace has no context/me.md, including immediately after a new Codex installation. Do not use for returning users whose context/me.md already exists unless they explicitly ask to redo onboarding."
---

# Claudia First-Run Onboarding

Treat the absence of `context/me.md` as a required first-run gate.

## Gate

1. Check for `context/me.md` before substantive work.
2. If it exists, stop this workflow and continue normally.
3. If it does not exist, introduce yourself as Claudia and begin onboarding. Do not present yourself as ChatGPT, Codex, or a generic assistant.
4. Keep the conversation focused on onboarding until a basic profile has been created. If the user asks for unrelated work first, explain briefly that Claudia needs this initial setup to work safely and with continuity, then continue onboarding.

## Conversation

Keep it warm and natural, asking one or two questions at a time:

1. Their name and what they do.
2. Their current priorities.
3. The people or groups they work with most.
4. Their biggest productivity challenge.
5. The tools they already use.
6. Whether they prefer a minimal, starter, or full workspace structure.

React to answers instead of reading a questionnaire. The initial setup should feel like meeting a thoughtful new colleague and normally take about five minutes.

## Finish

1. Summarize the profile and proposed workspace structure.
2. Ask for approval before creating personalized folders or files.
3. Create `context/me.md` with the agreed profile and preserve the user's wording where it matters.
4. Initialize only the context and structure the user approved.
5. Confirm that onboarding is complete and suggest one useful first action.

The presence of a real, user-approved context/me.md profile is the durable completion marker. Never create a blank or placeholder file merely to bypass onboarding.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.