# Onboarding

> Initialize CareerSignal OS from a small amount of user input. Use on /CSstart, when CareerSignal is first installed, or automatically when a personalized CareerSignal workflow is requested but no initialized profile exists.

- Skill: `venilkukadiya52/onboarding` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add venilkukadiya52/onboarding`
- Raw SKILL.md: https://api.skillmd.com/api/skills/venilkukadiya52/onboarding/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: venilkukadiya52 (https://skillmd.com/u/venilkukadiya52)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/venilkukadiya52/onboarding

---


# CareerSignal Onboarding

Ask for information once, then infer the rest.

## Compact first-run request

Ask in one message:

> To personalize CareerSignal once, send:
> 1. your CV/resume or LinkedIn profile (at least one);
> 2. what you want to be known for or target roles/topics;
> 3. optional GitHub/portfolio/project links;
> 4. optional 2–5 old posts/screenshots you wrote or like;
> 5. preferred language;
> 6. publishing mode: **Manual** or **Connected/Automated**.
>
> You can skip optional items. CareerSignal will infer the rest.

Do not ask a long questionnaire.

## Inference

From the supplied sources, build:

- professional identity;
- target roles/topics;
- evidence graph;
- knowledge boundaries;
- skills and maturity;
- projects;
- public/private boundaries;
- likely audiences;
- initial voice fingerprint;
- content domains;
- topics to avoid;
- supported and unsupported claims;
- publishing preferences;
- connector capabilities;
- language/locale.

Use `references/onboarding-rules.md`.

## Persist

When local execution is available:
1. initialize state:
   `python3 skills/user-context/scripts/context_cli.py init`
2. write the inferred context through:
   `python3 skills/user-context/scripts/context_cli.py import-onboarding --file <json>`

Do not save credentials, passwords, API keys, private tokens, or raw confidential documents.

If durable state is unavailable, create a compact portable profile package in the current workspace and tell the model to reuse it.

## Completion

After onboarding:
- do not ask these inputs again unless the user explicitly resets or changes them;
- if onboarding was triggered by `/CSpost`, continue directly into the daily-post workflow after initialization.

Do not stop at "setup complete" if the original request was for a post.

## Already initialized

If CareerSignal is already initialized and the user runs `/CSstart` again, do not repeat onboarding. Show a compact status and say that `/CSsettings` can update preferences or `/CSreset` can restart onboarding.