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 for /cs-onboard, or when the virtual C-suite lacks company context. Interviews the founder and writes ~/.claude/company-context.md.
Claude Code
$ npx -y skills add alirezarezvani/claude-skills --skill onboard --agent claude-code
Codex
$ npx skills add alirezarezvani/claude-skills --skill onboard -a codex -y
Cursor
$ npx skills add alirezarezvani/claude-skills --skill onboard -a cursor -y
Gemini CLI
$ npx skills add alirezarezvani/claude-skills --skill onboard -a gemini-cli -y
GitHub Copilot
$ npx skills add alirezarezvani/claude-skills --skill onboard -a github-copilot -y
OpenCode
$ npx skills add alirezarezvani/claude-skills --skill onboard -a opencode -y
Windsurf
$ npx skills add alirezarezvani/claude-skills --skill onboard -a windsurf -y
name: "onboard" description: "Use for /cs-onboard, or when the virtual C-suite lacks company context. Interviews the founder and writes ~/.claude/company-context.md."
**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.
`~/.claude/company-context.md` — a single file with the durable facts about the company. Read by:
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
5. **Revenue model:** SaaS subscription / usage / transaction / marketplace / hardware / services 6. **ICP:** name one real customer and describe what they have in common with others 7. **ACV:** median and range; deal count last 12 months 8. **Growth rate:** ARR YoY; if pre-revenue, leading metric (users, MAU, etc.)
9. **Runway:** months of cash at current burn; bear-case months 10. **Last raise:** amount, valuation, lead investor, date
11. **Top 3 priorities for the current quarter** (in plain language) 12. **Top 3 risks the founder loses sleep over** (be specific)
**Canonical schema:** `~/.claude/company-context.md` is owned by the [`cs-onboard`](${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/cs-onboard/SKILL.md) skill and follows its 7-dimension schema (`${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/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]
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?"
By default, `~/.claude/company-context.md` is local to the founder's machine. To make it persistent across machines / shareable:
---
**Version:** 1.0.0
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…