alirezarezvani/onboard
c-level-advisor/c-level-agents/skills/onboard/SKILL.md
/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.
$ install --global
skillsauthnpx skillsauth add alirezarezvani/claude-skills onboardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 4:13 AM94.7s1 file scanned
SKILL.md
- 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)
The Interview (12 Questions)
Company Basics
- Company name and one-sentence pitch.
- Stage: pre-seed / seed / Series A / Series B / Series C+ / public
- Headcount: total, by function (eng / product / GTM / ops / G&A)
- Geographic distribution: HQ + remote split, key countries
Business Model
- Revenue model: SaaS subscription / usage / transaction / marketplace / hardware / services
- ICP: name one real customer and describe what they have in common with others
- ACV: median and range; deal count last 12 months
- Growth rate: ARR YoY; if pre-revenue, leading metric (users, MAU, etc.)
Financial Posture
- Runway: months of cash at current burn; bear-case months
- Last raise: amount, valuation, lead investor, date
Strategic Context
- Top 3 priorities for the current quarter (in plain language)
- 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 (../../../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
- Walk the founder through all 12 questions
- Quote founder's own words wherever possible (don't paraphrase the ICP)
- Save to
~/.claude/company-context.md - (Optional) If llm-wiki bridge is configured: symlink to vault
ln -sf ~/company-vault/00-meta/company-context.md ~/.claude/company-context.md - 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:boardroomfor 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 - Encrypted dotfile sync: age + git
- Shared team: keep in a private repo, symlink from
~/.claude/
Related
- Skill:
cs-onboard— the underlying interview protocol - Skill:
context-engine— reads this file - Reference:
../../references/llm-wiki-bridge.md
Version: 1.0.0
Related Skills
alirezarezvani/collab-proof
data-ai
VerifiedTrustedCommunity
Use when you want to understand what Claude contributed vs what you drove in a session. Triggers on: /collab-proof, session retrospective, ai contribution analysis, collaboration evidence, what did claude do.
17,936SKILL.mdUpdated Jun 13, 2026
alirezarezvani/claude-coach
data-ai
VerifiedTrustedCommunity
Personal coach that teaches users to become Claude power users. Use this skill the FIRST time a user asks to "learn Claude", "be a power user", "coach me", "teach me Claude tricks", "what can Claude do", "make me better at prompting", or any variation. After activation, also use it on EVERY subsequent turn to detect missed optimization opportunities (vague prompts, ignored capabilities, manual work Claude could automate) and surface a single power-user tip. Trigger generously — most users do not know what they do not know, so err on the side of coaching.
17,936SKILL.mdUpdated May 23, 2026
alirezarezvani/pricing-strategist
development
VerifiedTrustedCommunity
Use when designing or revisiting product pricing — selecting a pricing model (subscription seat-based, usage-based, value-based, freemium, or hybrid), running Van Westendorp Price Sensitivity Meter analysis on WTP survey data, or designing Good/Better/Best packaging tiers. Recommends a model and a price range with trade-offs, never a single number. For Commercial leads, Product Marketing, and CMOs at the pricing-design moment — not deal-by-deal discounting, not brand positioning.
17,936SKILL.mdUpdated May 20, 2026
alirezarezvani/partnerships-architect
testing
VerifiedTrustedCommunity
Use when a startup is approached by a prospective partner and someone has to decide should we sign this partner, at what partner tier (referral / reseller / OEM / SI-consulting / strategic alliance), with what joint GTM commitment, and at what revshare. Classifies partner tier from independent-demand evidence vs. preferential-terms hunting, designs a 90-day joint GTM plan, models revshare against direct-sale margin, and surfaces kill criteria for unwinding under-performing partnerships. For Head of Partnerships, Head of BD, and Founder-CEOs doing reseller agreement, OEM deal, or strategic alliance review — not technical sale enablement, not channel cost economics, not M&A.
17,936SKILL.mdUpdated May 20, 2026