c-level-advisor/c-level-agents/skills/c-level-agents/SKILL.md
Founder-mode executive team. 13 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, GC, CDO, CAIO, CCO, VPE, Chief of Staff) and 21 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions.
npx skillsauth add alirezarezvani/claude-skills c-level-agentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A virtual C-suite delivered through slash commands and persona agents.
founder mode, virtual c-suite, executive team, boardroom, office hours, cfo review, cmo review, strategic sprint, decision logging, cross-model consensus, persona agents, chief of staff, forcing questions
agents/)Each agent wraps an existing c-level skill and adds:
See ../../references/persona-voices.md for voice specs.
skills/)Forcing-question office hours (12):
/cs:office-hours — YC-style 6-question intake/cs:cfo-review — unit economics, runway, dilution/cs:cmo-review — ICP, CAC payback, positioning/cs:cpo-review — RICE, JTBD, North Star, PMF/cs:cro-review — pipeline coverage, win rate, NRR/cs:cto-review — architecture risk, scaling cliff/cs:ciso-review — threat model, blast radius, compliance/cs:gc-review — contracts, IP, regulatory, term sheets/cs:cdo-review — training-data rights, data products, data assets/cs:caio-review — model selection, evals, AI risk, AI costs/cs:cco-review — GRR/NRR decomposition, churn root cause, CS coverage/cs:vpe-review — DORA metrics, cycle time, eng hiring funnel, team structureStrategic sprint pipeline (5):
/cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortemMeta + safety (4):
/cs:founder-mode — auto-routes to the right C-role/cs:onboard — founder interview → company-context.md/cs:cross-eval — multi-model consensus/cs:freeze — cooldown lock on a decision/cs:onboard # populate company context first
/cs:office-hours "should we hire a VP Sales?"
/cs:founder-mode "runway pressure" # auto-routes to CFO
/cs:boardroom briefs/pricing-v3.md # full panel
User question
│
├─ Single-role? → cs-{role}-advisor agent
│ ↓
│ /cs:{role}-review command (forcing Qs)
│ ↓
│ Skill tools + references
│ ↓
│ Bottom Line + Memo
│
└─ Multi-role? → /cs:boardroom
↓
6-phase deliberation (Phase 2 isolation)
↓
/cs:decide → decision-logger (two-layer memory)
↓
/cs:execute → 90-day plan
/cs:decide writes here/cs:boardroom command runs../../references/llm-wiki-bridge.md)/em:* commands stack cleanly on top/cs:cross-eval falls back to Claude-only.Version: 1.0.0 Last Updated: 2026-05-12 Status: Production Ready
data-ai
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.
data-ai
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.
development
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.
testing
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.