agent-launcher-orchest…
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a…
/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
$ npx -y skills add alirezarezvani/claude-skills --skill onboard --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/onboardContext preview
The summary Claude sees to decide when to auto-load this skill.
/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
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."
**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`](../../../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.
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
388 production-ready Claude Code skills, plugins, and agent skills for 13 AI coding tools. The most comprehensive open-source library of Claude Code skills and agent plugins — also works with OpenAI Codex, Gemini CLI, Cursor, and 9 more coding agents.
Repo: alirezarezvani/claude-skills
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a…
Phase 3 of building a Claude Managed Agent — the bounded grade→iterate loop. Define a CMA outcome (a required markdown rubric graded by an isolated grader),…
Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table +…
Phase 4 of building a Claude Managed Agent — make it run without you. Turn a graded agent into a recurring scheduled deployment (POSIX-cron), an event-driven…
Phase 2 of building a Claude Managed Agent — turn a validated build sheet into exact API payloads and a resumable BYOK curl launch script, then launch…
Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2…