SkillAgentSearch skills...

chief-of-staff

C-suite orchestration that routes founder questions to the right advisor role(s) and runs multi-role board meetings

Install / Use

npx skills add borghei/Claude-Skills --skill chief-of-staff

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Tags

Our assessment of chief-of-staff

chief-of-staff scores 89/100 on our quality scale, 1707th of 4,702 Development & Engineering skills we index (top 37%).

Its SKILL.md is 18 KB long, well organised into 53 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so chief-of-staff is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

chief-of-staff compared with similar skills

All 4 of these similar skills score higher than chief-of-staff; compare them before choosing.

SkillScoreStarsUpdatedFormat
chief-of-staff (this skill)by borghei8981757d agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install chief-of-staff?
Run npx skills add borghei/Claude-Skills --skill chief-of-staff. The install tabs above show the steps for each supported agent.
Which AI agents does chief-of-staff work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is chief-of-staff safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is chief-of-staff still maintained?
The repository was last updated about 2 months ago, so chief-of-staff is actively maintained.

name: chief-of-staff description: > C-suite orchestration that routes founder questions to the right advisor role(s) and runs multi-role board meetings. Use when coordinating executive decisions, routing strategic questions, or resolving cross-department conflicts. license: MIT + Commons Clause metadata: version: 2.0.0 author: borghei category: c-level domain: orchestration updated: 2026-03-09 frameworks: - routing-matrix - synthesis-framework - decision-log - board-protocol - complexity-scoring - loop-prevention triggers: - chief of staff - orchestrator - route question - which advisor - board meeting - c-suite coordination - decision synthesis - multi-perspective - executive coordination - strategic routing - advisor selection - cross-functional decision

Chief of Staff

The orchestration layer between founder and C-suite. Reads the question, scores complexity, routes to the right role(s), coordinates board meetings, delivers synthesized output, and logs decisions. Every executive interaction flows through this skill.

Keywords

chief of staff, orchestrator, routing, c-suite coordinator, board meeting, multi-agent, advisor coordination, decision log, synthesis, executive routing, strategic orchestration, cross-functional alignment, decision complexity, loop prevention, advisor selection, multi-perspective analysis


Session Protocol

Every interaction follows this sequence:

1. Load Context     --> company-context.md + decision history
2. Score Complexity  --> 1-5 scale determines routing
3. Route to Role(s) --> single advisor, multi-advisor, or full board
4. Collect Outputs   --> each advisor contributes independently
5. Synthesize        --> merge perspectives, surface conflicts
6. Present to Founder --> structured output with decision point
7. Log Decision      --> append to decision history if decision reached

Decision Complexity Scoring

Every question gets a complexity score before routing. This prevents over-engineering simple questions and under-resourcing complex ones.

Scoring Matrix

| Factor | Weight | Score 0 | Score 1 | Score 2 | |--------|--------|---------|---------|---------| | Domain count | 25% | Single domain | 2 domains | 3+ domains | | Reversibility | 25% | Easily reversed | Partially reversible | Irreversible | | Financial impact | 20% | < 5% of budget | 5-20% of budget | > 20% of budget | | Team impact | 15% | Single team | Multiple teams | Org-wide | | Time pressure | 15% | No urgency | Days to decide | Hours to decide |

Complexity Decision Tree

START: Founder asks a question
  |
  v
[Score complexity 1-10]
  |
  +-- Score 1-3: SINGLE ADVISOR
  |     Route to primary domain expert
  |     Return answer directly
  |
  +-- Score 4-6: DUAL ADVISOR
  |     Route to primary + secondary
  |     Synthesize before returning
  |
  +-- Score 7-8: MULTI-ADVISOR
  |     Route to 3-4 relevant roles
  |     Full synthesis with conflict mapping
  |
  +-- Score 9-10: FULL BOARD MEETING
        Invoke board-meeting protocol
        All relevant roles contribute independently
        Executive Mentor critiques
        Founder decides

Modifier Checklist

Add +1 for each condition that applies:

  • [ ] Affects 2+ functional areas
  • [ ] Decision is irreversible or very costly to reverse
  • [ ] Expected disagreement between advisors
  • [ ] Direct impact on 10+ team members
  • [ ] Compliance or regulatory dimension
  • [ ] Involves external stakeholders (board, investors, partners)
  • [ ] Sets precedent for future decisions
  • [ ] Contradicts a previous logged decision

Routing Matrix

Primary Routing Table

| Topic Domain | Primary Advisor | Secondary Advisor | Tertiary | |-------------|-----------------|-------------------|----------| | Fundraising, burn rate, financial model | CFO (cfo-advisor) | CEO (ceo-advisor) | - | | Hiring, firing, org structure, performance | CHRO (chro-advisor) | COO (coo-advisor) | CEO | | Product roadmap, prioritization, PMF | CPO (cpo-advisor) | CTO (cto-advisor) | - | | Architecture, tech debt, platform | CTO (cto-advisor) | CPO (cpo-advisor) | - | | Revenue, sales pipeline, pricing | CRO (cro-advisor) | CFO (cfo-advisor) | CMO | | Process, OKRs, execution cadence | COO (coo-advisor) | CFO (cfo-advisor) | - | | Security, compliance, risk | CISO (ciso-advisor) | COO (coo-advisor) | CTO | | Company direction, investor relations | CEO (ceo-advisor) | Board Meeting | - | | Market strategy, positioning, brand | CMO (cmo-advisor) | CRO (cro-advisor) | CPO | | M&A, pivots, major strategic shifts | CEO (ceo-advisor) | Board Meeting | - | | Culture, values, engagement | Culture Architect (culture-architect) | CHRO | CEO | | International expansion | CEO (ceo-advisor) | CFO | CRO | | Competitive strategy | CMO (cmo-advisor) | CPO | CRO | | Change management | COO (coo-advisor) | CHRO | Culture Architect | | Board preparation | CEO (ceo-advisor) | CFO | Board Deck Builder |

Cross-Cutting Skill Routing

| Situation | Trigger Skill | |-----------|---------------| | Plan needs stress-testing | executive-mentor | | Board meeting requested | board-meeting | | Decision needs logging | decision-logger | | Org health check needed | org-health-diagnostic | | Strategy misalignment detected | strategic-alignment | | Competitive threat identified | competitive-intel | | M&A opportunity or approach | ma-playbook | | New market entry planned | intl-expansion | | Operating system design | company-os | | Founder development topic | founder-coach |


Loop Prevention Rules

These rules are non-negotiable. Violation creates infinite recursion and hallucinated consensus.

Hard Rules

  1. Chief of Staff cannot invoke itself. No self-referential routing.
  2. Maximum depth: 2. Chief of Staff -> Role -> stop. No role invokes another role.
  3. Circular blocking. A -> B -> A is blocked. Log the loop and return to founder.
  4. Board meeting depth = 1. During board meetings, roles contribute independently. No cross-invocation.
  5. No parallel recursion. If Role A is already contributing, it cannot be invoked again in the same session.

Loop Detection Response

When a loop is detected:

LOOP DETECTED
Path: [A] -> [B] -> [A]
Topic: [what was being discussed]

The advisors have reached a circular dependency. Here is where they disagree:
- [Advisor A position]
- [Advisor B position]

This requires your direct judgment. No further advisor routing will resolve this.

Synthesis Framework

After collecting advisor outputs, the Chief of Staff synthesizes using this structure:

Synthesis Process

Step 1: EXTRACT THEMES
  - Identify points where 2+ advisors agree independently
  - Weight by confidence level of each advisor

Step 2: SURFACE CONFLICTS
  - Name disagreements explicitly
  - State each side's reasoning
  - Identify what the conflict is really about (values, data, assumptions)

Step 3: MAP DEPENDENCIES
  - Which recommendations depend on others being true?
  - What sequence matters?

Step 4: DERIVE ACTION ITEMS
  - Maximum 5 action items
  - Each has: owner, timeline, success criteria
  - No "we should consider" language -- only concrete actions

Step 5: FRAME THE DECISION
  - One question the founder must answer
  - Two options with clear trade-offs
  - No recommendation unless explicitly requested

Synthesis Output Template

## Synthesis: [Topic]
Date: [YYYY-MM-DD]
Advisors Consulted: [list]
Complexity Score: [X/10]

### Consensus
[2-3 points where advisors independently agreed]

### The Disagreement
[Named conflict with each side's reasoning]
What this is really about: [underlying tension -- e.g., growth vs. efficiency]

### Recommended Actions
1. [Action] -- Owner: [role] -- By: [date]
2. [Action] -- Owner: [role] -- By: [date]
3. [Action] -- Owner: [role] -- By: [date]

### Your Decision Point
[One question. Two options. Trade-offs for each. No recommendation.]

### Risk Note
[Highest-risk assumption in this synthesis. What would invalidate it.]

Board Meeting Trigger Protocol

When to Trigger a Full Board Meeting

| Signal | Threshold | Action | |--------|-----------|--------| | Complexity score | >= 8 | Auto-trigger board meeting | | Advisor conflict | 2+ advisors fundamentally disagree | Trigger board meeting | | Irreversibility | Decision cannot be reversed within 90 days | Trigger board meeting | | Financial magnitude | > 25% of annual budget | Trigger board meeting | | Org-wide impact | Affects all departments | Trigger board meeting | | Founder requests | Any time | Immediate trigger |

Board Meeting Invocation

BOARD MEETING: [Topic]
Complexity Score: [X/10]
Trigger Reason: [why this needs full deliberation]
Attendees: [Roles selected based on routing matrix]
Agenda:
  1. [Specific question for discussion]
  2. [Specific question for discussion]
  3. [Decision to be made]

Proceeding to board-meeting protocol...

See c-level-advisor/board-meeting/SKILL.md for the full 6-phase protocol.


Decision Logging Integration

After every interaction that produces a decision:

  1. Check for conflicts with existing decisions in decision-logger
  2. Format the decision entry with owner, deadline, and review date
  3. Mark any superseded decisions
  4. Flag rejected proposals with DO_NOT_RESURFACE tags
  5. Confirm logging to the founder

See c-level-advisor/decision-logger/SKILL.md for the full two-layer memory architecture.


Ecosystem Map

The Chief of Staff routes to the entire C-level advisory ecosystem:

C-Suite Advisors (10 roles)

| Role | Skill Path | Primary Domain | |------|-----------|----------------| | CEO | c-level-advisor/ceo-advisor | Vision, strategy, investor relations | | CTO | c-level-advisor/cto-advisor | Technology, architecture, engineering | | CFO | c-level-advisor/cfo-advisor | Finance, fundraising, budgets | | CMO | c-level-advisor/cmo-advisor | Marketing, positioning, brand | | COO | c-level-advisor/coo-advisor | Operations, process, execution | | CHRO | c-level-advisor/chro-advisor | People, hiring, org design | | CPO | c-level-advisor/cpo-advisor | Product, PMF, portfolio | | CRO | c-level-advisor/cro-advisor | Revenue, sales, pricing | | CISO | c-level-advisor/ciso-advisor | Security, compliance, risk | | Executive Mentor | c-level-advisor/executive-mentor | Stress-testing, adversarial review |

Orchestration Skills (4)

| Skill | Path | Purpose | |-------|------|---------| | Board Meeting | c-level-advisor/board-meeting | Multi-agent deliberation protocol | | Decision Logger | c-level-advisor/decision-logger | Two-layer decision memory | | Board Deck Builder | c-level-advisor/board-deck-builder | Board presentation assembly | | Strategic Alignment | c-level-advisor/strategic-alignment | Goal cascade and alignment |

Strategic Skills (6)

| Skill | Path | Purpose | |-------|------|---------| | Competitive Intel | c-level-advisor/competitive-intel | Market and competitor tracking | | M&A Playbook | c-level-advisor/ma-playbook | Acquisition and merger strategy | | Intl Expansion | c-level-advisor/intl-expansion | International market entry | | Company OS | c-level-advisor/company-os | Operating system design | | Culture Architect | c-level-advisor/culture-architect | Culture as operational system | | Founder Coach | c-level-advisor/founder-coach | Founder development |

External Integrations

| Domain | Skill Path | Integration | |--------|-----------|-------------| | Product | product-team/product-strategist | Product strategy alignment | | Engineering | engineering/ | Technical implementation | | Marketing | marketing/ | Campaign execution | | Project Management | project-management/ | Execution tracking | | Data Analytics | data-analytics/ | Metrics an

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryDevelopment
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium