agent-launcher-orchest…
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use when setting up the C-suite advisors for the first time, or when company context is missing or stale after a raise or pivot. Interviews the founder across 7 dimensions and writes ~/.claude/company-context.md.
Claude Code
$ npx -y skills add alirezarezvani/claude-skills --skill cs-onboard --agent claude-code
Codex
$ npx skills add alirezarezvani/claude-skills --skill cs-onboard -a codex -y
Cursor
$ npx skills add alirezarezvani/claude-skills --skill cs-onboard -a cursor -y
Gemini CLI
$ npx skills add alirezarezvani/claude-skills --skill cs-onboard -a gemini-cli -y
GitHub Copilot
$ npx skills add alirezarezvani/claude-skills --skill cs-onboard -a github-copilot -y
OpenCode
$ npx skills add alirezarezvani/claude-skills --skill cs-onboard -a opencode -y
Windsurf
$ npx skills add alirezarezvani/claude-skills --skill cs-onboard -a windsurf -y
name: "cs-onboard" description: "Use when setting up the C-suite advisors for the first time, or when company context is missing or stale after a raise or pivot. Interviews the founder across 7 dimensions and writes ~/.claude/company-context.md." 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
Structured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.
cs:setup, cs:update, company context, founder interview, onboarding, company profile, c-suite setup, advisor setup
---
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?"*
---
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.
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?"*
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.
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."
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."
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.
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?"*
---
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."*
---
**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`.
---
`~/.claude/company-context.md` — single source of truth for all C-suite skills. Do not move it. Do not create duplicates.
411 production-ready skills for Claude Code and 12 other coding agents, covering engineering, product, marketing, compliance, finance and the C-suite. We test whether each skill loads when you ask in plain words, and publish the results.
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use when a launched managed agent needs grading against a rubric and improving ('grade my agent', 'is it good enough'). Builds…
Use when someone has an agent idea to scope before launch ('help me scope an agent'). Interviews them about the one job and…
Use when a graded managed agent should run on a schedule, on an event trigger or on demand ('run it every morning'). Validates…
Use when a managed-agent build sheet is ready to launch ('launch it', 'deploy the agent'). Generates and validates API payloads…
Use when closing out a launched managed agent ('wrap up', 'what do I own now'). Inventories primitives with…
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI…