onboard
/cs:onboard — Founder interview that populates ~/.claude/company-context.md. The first command to run when starting with c-level-agents.
What this skill does
# /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 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.) ### Financial Posture 9. **Runway:** months of cash at current burn; bear-case months 10. **Last raise:** amount, valuation, lead investor, date ### Strategic Context 11. **Top 3 priorities for the current quarter** (in plain language) 12. **Top 3 risks the founder loses sleep over** (be specific) ## Output Format Saved to `~/.claude/company-context.md`: ```markdown # 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 ```bash 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: - **Markdown vault (recommended):** see [`../../references/llm-wiki-bridge.md`](../../references/llm-wiki-bridge.md) - **Encrypted dotfile sync:** age + git - **Shared team:** keep in a private repo, symlink from `~/.claude/` ## Related - Skill: [`cs-onboard`](../../../skills/cs-onboard/SKILL.md) — the underlying interview protocol - Skill: [`context-engine`](../../../skills/context-engine/SKILL.md) — reads this file - Reference: [`../../references/llm-wiki-bridge.md`](../../references/llm-wiki-bridge.md) --- **Version:** 1.0.0
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.