ceo-advisor
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.
1How It Works & Mechanism
The core prompt asset is structured around 'CEO Responsibility Framework + Quantitative Dashboard + Red Flag Checklist': five core responsibility pillars (Vision & Strategy / Capital & Allocation / People & Culture / Stakeholder Management / Board & Governance) each point to an in-depth reference document.
### 1. Vision & Strategy Set the direction. Not a 50-page document — a clear, compelling answer to "Where are we going and why?"
Includes two Python tools built using only the standard library, positioned as 'runnable scoring models' rather than CLI analyzers: scripts import only json, typing, datetime, and math, feature no argument parsing, and involve no file or network I/O; `__main__` executes built-in sample company data and prints a report.
if __name__ == "__main__": # Example usage example_company = { 'name': 'TechCorp Inc.', 'market_position': { 'market_share': 35,
The second script performs three-scenario (base/bull/bear) financial modeling, likewise driven by hardcoded sample data in `__main__`, exposing analyze_financial_scenarios(base_case, scenarios) for external invocation.
print(analyze_financial_scenarios(example_base_case, example_scenarios))
Outputs adhere to strict formatting and confidence governance: Bottom Line → What (with confidence level) → Why → How to Act → Your Decision. Every finding is labeled as 🟢 verified / 🟡 medium / 🔴 assumed, and results must pass the repository's unified Internal Quality Loop (Self-Check / Cross-Functional Check / Executive Mentor Review).
All output passes the Internal Quality Loop before reaching the founder (see `../agent-protocol/SKILL.md`). - Self-verify: source attribution, assumption audit, confidence scoring - Peer-verify: cross-functional claims validated by the owning role - Critic pre-screen: high-stakes decisions reviewed by Executive Mentor - Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision - Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.
Reasoning technique is tied to Tree of Thought, requiring at least three distinct paths evaluated across upside/downside/reversibility/second-order effects, with planning horizons adjusted by company stage.
## Reasoning Technique: Tree of Thought Explore multiple futures. For every strategic decision, generate at least 3 paths. Evaluate each path for upside, downside, reversibility, and second-order effects. Pick the path with the best risk-adjusted outcome.
Context injection relies on standard file conventions: It 'ALWAYS' reads company-context.md (if present) before every response and allows the agent to initiate [INVOKE:role|question] requests to peer roles, establishing lateral cross-consultation within the C-suite advisory council.
- **Always** read `company-context.md` before responding (if it exists) - **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination) - **Invocation:** You can request input from other roles: `[INVOKE:role|question]`
The quantitative section establishes standard evaluation baselines via the CEO Metrics Dashboard table (ARR growth, runway > 12 months, burn multiple < 2x, NPS > 40, regrettable attrition < 10%, strategic work allocation > 40%, etc.), enabling advice to be challenged with concrete metrics.
| **Capital** | Months of runway | > 12 months | Monthly | | **Capital** | Burn multiple | < 2x | Monthly |
A lateral collaboration matrix links the CEO to other C-suite roles by scenario (COO for OKR translation, CFO for fundraising modeling, CHRO for culture assessment, CISO for risk posture, etc.), formalized in c-level-advisor/CLAUDE.md's architectural view: 'Chief of Staff routing → 10 roles → Executive Mentor critique → Decision Logger memory'.
| Setting direction | COO | Translate vision into OKRs and execution plan | | Fundraising | CFO | Model scenarios, prep financials, negotiate terms | | Board meetings | All C-suite | Each role contributes their section |
2Core Capabilities
4Recommended Governance & Evidence
- scripts/: Local script or command execution: python scripts/strategy_analyzer.py (explicitly stated in SKILL.md Quick Start; actually executes module `__main__`)
- 本地工作目录: File I/O and artifact output: Indirect: other skills within the c-level-advisor pod (decision-logger, company-os) handle memory persistence and decision logging, outside of this skill
5Second-Pass Verification
- [ok] skill 路径(任务书标『待定位』) — 实际相对路径 c-level-advisor/skills/ceo-advisor;仓库内另有 .gemini/skills/ceo-advisor(生成镜像,逐字相同)、.hermes/.vibe 打包树,以及 c-level-advisor/ceo-advisor.zip(见下条)。
- [ok] 『两个 Python 工具』的真实能力 — 两脚本确实存在且可独立运行,但都只含内置示例数据、无 argparse/无输入输出文件参数:strategy_analyzer.py 的 __main__ 构造 example_company(TechCorp Inc.)后 print;financial_scenario_analyzer.py 的 __main__ 构造三个示例情景后 print。如实测能力应为『可复用的评分函数库 + 演示运行』,SKILL.md Quick Start 的三行注释('Analyze strategic options with weighted scoring' 等)描述的是函数能力而非 CLI 行为,未夸大但易被误读。
- [discrepancy] 随包 zip 与目录版本不一致 — c-level-advisor/ceo-advisor.zip 内的 ceo-advisor/SKILL.md 是旧版:505 行、frontmatter 无 license/metadata、description 为 'Comprehensive CEO leadership skill providing strategic planning frameworks, financial scenario modeling, board governance guidance, investor relations strategies, and organizational leadership tools. …',条目时间 2025-10-18/19;目录内为 169 行、version 2.0.0、updated 2026-03-05 的新版。凡按 zip 安装者拿到的是旧内容(含旧脚本副本)。属分发产物未同步。
- [ok] 引用目标(agent-protocol / culture-architect / board-deck-builder) — 三者均存在于 c-level-advisor/skills/ 下;正文 'see `../agent-protocol/SKILL.md`' 路径正确。
- [ok] 无网络/无凭证/无写入 — 全目录 token 扫描零命中;两脚本 import 仅标准库;脚本无 open()、无 subprocess、无环境变量读取。company-context.md 为读取路径(SKILL.md 文本指令),非本目录内代码行为。
- [ok] 跨宿主镜像一致性 — diff -q .gemini/skills/ceo-advisor/SKILL.md c-level-advisor/skills/ceo-advisor/SKILL.md 无输出(内容相同),确认为 sync-gemini-skills.py 生成产物。
- [ok] 输出协议引用的一致性 — SKILL.md 声称输出过 Internal Quality Loop 并引用 ../agent-protocol/SKILL.md;该文件存在,属仓库统一协议,非本 skill 独有机制(已如实标注归属)。
- [ok] 元数据(commit/license/stars/last_push) — 本地 git HEAD = 19392f7a08264ed00486a251f5b2098321771f94(= 任务书 pin 19392f7a0826);SKILL.md frontmatter license MIT、metadata.version 2.0.0、author Alireza Rezvani、category c-level、updated 2026-03-05;LICENSE MIT / Copyright (c) 2025 Alireza Rezvani;gh api → stars 25977、pushed_at 2026-08-30T09:46:16Z。
6Verdict & Scenarios
4c873d324e29d1c8…