C Level Advisor
Install this when you need a virtual C-suite and Chief of Staff routing for strategic questions, runway-aware advice, and multi-role /cs:board meetings from company-context.md.
Overview
c-level-advisor is a journey-wide agent skill that simulates a C-level advisory board and routes founder strategy questions—usable whenever a solo builder needs executive-level framing before committing to product, GTM,
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill c-level-advisorWhat is this skill?
- Ten C-level advisory roles (CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor) plus Chief of Staff routing
- /cs:setup questionnaire writes company-context.md that all agents read
- /cs:board runs multi-role board meetings with verification that at least three roles weigh in
- Metadata cites 28 skills, 25 scripts, and 52 references in the advisory ecosystem
- Structured recommendations for founders needing executive-level decision support without a full board
- 28 skills_count in metadata
- 25 scripts_count in metadata
- 52 references_count in metadata
Adoption & trust: 1.8k installs on skills.sh; 17.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are making founder-level calls alone and lack structured pushback from finance, security, product, and revenue viewpoints.
Who is it for?
Pre-seed through Series B+ founders who want board-style rigor on strategy, spend, security, and org decisions inside their agent.
Skip if: Builders who only need code snippets, or operators with an engaged human board and no desire for simulated executive personas.
When should I use this skill?
You need executive-level strategic answers, role routing, or a multi-role /cs:board after company-context.md exists from /cs:setup.
What do I get? / Deliverables
You get company-context-aware routing, role-specific recommendations, and for major bets a multi-role board transcript after /cs:setup—with explicit confirmation that multiple roles contributed.
- company-context.md
- Role-routed recommendation
- Multi-role board meeting synthesis
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
After /cs:setup, ask the Chief of Staff to stress-test positioning for your stated stage and runway.
Route a pricing change to CFO and CRO lenses before you publish new plans.
Pull CISO guidance before a major release handling customer data.
Use CMO framing for channel spend versus measurable launch goals.
Run /cs:board when choosing between hiring, infra spend, or feature velocity.
How it compares
Executive decision workflow with shared company-context—not a single-domain checker like linting or a passive docs MCP.
Common Questions / FAQ
Who is c-level-advisor for?
Founders and solo leaders who want CEO/CTO/CFO/CISO-style perspectives and coordinated routing without hiring a full executive bench.
When should I use c-level-advisor?
At Idea when framing market and stage; at Validate when pricing and scope affect runway; before Ship/Launch on risk and resourcing; and in Grow/Operate when GTM, security, and people decisions compound—especially after /cs:setup.
Is c-level-advisor safe to install?
Use the Security Audits panel on this Prism page and avoid placing live secrets in company-context.md; simulated executives do not replace legal, financial, or compliance professionals.
SKILL.md
READMESKILL.md - C Level Advisor
# C-Level Advisory Ecosystem A complete virtual board of directors for founders and executives. ## Quick Start ``` 1. Run /cs:setup → creates company-context.md (all agents read this) ✓ Verify company-context.md was created and contains your company name, stage, and core metrics before proceeding. 2. Ask any strategic question → Chief of Staff routes to the right role 3. For big decisions → /cs:board triggers a multi-role board meeting ✓ Confirm at least 3 roles have weighed in before accepting a conclusion. ``` ### Commands #### `/cs:setup` — Onboarding Questionnaire Walks through the following prompts and writes `company-context.md` to the project root. Run once per company or when context changes significantly. ``` Q1. What is your company name and one-line description? Q2. What stage are you at? (Idea / Pre-seed / Seed / Series A / Series B+) Q3. What is your current ARR (or MRR) and runway in months? Q4. What is your team size and structure? Q5. What industry and customer segment do you serve? Q6. What are your top 3 priorities for the next 90 days? Q7. What is your biggest current risk or blocker? ``` After collecting answers, the agent writes structured output: ```markdown # Company Context - Name: <answer> - Stage: <answer> - Industry: <answer> - Team size: <answer> - Key metrics: <ARR/MRR, growth rate, runway> - Top priorities: <answer> - Key risks: <answer> ``` #### `/cs:board` — Full Board Meeting Convenes all relevant executive roles in three phases: ``` Phase 1 — Framing: Chief of Staff states the decision and success criteria. Phase 2 — Isolation: Each role produces independent analysis (no cross-talk). Phase 3 — Debate: Roles surface conflicts, stress-test assumptions, align on a recommendation. Dissenting views are preserved in the log. ``` Use for high-stakes or cross-functional decisions. Confirm at least 3 roles have weighed in before accepting a conclusion. ### Chief of Staff Routing Matrix When a question arrives without a role prefix, the Chief of Staff maps it to the appropriate executive using these primary signals: | Topic Signal | Primary Role | Supporting Roles | |---|---|---| | Fundraising, valuation, burn | CFO | CEO, CRO | | Architecture, build vs. buy, tech debt | CTO | CPO, CISO | | Hiring, culture, performance | CHRO | CEO, Executive Mentor | | GTM, demand gen, positioning | CMO | CRO, CPO | | Revenue, pipeline, sales motion | CRO | CMO, CFO | | Security, compliance, risk | CISO | CTO, CFO | | Product roadmap, prioritisation | CPO | CTO, CMO | | Ops, process, scaling | COO | CFO, CHRO | | Vision, strategy, investor relations | CEO | Executive Mentor | | Career, founder psychology, leadership | Executive Mentor | CEO, CHRO | | Multi-domain / unclear | Chief of Staff convenes board | All relevant roles | ### Invoking a Specific Role Directly To bypass Chief of Staff routing and address one executive directly, prefix your question with the role name: ``` CFO: What is our optimal burn rate heading into a Series A? CTO: Should we rebuild our auth layer in-house or buy a solution? CHRO: How do we design a performance review process for a 15-person team? ``` The Chief of Staff still logs the exchange; only routing is skipped. ### Example: Strategic Question **Input:** "Should we raise a Series A now or extend runway and grow ARR first?" **Output format:** - **Bottom Line:** Extend runway 6 months; raise at $2M ARR