cs-onboard
Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.
Best use case
cs-onboard is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.
Teams using cs-onboard should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cs-onboard/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cs-onboard Compares
| Feature / Agent | cs-onboard | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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:setup` — Full onboarding interview (~45 min, 7 dimensions) - `/cs: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:update in 90 days to keep it current."* --- ## /cs: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
Related Skills
gtm-enterprise-onboarding
Four-phase framework for onboarding enterprise customers from contract to value realization. Use when implementing new enterprise customers, preventing churn during onboarding, or solving the adoption cliff that kills deals post-go-live. Includes the Week 4 ghosting pattern.
wiki-onboarding
Generates two complementary onboarding guides — a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation for a codebase.
git-pr-workflows-onboard
You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You
onboard
Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly.
onboarding-helper
Generate comprehensive onboarding documentation and guides for new developers joining your team o...
onboarding-cro
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
codebase-onboarding
分析一个陌生的代码库,并生成一个结构化的入门指南,包括架构图、关键入口点、规范和一个起始的CLAUDE.md文件。适用于加入新项目或首次在代码仓库中设置Claude Code时。
/understand-onboard
Generate a comprehensive onboarding guide from the project's knowledge graph.
onboarding-optimization
When the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy.
Daily Logs
Record the user's daily activities, progress, decisions, and learnings in a structured, chronological format.
Socratic Method: The Dialectic Engine
This skill transforms Claude into a Socratic agent — a cognitive partner who guides
Sokratische Methode: Die Dialektik-Maschine
Dieser Skill verwandelt Claude in einen sokratischen Agenten — einen kognitiven Partner, der Nutzende durch systematisches Fragen zur Wissensentdeckung führt, anstatt direkt zu instruieren.