Agent skill · Audited from source

Chief Of Staff

skill · borghei/Claude-SkillsNOASSERTION licenceAudited 19 Oct 2026 · source 6e3fcbdbb5cf

★ 949pushed 12 days agoversion 2.0.0
!CAUTIONGrade B · 89/100 · 5 findings · 6e3fcbd
949repo stars · whole borghei/Claude-Skills

Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit 6e3fcbdbb5cf and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 5 findings, 0 critical or high. What it does: 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…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Chief Of Staff (borghei/Claude-Skills)”. Retrieved 19 Oct 2026. https://modelsatlas.com/skills/borghei/chief-of-staff

2 skills are called “Chief Of Staff”. You are viewing borghei/Claude-Skills.

Trust audit

Audit 0.4.1 · source read 19 Oct 2026

Trust score89/100!CAUTION B
0 critical0 high5 medium0 low0 info

CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 13,985 of 14,816 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityWARN5
L1 Static sourceSecrets, path traversal, supply chain, hidden codePASS0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (5)

Audit 0.4.1 · source sha 6e3fcbdbb5cf · 19 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publisherborghei GitHub userOwner of the repository this skill is read from
  • Source folderborghei/Claude-Skills/c-level-advisor/chief-of-staffThe exact folder we audited
  • LicenceNOASSERTIONAs the repository states it
  • Commit pinned for this verdict6e3fcbdbb5cfA new audit runs when the source changes
  • Repository statusNot archivedLast push 12 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its 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…

---
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. **Circ

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 6e3fcbd

Download folder ↗
git clone https://github.com/borghei/Claude-Skills
git -C Claude-Skills checkout 6e3fcbdbb5cf

The author documents no install command, so this uses the repository directly. Our verdict covers commit 6e3fcbdbb5cf only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. !CAUTION B 89 / 100

    first audit · source 6e3fcbdbb5cf

A11y Audit!CAUTION

borghei/Claude-Skills

This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".

★ 949Grade B
Agent Designer!CAUTION

borghei/Claude-Skills

Designs multi-agent system architectures with orchestration patterns, tool schemas, and performance evaluation. Use when building AI agent systems, designing agent workflows, creating tool schemas, or evaluating agent…

★ 949Grade B
Agent Protocol!CAUTION

borghei/Claude-Skills

Design AI agent communication protocols: MCP tool schemas, A2A, function calling, and inter- agent messaging. Use when building multi-agent systems, defining tool interfaces, or implementing agent-to-agent communication.

★ 949Grade B
Agent Workflow Designer!CAUTION

borghei/Claude-Skills

Design multi-agent orchestration with workflow DAGs, routing, handoff protocols, and state management. Use when building pipelines of specialized agents, designing fan-out/fan-in patterns, or implementing fault-tolerant…

★ 949Grade B
Agenthub!CAUTION

borghei/Claude-Skills

Multi-agent DAG orchestration for workflows where AI agents collaborate via dependency graphs, covering agent spawning, output merging, and quality evaluation. Use when a task needs multiple specialized agents or to…

★ 949Grade B
Analytics Engineer!CAUTION

borghei/Claude-Skills

Analytics engineering across data modeling, dbt, transformation, and semantic layers. Use when building dbt models, designing star schemas, writing staging or mart SQL, configuring data tests, or optimizing warehouse…

★ 949Grade B

Questions about Chief Of Staff

What does the Chief Of Staff skill do?
385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit. Installs on Claude Code, Cursor, Codex, Gemini, Copilot, and 6 other AI assistants.
Is Chief Of Staff safe to install?
With care. The audit graded it B (89/100) and found 5 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Chief Of Staff access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (6e3fcbdbb5cf), read on 2026-10-19. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.