A personal AI Chief of Staff — local-first, plain-text memory that prepares you for what's ahead, closes loops, coaches you, and gets sharper over time. Propose-never-act by default.
Strengths-based weekly coaching grounded in your real meetings — one or two specific, role-relevant moves and an experiment for the week ahead.
Weekly memory consolidation (the cold path) — promote clustered learnings, supersede stale facts, decay and prune, and produce a reviewable diff. Usually scheduled; the only skill that edits memory.
Keep your world model current — refresh people, accounts, projects, and competitors from recent activity, superseding stale facts rather than overwriting them.
Internal read-only extractor — stages facts from email/docs/transcripts without writing memory. Used by other skills; run in a restricted profile. Not typically invoked directly.
Monthly goals and prioritization — reviews progress, then proposes an updated set of current priorities for your approval.
Read your meeting notes and transcripts so the assistant can capture outcomes and commitments. First-party; OAuth on Connect (sees your 'My notes' space).
Read your Zoom recordings, transcripts, and AI summaries. First-party Zoom MCP; OAuth on Connect.
Read your Fathom meeting recordings, transcripts, and summaries. First-party; OAuth on Connect.
Read your Fireflies transcripts, summaries, and action items. First-party; OAuth or API key on Connect.
Search messages and channels so the assistant has your work conversations as context. First-party Slack MCP; OAuth on Connect.
External network access
Connects to servers outside your machine
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A personal Chief of Staff that runs on top of an agent runtime (Claude Cowork / Codex): scheduled and on-demand skills, backed by a plain-text Markdown memory store, that prepares you for what's ahead, closes loops, coaches you, and gets sharper the longer it runs. It installs and configures itself by interviewing you.
It does not act on the world by default. It proposes; you approve.
Build artifact of [[AI Chief of Staff — Build Plan]]. Design: [[AI Chief of Staff]] · validation: [[AI Chief of Staff — Architecture Evaluation]] · loop spec: [[AI Chief of Staff — write-back method]].
As a plugin (easiest) — Claude Code:
/plugin marketplace add fontesgerards/chief-of-staff
/plugin install chief-of-staff@chief-of-staff
Then, in the folder where you want your brain to live: /cos-onboarding. Codex uses the same engine/ package — see PUBLISH.md. Publishing steps + the naming/collision note: PUBLISH.md.
Or clone (dev / no plugin): git clone …, ./setup.sh, open the folder, /cos-onboarding. See INSTALL.md.
The engine is the shared plugin; your instance (private brain) is created by /cos-onboarding in your own folder — it never lives in the plugin.
chief-of-staff/
├─ CLAUDE.md / AGENTS.md ← always-loaded entry (Claude / Codex) → engine/INSTRUCTIONS.md
├─ setup.sh / INSTALL.md ← one command to make skills invocable (/cos-onboarding, $cos-onboarding)
├─ engine/ ← git, shareable, identical for everyone (THE PRODUCT — no personal data)
│ ├─ INSTRUCTIONS.md global behavior + autonomy + memory-access conventions
│ ├─ skills/cos-<name>/SKILL.md invocable skills — cos-onboarding, cos-meeting-prep, cos-consolidate-memory, …
│ ├─ methods/ write-back, problem-solving, minto, coaching, PEI
│ ├─ templates/ entity schemas, memory-file + capture + proposal templates
│ └─ docs/ capability spike + write-isolation config + build notes
├─ .claude/skills → engine/skills (symlink — Claude discovers /<name>)
├─ .agents/skills → engine/skills (symlink — Codex discovers $<name>)
└─ instance/ ← local + private, GITIGNORED here; its own separate backup repo (one person's brain)
├─ config.md identity, goals, autonomy level, connectors, schedules
├─ memory/ core · semantic · episodic · procedural · sources · archive
├─ state/ current run, open loops, commitments, pending questions, corrections
├─ queue/ proposals awaiting approval (outbound · approvals · review)
├─ log/ run history + maintenance changelogs
└─ index/ optional, generated, rebuildable from Markdown
Why the split: to productize later, ship engine/ and let the onboarding skill regenerate a fresh instance/ for each new person. Nothing personal ever lives in the shared repo.
v1 scaffold complete; skills are invocable as commands (run ./setup.sh, then /cos-onboarding in Claude or $cos-onboarding in Codex — see INSTALL.md). U0 capability spike resolved (2026-06-04): scheduling ✓, connectors ✓, write-isolation ✓ (structural — enforced per-run via Claude Code permissions.deny+sandbox or Codex permissions profile; recipes in engine/docs/write-isolation-config.md). KTD-5 stays "structural." Next: run /cos-onboarding to seed a real instance/, and add a private remote to the instance backup repo.
npx claudepluginhub fontesgerards/chief-of-staff --plugin chief-of-staffHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
AI-powered development tools for code review, research, design, and workflow automation.
Plugin that includes the Figma MCP server and Skills for common workflows
Memory compression system for Claude Code - persist context across sessions