agentleFS
poorvith-mppoorvith-mp/skills-business/skills/chief-of-staff/SKILL.md

chief-of-staff

Skill1 starsChanged 3 months agoMITView on GitHub

Run the operating cadence behind a leader: priority triage, meeting and decision hygiene, follow-through. Use when managing CEO priorities, executive meetings, or strategic cadence.

40 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use software-factory, setup-ts-deep-modules and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jddeliaSkill

    software-factory

    Instantiate and operate an adaptive Codex software factory for substantial software projects. Use when Codex should ask or infer a factory work mode, including Safe MVP mode for thin real vertical slices, set up persistent factory goals, configure Principal Executive/user-involvement pattern, role topology, ledger topology, baton sizing, verification cadence, acceptance tiers, reviewers, manager/user-liaison intake, thread cleanup, stop/resume controls, handoffs, monitors, commits, release gates, or recovery from messy multi-agent work.

    Also in 6 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 16 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 18 projects that use this

  • richard12511Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 15 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 17 projects that use this

  • LesaniSkill

    writing-fragments

    Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.

    Also in 17 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run weekly asynchronous follow-through reviews.

    line 38
  2. Distinctive:

    Never escalate an issue to the principal without a stated recommendation and the primary condition that would invalidate it.

    line 46
  3. Distinctive:

    Keep meeting minutes under 5 bullets: decision reached, DRI assigned, target completion date.

    line 48
  4. Distinctive:

    NEVER act as an information bottleneck.

    line 58
  5. Distinctive:

    NEVER allow a meeting to end without an explicit decision or a scheduled decision date.

    line 59
  6. Distinctive:

    NEVER brief an executive by summarizing an entire document when they only need the recommendation and the two facts that would change it.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 37 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Chief Of Staff

The primary objective of a Chief of Staff is maximizing the principal's cognitive bandwidth and institutional leverage. This requires establishing rigid inbound triage, enforcing decision hygiene across executive forums, and ensuring commitments made in executive meetings translate into closed operational loops.

1. Operating Cadence & Priority Triage

Structure executive attention around a 4-tier inbound sorting matrix:

  • Decide Now: Requires principal authority; accompanied by a 1-page decision memo with recommendation and trade-offs.
  • Delegate: Route directly to the functional leader with explicit context, decision deadline, and expected deliverable format.
  • Defer with Date: Non-urgent strategic issues scheduled into quarterly planning cycles; do not let them linger in daily inboxes.
  • Drop: Requests lacking actionable data, clear ownership, or strategic alignment; return to sender with specific guidance.

2. Decision Hygiene & Executive Meeting Governance

Meetings without pre-reads and explicit decision owners become expensive status updates:

  • The 1-Page Pre-Read Mandate: Require all items seeking executive decision to submit a structured 1-pager 24 hours in advance:
    1. Core Decision Required (1 sentence)
    2. Context & Problem Statement (1 paragraph)
    3. Recommendation & Rationale (Why this path over alternatives)
    4. Key Trade-offs & Risks (What we give up or risk)
    5. Dissenting Opinions (Valid objections raised during functional review)
  • Meeting Auditing: Cancel meetings that exist solely for broadcast reporting. Convert status updates to asynchronous written Friday roundups.

3. Commitment Tracking & Institutional Follow-Through

Maintain the executive single-source-of-truth commitment register:

  • Log every promise, directive, or delegation made by the principal in meetings or communication channels.
  • Attribute three mandatory fields: Single Directly Responsible Individual (DRI), Binary Success Criterion, and Hard Due Date.
  • Run weekly asynchronous follow-through reviews; surface overdue or blocked commitments directly to the functional DRI before escalating to the principal.

4. Executive Deliverables

  • Weekly Executive Brief: 1-page dashboard highlighting: Decisions needed this week, Key metric anomalies, Operational commitments at risk, and Cross-functional escalations.
  • Commitment Register: Living ledger of all open executive action items and completion status.
  • Quarterly Business Review (QBR) Synthesis: Integrated review of department milestones and strategic alignment.

Critical Rules

  1. Never escalate an issue to the principal without a stated recommendation and the primary condition that would invalidate it.
  2. Protect calendar blocks: ensure the principal has a minimum of 10 hours of uncommitted strategic thinking time per week.
  3. Keep meeting minutes under 5 bullets: decision reached, DRI assigned, target completion date.

Verification Checklist

  • Inbound triage protocol categorizes all pending executive items into Decide, Delegate, Defer, or Drop.
  • Executive decision items accompanied by structured 1-page pre-reads submitted in advance.
  • All commitments from executive forums recorded with a single DRI and hard deadline.
  • Calendar audit protects uninterrupted strategic focus blocks.
  • Weekly brief synthesizes risks and decisions rather than reciting activity logs.

Anti-Patterns

  • NEVER act as an information bottleneck; facilitate direct communication between leaders while monitoring commitments.
  • NEVER allow a meeting to end without an explicit decision or a scheduled decision date.
  • NEVER brief an executive by summarizing an entire document when they only need the recommendation and the two facts that would change it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.