c-level-advisor/skills/c-level-skills/SKILL.md
Index and router for the C-level advisory bundle: 33 skills covering 14 C-suite roles, orchestration, cross-cutting capabilities, and culture. Use when exploring what the c-level-advisor bundle contains, deciding which advisor skill fits a question, or finding the entry points (cs-onboard interview, chief-of-staff routing, board-meeting protocol).
npx skillsauth add alirezarezvani/claude-skills c-level-skillsInstall 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.
This is the bundle index, not an advisor. It tells you what exists and where to start; the skills below do the work.
cs-onboard skill runs the founder interview (/cs:setup, 7 dimensions, ~45 min) and writes ~/.claude/company-context.md. Refresh quarterly with /cs:update. This is the canonical context schema every advisor reads.chief-of-staff skill routes any question to the right advisor(s). See its routing matrix for all 14 roles.board-meeting skill runs a 6-phase deliberation: (1) context gathering → (2) independent contributions (isolated) → (3) critic analysis → (4) synthesis → (5) founder review (full stop) → (6) decision extraction. Invoked via /cs:boardroom in the c-level-agents plugin.~/.claude/decisions/{raw,approved}/ (see ../agent-protocol/SKILL.md → "Decision Memory (Canonical Layout)").14 C-suite roles + critic (15): ceo-advisor, cfo-advisor, cto-advisor, coo-advisor, cpo-advisor, cmo-advisor, cro-advisor, ciso-advisor, chro-advisor, general-counsel-advisor, chief-data-officer-advisor, chief-ai-officer-advisor, chief-customer-officer-advisor, vpe-advisor — plus the executive-mentor critic (sibling plugin).
Orchestration (6): cs-onboard, chief-of-staff, board-meeting, decision-logger, agent-protocol, context-engine.
Cross-cutting (6): board-deck-builder, scenario-war-room, competitive-intel, org-health-diagnostic, ma-playbook, intl-expansion.
Culture & collaboration (6): culture-architect, company-os, founder-coach, strategic-alignment, change-management, internal-narrative.
Plus this index (1). 37 stdlib-only Python tools and 68 reference docs across the bundle.
Full matrix in ../chief-of-staff/SKILL.md and ../chief-of-staff/references/routing-matrix.md. Primary roles: CFO (capital/burn), CRO (pipeline/sales), CMO (positioning), CPO (roadmap/PMF), CTO (architecture), COO (ops/OKRs), CHRO (people), CISO (security), GC (contracts/term sheets), CDO (data strategy/training-data rights), CAIO (AI strategy/evals), CCO (retention/GRR), VPE (delivery/DORA), CEO (direction). Multi-domain or irreversible → board meeting.
../../c-level-agents/ — 13 cs-* persona agents + 21 /cs:* slash commands on top of these skills../../executive-mentor/ — adversarial /em:* critic commands../../CLAUDE.md — full architecture diagram and integration guidedevelopment
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.