# Career Signal Os

> Research-driven professional intelligence and content OS. Personalize once from a CV/profile and optional projects, then use /CSpost to research current problems in the user's field, choose the strongest evidence-backed topic and format, create a humanized LinkedIn-ready post or learning asset, and keep free/manual fallbacks when connectors are unavailable. Also supports /CSstart, /CSbrief, /CSprofile, /CScareer, /CSproject, /CSlearn, /CStest, /CSaudit, /CShistory, /CSsettings, /CSconnectors, /CSideas, /CSseries, /CSvisual, /CSpoll, /CSreply, and /CSrepost.

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

---


# CareerSignal OS

CareerSignal is a portable professional-intelligence skill bundle for Claude, Claude Code, Codex, ChatGPT-compatible plugin environments, and agents that read `SKILL.md`.

Core loop:

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

## Zero-setup mode

CareerSignal works without paid connectors.

- `/CSstart` initializes the user's professional context once.
- `/CSpost` researches and builds the best post for that day.
- The result is returned for manual copy/paste.
- If image generation exists, use it when useful.
- If it does not, return the exact visual/carousel brief.
- Optional connectors may remove manual steps, but they never unlock the core intelligence.

## Command routing

Read the relevant focused skill:

- `/CSstart` → `skills/onboarding/SKILL.md`
- `/CSpost`, `/CSideas`, `/CSseries`, `/CSvisual`, `/CSpoll`, `/CSreply`, `/CSrepost` → `skills/daily-post/SKILL.md`
- `/CSbrief` → `skills/research-brief/SKILL.md`
- `/CSprofile` → `skills/profile-audit/SKILL.md`
- `/CScareer`, `/CSgaps` → `skills/career-gap/SKILL.md`
- `/CSproject` → `skills/build-project/SKILL.md`
- `/CSlearn`, `/CStest` → `skills/learn-topic/SKILL.md`
- `/CSaudit` → `skills/post-audit/SKILL.md`
- `/CShistory` → `skills/performance-learning/SKILL.md`
- `/CSsettings`, `/CSexport`, `/CSreset` → `skills/user-context/SKILL.md`
- `/CSconnectors` → `skills/connector-setup/SKILL.md`

Natural-language equivalents also work.

## First-run rule

If a personalized workflow is requested before setup, run onboarding first and then continue the original request.

Ask once for:
1. CV/resume or LinkedIn profile;
2. desired roles/topics;
3. optional GitHub/portfolio;
4. optional old posts/screenshots;
5. preferred language;
6. manual or connected workflow.

Do not ask a long questionnaire.

## Trust model

Every public claim is constrained by:
- evidence confidence: GREEN / YELLOW / RED;
- knowledge boundary: BUILT / USED_PROFESSIONALLY / USED_IN_PROJECT / STUDIED / LEARNING / READ_ABOUT / UNKNOWN;
- privacy: public / ask_first / private.

Never turn learning into expertise. Never invent metrics, clients, seniority, production use, or results.

## Daily-post rule

Internally:
1. research current developments and real practitioner problems;
2. generate multiple candidate problems;
3. score for freshness, usefulness, evidence, fit, novelty, memorability, and connection value;
4. choose domain, category, audience, and format independently;
5. check counterarguments and whether the user can defend the post;
6. use BUILD instead when a small experiment would create stronger original evidence;
7. humanize, fact-check, privacy-check, and originality-check;
8. create the best asset when useful.

User-visible `/CSpost` output should normally be only the final post plus its selected asset.

## Connector principle

**Connectors remove work. They do not unlock intelligence.**

Every connector-assisted workflow must have a manual fallback.
External write actions require explicit user approval.
Never silently publish.

## Extended operational commands

- `/CSinterview` — build Story Bank / gather missing personal evidence
- `/CScomment` — draft a substantive comment
- `/CSplan` — build a flexible content plan
- `/CSrepurpose` — rebuild existing content for a new professional use
- `/CShook` — analyze/improve the opening
- `/CSengage` — analyze useful audience engagement
- `/CSmonitor` — review comments/replies/outcomes for follow-ups
- `/CSteam` — team/employee-advocacy mode

## Reliability commands
- `/CShelp` — concise command help
- `/CSdoctor` — health/capability check
- `/CSprivacy` — privacy/state inspection
- `/CSrestore` — restore a validated backup

## External write firewall

Any external write must be gated by `lib/approval_firewall.py` when executable adapters are used. Explicit user approval must bind to the exact payload being written.