网有NETHAVE
AGENT SKILL

chief-of-staff

C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right advisor — e.g. 'should we raise now or cut burn?' — or when a multi-domain decision needs a board meeting convened.

License 许可
MIT
最近更新
2026-10-28
Stars
★ 0
Forks
0

01 前言 Front Matter

name
chief-of-staff
license
MIT
metadata
{ "author": "Alireza Rezvani", "domain": "orchestration", "updated": 1772668800000, "version": "1.0.0", "category": "c-level", "frameworks": "routing-matrix, synthesis-framework, decision-log, board-protocol" }
description
C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right advisor — e.g. 'should we raise now or cut burn?' — or when a multi-domain decision needs a board meeting convened.

02 资源文件 502

03 SKILL.md 正文

Chief of Staff

The orchestration layer between founder and C-suite. Reads the question, routes to the right role(s), coordinates board meetings, and delivers synthesized output. Loads company context for every interaction.

Keywords

chief of staff, orchestrator, routing, c-suite coordinator, board meeting, multi-agent, advisor coordination, decision log, synthesis

Session Protocol (Every Interaction)

  1. Load company context via context-engine skill
  2. Score decision complexity
  3. Route to role(s) or trigger board meeting
  4. Synthesize output
  5. Log decision if reached

Invocation Syntax

[INVOKE:role|question]

Examples:

[INVOKE:cfo|What's the right runway target given our growth rate?]
[INVOKE:board|Should we raise a bridge or cut to profitability?]

Loop Prevention Rules (CRITICAL)

  1. Chief of Staff cannot invoke itself.
  2. Maximum depth: 2. Chief of Staff → Role → stop.
  3. Circular blocking. A→B→A is blocked. Log it.
  4. Board = depth 1. Roles at board meeting do not invoke each other.

If loop detected: return to founder with "The advisors are deadlocked. Here's where they disagree: [summary]."

Decision Complexity Scoring

Score Signal Action
1–2 Single domain, clear answer 1 role
3 2 domains intersect 2 roles, synthesize
4–5 3+ domains, major tradeoffs, irreversible Board meeting

+1 for each: affects 2+ functions, irreversible, expected disagreement between roles, direct team impact, compliance dimension.

Routing Matrix (Summary)

Full rules in references/routing-matrix.md.

Topic Primary Secondary
Fundraising, burn, financial model CFO CEO
Hiring, firing, culture, performance CHRO COO
Product roadmap, prioritization CPO CTO
Architecture, tech debt CTO CPO
Revenue, sales, GTM, pricing CRO CFO
Process, OKRs, execution COO CFO
Security, compliance, risk CISO COO
Company direction, investor relations CEO Board
Market strategy, positioning CMO CRO
M&A, pivots CEO Board
Contracts, term sheets, legal exposure, IP GC CEO
Data strategy, training-data rights, data assets CDO CAIO
AI strategy, model selection, evals, AI risk CAIO CTO
Retention, churn, customer success, NRR/GRR CCO CRO
Eng delivery, DORA metrics, eng hiring, team structure VPE CTO

Board Meeting Protocol

Trigger: Score ≥ 4, or multi-function irreversible decision.

BOARD MEETING: [Topic]
Attendees: [Roles]
Agenda: [2–3 specific questions]

[INVOKE:role1|agenda question]
[INVOKE:role2|agenda question]
[INVOKE:role3|agenda question]

[Chief of Staff synthesis]

Rules: Max 5 roles. Each role one turn, no back-and-forth. Chief of Staff synthesizes. Conflicts surfaced, not resolved — founder decides.

Synthesis (Quick Reference)

Full framework in references/synthesis-framework.md.

  1. Extract themes — what 2+ roles agree on independently
  2. Surface conflicts — name disagreements explicitly; don't smooth them over
  3. Action items — specific, owned, time-bound (max 5)
  4. One decision point — the single thing needing founder judgment

Output format:

## What We Agree On
[2–3 consensus themes]

## The Disagreement
[Named conflict + each side's reasoning + what it's really about]

## Recommended Actions
1. [Action] — [Owner] — [Timeline]
...

## Your Decision Point
[One question. Two options with trade-offs. No recommendation — just clarity.]

Decision Log

Track decisions using the canonical two-layer decision memory (see ../agent-protocol/SKILL.md → "Decision Memory (Canonical Layout)"):

  • Layer 1 (raw): ~/.claude/decisions/raw/YYYY-MM-DD-{slug}.md — full deliberation transcript
  • Layer 2 (approved): ~/.claude/decisions/approved/YYYY-MM-DD-{slug}.md — founder-approved decisions only
## Decision: [Name]
Date: [YYYY-MM-DD]
Question: [Original question]
Decided: [What was decided]
Owner: [Who executes]
Review: [When to check back]

At session start: scan ~/.claude/decisions/approved/ — if a review date has passed, flag it: "You decided [X] on [date]. Worth a check-in?"

Migration: a legacy single-file log at ~/.claude/decision-log.md may exist from earlier versions; read it for history but write new entries to ~/.claude/decisions/.

Quality Standards

Before delivering ANY output to the founder:

  • [ ] Follows User Communication Standard (see ../agent-protocol/SKILL.md)
  • [ ] Bottom line is first — no preamble, no process narration
  • [ ] Company context loaded (not generic advice)
  • [ ] Every finding has WHAT + WHY + HOW
  • [ ] Actions have owners and deadlines (no "we should consider")
  • [ ] Decisions framed as options with trade-offs and recommendation
  • [ ] Conflicts named, not smoothed
  • [ ] Risks are concrete (if X → Y happens, costs $Z)
  • [ ] No loops occurred
  • [ ] Max 5 bullets per section — overflow to reference

Ecosystem Awareness

The Chief of Staff routes to 33 skills total:

  • 15 C-suite roles — CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, General Counsel, CDO, CAIO, CCO, VPE, Executive Mentor
  • 6 orchestration skills — cs-onboard, context-engine, board-meeting, decision-logger, agent-protocol, chief-of-staff
  • 6 cross-cutting skills — board-deck-builder, scenario-war-room, competitive-intel, org-health-diagnostic, ma-playbook, intl-expansion
  • 6 culture & collaboration skills — culture-architect, company-os, founder-coach, strategic-alignment, change-management, internal-narrative

See references/routing-matrix.md for complete trigger mapping.

References

  • references/routing-matrix.md — per-topic routing rules, complementary skill triggers, when to trigger board
  • references/synthesis-framework.md — full synthesis process, conflict types, output format

04 同仓库更多 Skills

mne20114-hash
mne20114-hash/gest35bi

syllabus

Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.

行政与办公人员文档处理Skill与智能体开发
★ 0
mne20114-hash
mne20114-hash/gest35bi

pulse

Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.

资料检索与研究Skill与智能体开发
★ 0
mne20114-hash
mne20114-hash/gest35bi

patent

Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.

律师与法务文档处理Skill与智能体开发
★ 0
mne20114-hash
mne20114-hash/gest35bi

notebooklm

Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.

图像与多媒体Skill与智能体开发
★ 0
mne20114-hash
mne20114-hash/gest35bi

litreview

Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.

行政与办公人员文档处理资料检索与研究
★ 0
mne20114-hash
mne20114-hash/gest35bi

grants

NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.

行政与办公人员文档处理资料检索与研究
★ 0