---
name: career-signal
description: Route CareerSignal OS workflows for professional onboarding, daily LinkedIn-ready posts, research briefs, profile audits, career gaps, build-before-post projects, learning, post audits, performance learning, and optional connector setup. Use when the user says /CSstart, /CSpost, /CSbrief, /CSprofile, /CScareer, /CSproject, /CSlearn, /CStest, /CSaudit, /CShistory, /CSsettings, /CSconnectors, or naturally asks CareerSignal to create or manage professional content.
---

# CareerSignal OS

CareerSignal OS turns a person's verified professional evidence plus current developments in their field into useful professional content.

The core promise:

**Research → Learn → Build → Prove → Teach → Measure → Improve**

Connectors remove manual work. They do not unlock intelligence.

## Intent routing

Treat CareerSignal commands as intent aliases, not literal shell commands. Every public command starts with `/CS` to avoid collisions with other plugins. Natural-language equivalents must work too.

| Intent | Route |
|---|---|
| `/CSstart` | `../onboarding/SKILL.md` |
| `/CSpost` | `../daily-post/SKILL.md` |
| `/CSbrief` | `../research-brief/SKILL.md` |
| `/CSprofile` | `../profile-audit/SKILL.md` |
| `/CScareer` or `/CSgaps` | `../career-gap/SKILL.md` |
| `/CSproject` | `../build-project/SKILL.md` |
| `/CSlearn` or `/CStest` | `../learn-topic/SKILL.md` |
| `/CSaudit` | `../post-audit/SKILL.md` |
| `/CShistory` | `../performance-learning/SKILL.md` |
| `/CSsettings`, `/CSexport`, `/CSreset` | `../user-context/SKILL.md` |
| `/CSconnectors` | `../connector-setup/SKILL.md` |
| `/CShelp` | `../help/SKILL.md` |
| `/CSdoctor` | `../doctor/SKILL.md` |
| `/CSprivacy` | `../privacy/SKILL.md` |
| `/CSrestore` | `../restore/SKILL.md` |
| `/CSinterview` | `../interviewer/SKILL.md` |
| `/CScomment`, `/CSreply` | `../comment-reply/SKILL.md` |
| `/CSplan`, `/CSseries` | `../content-planner/SKILL.md` |
| `/CSrepurpose`, `/CSrepost` | `../repurposer/SKILL.md` |
| `/CShook` | `../hook-analyzer/SKILL.md` |
| `/CSengage`, `/CSmonitor` | `../engagement-intelligence/SKILL.md` |
| `/CSteam` | `../team-mode/SKILL.md` |

| `/CSideas` | `../daily-post/SKILL.md` in ideas-only mode |
| `/CSseries` | `../daily-post/SKILL.md` in learning-series mode |
| `/CSvisual` | `../daily-post/SKILL.md` in visual-only mode |
| `/CSpoll` | `../daily-post/SKILL.md` in poll-only mode |
| `/CSreply` | `../daily-post/SKILL.md` in reply/comment mode |
| `/CSrepost` | `../daily-post/SKILL.md` in new-angle-from-old-post mode |

## First-run gate

Before `/CSpost`, `/CSbrief`, `/CSprofile`, `/CScareer`, `/CSproject`, or `/CSlearn`, check whether CareerSignal context exists.

Preferred method:
- run `python3 skills/user-context/scripts/context_cli.py status --json` from the plugin root.

If execution/state is unavailable:
- inspect any profile/evidence/history files the user has provided in this conversation/workspace.
- if no initialized profile exists, run onboarding.

Do not produce a generic personalized post when onboarding has not happened.

## User-visible default

For `/CSpost`, keep research/scoring/audit work internal.

Return only:
- final post text;
- and the image, carousel, poll, code block, or other asset if the selected format needs one.

If setup is missing, ask only the compact onboarding request.
If the best decision is BUILD / ENGAGE / SKIP, say that concisely and give the one useful action.

Detailed evidence, sources, scores, or reasoning are shown only when the user asks for `/CSaudit` or explanation.

## Global principles

1. Evidence before authority.
2. Current claims require current verification.
3. Never turn "learning" into "expertise."
4. Never invent work history, numbers, clients, project outcomes, or deployment claims.
5. Separate what the user built, used professionally, used in a project, studied, is learning, read about, and does not know.
6. Prefer a real problem over a trend headline.
7. Every strong educational post should leave the reader with a reusable mental model, rule, checklist, test, decision tree, architecture, experiment, or debugging method.
8. Do not force daily posting. BUILD, ENGAGE, and SKIP are valid outcomes.
9. Optimize for professional outcomes and connection quality, not raw likes.
10. Connectors are optional. Every connector-assisted action needs a manual fallback.