cs-onboard — Claude Code skill: what it does, how to install
Runs a 7-part founder interview and saves company context for C-suite skills. Use it for initial setup or a context refresh after major changes.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install c-level-skills@claude-code-skillsWhat cs-onboard does
cs-onboard interviews the founder across 7 areas: company identity, stage and scale, founder profile, team and culture, market and competition, current challenges, and goals. Run /cs-onboard setup for the initial interview, which takes about 45 minutes. Run /cs-onboard update for a refresh that takes about 15 minutes and focuses on what changed.
After the interview, the skill creates ~/.claude/company-context.md from templates/company-context-template.md. C-suite skills use this file as shared company context, and the file should stay at that path without duplicates. You need Claude Code and the installed skill. Install cs-onboard when advisor skills need one current company profile; skip it for a one-off conversation without saved context.
What it helps with
- build a company profile for advisor skills
- run a structured founder interview
- capture goals, challenges, and business stage
- refresh context after a company change
- save shared context for C-suite advisors
Example prompts for the agent
- Run `/cs-onboard setup` and interview me about the company.
- Run `/cs-onboard update` and refresh the context after our latest changes.
- Create `~/.claude/company-context.md` from the interview.
How to install cs-onboard
1Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install c-level-skills@claude-code-skillsThis installs the whole c-level-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add alirezarezvani/claude-skills --skill cs-onboard -a claude-code3Manually: put the files in place
~/.claude/skills/cs-onboard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cs-onboard/
Manually: put the files in place
.agents/skills/cs-onboard/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/cs-onboard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install alirezarezvani/claude-skills cs-onboard2Manually: put the files in place
.github/skills/cs-onboard/SKILL.mdPlatform CLI
gemini skills install https://github.com/alirezarezvani/claude-skills --path c-level-advisor/skills/cs-onboardManually: put the files in place
.devin/skills/cs-onboard/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set349
The whole set →Similar
Questions about cs-onboard
How do I install cs-onboard in Claude Code?
Run npx skills add alirezarezvani/claude-skills --skill cs-onboard -a claude-code.
What does cs-onboard do?
The skill interviews a founder across 7 areas and creates ~/.claude/company-context.md for C-suite advisor skills.
What is the difference between setup and update?
/cs-onboard setup starts the initial interview and takes about 45 minutes. /cs-onboard update runs a roughly 15-minute refresh after changes or 90 days.
Source text
SKILL.md · MIT
--- name: "cs-onboard" description: "Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs-onboard setup for initial interview or /cs-onboard update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old — e.g. after a fundraise or pivot." license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: c-level domain: orchestration updated: 2026-03-05 frameworks: founder-interview, context-capture, quarterly-refresh --- # C-Suite Onboarding Structured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles. ## Commands - `/cs-onboard setup` — Full onboarding interview (~45 min, 7 dimensions) - `/cs-onboard update` — Quarterly refresh (~15 min, "what changed?") ## Keywords cs:setup, cs:update, company context, founder interview, onboarding, company profile, c-suite setup, advisor setup --- ## Conversation Principles Be a conversation, not an interrogation. Ask one question at a time. Follow threads. Reflect back: "So the real issue sounds like X — is that right?" Watch for what they skip — that's where the real story lives. Never read a list of questions. Open with: *"Tell me about the company in your own words — what are you building and why does it matter?"* --- ## 7 Interview Dimensions ### 1. Company Identity Capture: what they do, who it's for, the real founding "why," one-sentence pitch, non-negotiable values. Key probe: *"What's a value you'd fire someone over violating?"* Red flag: Values that sound like marketing copy. ### 2. Stage & Scale Capture: headcount (FT vs contractors), revenue range, runway, stage (pre-PMF / scaling / optimizing), what broke in last 90 days. Key probe: *"If you had to label your stage — still finding PMF, scaling what works, or optimizing?"* ### 3. Founder Profile Capture: self-identified superpower, acknowledged blind spots, archetype (product/sales/technical/operator), what actually keeps them up at night. Key probe: *"What would your co-founder say you should stop doing?"* Red flag: No blind spots, or weakness framed as a strength. ### 4. Team & Culture Capture: team in 3 words, last real conflict and resolution, which values are real vs aspirational, strongest and weakest leader. Key probe: *"Which of your stated values is most real? Which is a poster on the wall?"* Red flag: "We have no conflict." ### 5. Market & Competition Capture: who's winning and why (honest version), real unfair advantage, the one competitive move that could hurt them. Key probe: *"What's your real unfair advantage — not the investor version?"* Red flag: "We have no real competition." ### 6. Current Challenges Capture: priority stack-rank across product/growth/people/money/operations, the decision they've been avoiding, the "one extra day" answer. Key probe: *"What's the decision you've been putting off for weeks?"* Note: The "extra day" answer reveals true priorities. ### 7. Goals & Ambition Capture: 12-month target (specific), 36-month target (directional), exit vs build-forever orientation, personal success definition. Key probe: *"What does success look like for you personally — separate from the company?"* --- ## Output: company-context.md After the interview, generate `~/.claude/company-context.md` using `templates/company-context-template.md`. Fill every section. Write `[not captured]` for unknowns — never leave blank. Add timestamp, mark as `fresh`. Tell the founder: *"I've captured everything in your company context. Every advisor will use this to give specific, relevant advice. Run /cs-onboard update in 90 days to keep it current."* --- ## /cs-onboard update — Quarterly Refresh **Trigger:** Every 90 days or after a major change. Duration: ~15 minutes. Open with: *"It's been [X time] since we did your company context. What's changed?"* Walk each dimension with one "what changed?" question: 1. Identity: same mission or shifted? 2. Scale: team, revenue, runway now? 3. Founder: role or what's stretching you? 4. Team: any leadership changes? 5. Market: any competitive surprises? 6. Challenges: #1 problem now vs 90 days ago? 7. Goals: still on track for 12-month target? Update the context file, refresh timestamp, reset to `fresh`. --- ## Context File Location `~/.claude/company-context.md` — single source of truth for all C-suite skills. Do not move it. Do not create duplicates. ## References - `templates/company-context-template.md` — blank template for output - `references/interview-guide.md` — deep interview craft: probes, red flags, handling reluctant founders
© Alireza Rezvani · MIT · alirezarezvani/claude-skills