New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

/cs:onboard — Founder interview that populates

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

/cs:onboard — Founder Interview cover

/cs:onboard — Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema. The first command to run when starting with c-level-agents.

---
name: "onboard"
description: "/cs:onboard — Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema. The first command to run when starting with c-level-agents. Use when setting up the virtual C-suite for a new company, or when advisors lack company context — e.g. before a first /cs:boardroom or after a fundraise changes the numbers."
---

# /cs:onboard — Founder Interview

**Command:** `/cs:onboard`

The first command to run when adopting c-level-agents. A structured founder interview that produces `~/.claude/company-context.md` — the file every cs-* advisor reads before responding. Without this, the advisors are guessing.

## What This Produces

`~/.claude/company-context.md` — a single file with the durable facts about the company. Read by:
- `cs-chief-of-staff` (routing decisions)
- Every cs-* advisor (context for any question)
- `/cs:brief` (assumptions in any new decision)

Overview

The first command to run when adopting c-level-agents. A structured founder interview that produces ~/.claude/company-context.md — the file every cs-* advisor reads before responding. Without this, the advisors are guessing.

Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill onboard -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \ | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/c-level-agents/skills/onboard
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/3e5a9b0b13548de98309/onboard.zip" -OutFile "$env:TEMP\onboard.zip"; Expand-Archive "$env:TEMP\onboard.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md5.0 KB
Read the files here
alirezarezvani/19392f71 file
Shared references4SKILL.md reads these from elsewhere in the repo. Not in the ZIP.Get them on GitHub ↗
SKILL.md
Show the full text127 lines

/cs:onboard — Founder Interview

Command: /cs:onboard

The first command to run when adopting c-level-agents. A structured founder interview that produces ~/.claude/company-context.md — the file every cs-* advisor reads before responding. Without this, the advisors are guessing.

What This Produces

~/.claude/company-context.md — a single file with the durable facts about the company. Read by:

  • cs-chief-of-staff (routing decisions)
  • Every cs-* advisor (context for any question)
  • /cs:brief (assumptions in any new decision)

The Interview (12 Questions)

Company Basics
  1. Company name and one-sentence pitch.
  2. Stage: pre-seed / seed / Series A / Series B / Series C+ / public
  3. Headcount: total, by function (eng / product / GTM / ops / G&A)
  4. Geographic distribution: HQ + remote split, key countries
Business Model
  1. Revenue model: SaaS subscription / usage / transaction / marketplace / hardware / services
  2. ICP: name one real customer and describe what they have in common with others
  3. ACV: median and range; deal count last 12 months
  4. Growth rate: ARR YoY; if pre-revenue, leading metric (users, MAU, etc.)
Financial Posture
  1. Runway: months of cash at current burn; bear-case months
  2. Last raise: amount, valuation, lead investor, date
Strategic Context
  1. Top 3 priorities for the current quarter (in plain language)
  2. Top 3 risks the founder loses sleep over (be specific)

Output Format

Canonical schema: ~/.claude/company-context.md is owned by the cs-onboard skill and follows its 7-dimension schema (../../../c-level-advisor/skills/cs-onboard/templates/company-context-template.md): Company Identity, Stage & Scale, Founder Profile, Team & Culture, Market & Competition, Current Challenges, Goals & Ambition. The 12 questions above are a faster structured intake that populates that same file — Identity/Business/Financial → Stage & Scale, Team → Team & Culture, Quarter priorities/risks → Current Challenges + Goals & Ambition. Write [not captured] for dimensions the quick intake doesn't reach (Founder Profile, Market & Competition); run the full cs-onboard interview to fill them. Never create a second context file or a divergent layout.

The intake summary captured by the 12 questions:

# Company Context
**Generated:** YYYY-MM-DD
**Last updated:** YYYY-MM-DD

## Identity
- **Company:** <name>
- **Pitch:** <one sentence>
- **Stage:** <stage>
- **HQ + remote:** <distribution>

## Business
- **Model:** <type>
- **ICP:** <description + named customer>
- **ACV:** $<median> (range $<low> - $<high>)
- **Deal count (LTM):** N
- **ARR growth (YoY):** X%

## Financial
- **Cash on hand:** $<amount>
- **Net burn (monthly):** $<amount>
- **Runway base:** N months
- **Runway bear:** N months
- **Last raise:** $<amount> at $<post> in <month YYYY>, led by <investor>

## Team
- **Total headcount:** N
- **Eng:** N | Product: N | GTM: N | Ops: N | G&A: N

## Quarter
- **Top priorities (Q<X> YYYY):**
  1. <priority>
  2. <priority>
  3. <priority>

- **Top risks:**
  1. <risk>
  2. <risk>
  3. <risk>

## Routing Hints
[Optional: any role the founder wants to use sparingly or rely on heavily]

Workflow

  1. Walk the founder through all 12 questions
  2. Quote founder's own words wherever possible (don't paraphrase the ICP)
  3. Save to ~/.claude/company-context.md
  4. (Optional) If llm-wiki bridge is configured: symlink to vault
    ln -sf ~/company-vault/00-meta/company-context.md ~/.claude/company-context.md
    
  5. Confirm with founder: read the file back, ask "anything missing?"

When to Re-Run

  • After a fundraise (numbers change)
  • After a major pivot or product launch
  • After 6+ months (most facts have drifted)
  • After a major hire (team distribution changes)
  • Always before a /cs:boardroom for a high-stakes decision

Persistence

By default, ~/.claude/company-context.md is local to the founder's machine. To make it persistent across machines / shareable:


Version: 1.0.0

1---
2name: "onboard"
3description: "/cs:onboard — Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema. The first command to run when starting with c-level-agents. Use when setting up the virtual C-suite for a new company, or when advisors lack company context — e.g. before a first /cs:boardroom or after a fundraise changes the numbers."
4---
5 
6# /cs:onboard — Founder Interview
7 
8**Command:** `/cs:onboard`
9 
10The first command to run when adopting c-level-agents. A structured founder interview that produces `~/.claude/company-context.md` — the file every cs-* advisor reads before responding. Without this, the advisors are guessing.
11 
12## What This Produces
13 
14`~/.claude/company-context.md` — a single file with the durable facts about the company. Read by:
15- `cs-chief-of-staff` (routing decisions)
16- Every cs-* advisor (context for any question)
17- `/cs:brief` (assumptions in any new decision)
18 
19## The Interview (12 Questions)
20 
21### Company Basics
221. **Company name and one-sentence pitch.**
232. **Stage:** pre-seed / seed / Series A / Series B / Series C+ / public
243. **Headcount:** total, by function (eng / product / GTM / ops / G&A)
254. **Geographic distribution:** HQ + remote split, key countries
26 
27### Business Model
285. **Revenue model:** SaaS subscription / usage / transaction / marketplace / hardware / services
296. **ICP:** name one real customer and describe what they have in common with others
307. **ACV:** median and range; deal count last 12 months
318. **Growth rate:** ARR YoY; if pre-revenue, leading metric (users, MAU, etc.)
32 
33### Financial Posture
349. **Runway:** months of cash at current burn; bear-case months
3510. **Last raise:** amount, valuation, lead investor, date
36 
37### Strategic Context
3811. **Top 3 priorities for the current quarter** (in plain language)
3912. **Top 3 risks the founder loses sleep over** (be specific)
40 
41## Output Format
42 
43**Canonical schema:** `~/.claude/company-context.md` is owned by the [`cs-onboard`](../../../c-level-advisor/skills/cs-onboard/SKILL.md) skill and follows its 7-dimension schema (`../../../c-level-advisor/skills/cs-onboard/templates/company-context-template.md`): Company Identity, Stage & Scale, Founder Profile, Team & Culture, Market & Competition, Current Challenges, Goals & Ambition. The 12 questions above are a faster structured intake that populates that same file — Identity/Business/Financial → Stage & Scale, Team → Team & Culture, Quarter priorities/risks → Current Challenges + Goals & Ambition. Write `[not captured]` for dimensions the quick intake doesn't reach (Founder Profile, Market & Competition); run the full `cs-onboard` interview to fill them. Never create a second context file or a divergent layout.
44 
45The intake summary captured by the 12 questions:
46 
47```markdown
48# Company Context
49**Generated:** YYYY-MM-DD
50**Last updated:** YYYY-MM-DD
51 
52## Identity
53- **Company:** <name>
54- **Pitch:** <one sentence>
55- **Stage:** <stage>
56- **HQ + remote:** <distribution>
57 
58## Business
59- **Model:** <type>
60- **ICP:** <description + named customer>
61- **ACV:** $<median> (range $<low> - $<high>)
62- **Deal count (LTM):** N
63- **ARR growth (YoY):** X%
64 
65## Financial
66- **Cash on hand:** $<amount>
67- **Net burn (monthly):** $<amount>
68- **Runway base:** N months
69- **Runway bear:** N months
70- **Last raise:** $<amount> at $<post> in <month YYYY>, led by <investor>
71 
72## Team
73- **Total headcount:** N
74- **Eng:** N | Product: N | GTM: N | Ops: N | G&A: N
75 
76## Quarter
77- **Top priorities (Q<X> YYYY):**
78 1. <priority>
79 2. <priority>
80 3. <priority>
81 
82- **Top risks:**
83 1. <risk>
84 2. <risk>
85 3. <risk>
86 
87## Routing Hints
88[Optional: any role the founder wants to use sparingly or rely on heavily]
89```
90 
91## Workflow
92 
931. Walk the founder through all 12 questions
942. Quote founder's own words wherever possible (don't paraphrase the ICP)
953. Save to `~/.claude/company-context.md`
964. (Optional) If llm-wiki bridge is configured: symlink to vault
97 ```bash
98 ln -sf ~/company-vault/00-meta/company-context.md ~/.claude/company-context.md
99 ```
1005. Confirm with founder: read the file back, ask "anything missing?"
101 
102## When to Re-Run
103 
104- After a fundraise (numbers change)
105- After a major pivot or product launch
106- After 6+ months (most facts have drifted)
107- After a major hire (team distribution changes)
108- Always before a `/cs:boardroom` for a high-stakes decision
109 
110## Persistence
111 
112By default, `~/.claude/company-context.md` is local to the founder's machine. To make it persistent across machines / shareable:
113 
114- **Markdown vault (recommended):** see [`../../references/llm-wiki-bridge.md`](../../references/llm-wiki-bridge.md)
115- **Encrypted dotfile sync:** age + git
116- **Shared team:** keep in a private repo, symlink from `~/.claude/`
117 
118## Related
119 
120- Skill: [`cs-onboard`](../../../c-level-advisor/skills/cs-onboard/SKILL.md) — the underlying interview protocol
121- Skill: [`context-engine`](../../../c-level-advisor/skills/context-engine/SKILL.md) — reads this file
122- Reference: [`../../references/llm-wiki-bridge.md`](../../references/llm-wiki-bridge.md)
123 
124---
125 
126**Version:** 1.0.0
127 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillExtracting first-party expertise from a subject-matterExpert interviewinhouseseo/superseo-skills · by inhouseseoUse when extracting first-party expertise from a subject-matter expert before writing content. Produces a knowledge document of contrarian takes, specific examples, and surprising outcomes that AI can't fabricate.★ 353 GitHub starsSkillStart of the UGC pipeline for persona researchPersona & ScriptTheMattBerman/scrollclaw · by TheMattBermanStart of the UGC pipeline for persona research, creator profiles, format selection, and scriptwriting. Use when the user is clearly asking for messaging work rather than broad full-pipeline orchestration.★ 71 GitHub starsSkillTell us who you need answers from and what you're missingTo questionnairemattpocock/skills · by mattpocockTell us who you need answers from and what you're missing; get back a clean form you send them to fill in.★ 267k GitHub starsSkillExtracts what the user actually wants instead of what theyInterview meaddyosmani/agent-skills · by addyosmaniExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.★ 98.7k GitHub starsSkillMarketes psychology & mental modelsMarketing Psychology & Mental Modelscoreyhaines31/marketingskills · by coreyhaines31When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.★ 51.1k GitHub stars

More from alirezarezvani

SkillResume a paused experiment/ar:ar-resume — Resume Experimentalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars