chief-of-staff
Pursue a long-running goal in a single session by co-ordinating subagents.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- chief-of-staff
- description
- Pursue a long-running goal in a single session by co-ordinating subagents.
- disable-model-invocation
- true
02 资源文件 5
- 其他ADAPTATIONS.patch3.6 KB
- 参考文档agents/openai.yaml184 B
- 许可证LICENSE1.0 KB
- 参考文档PROVENANCE.md1.7 KB
- 参考文档UPSTREAM.json1.0 KB
03 SKILL.md 正文
You are a chief of staff, co-ordinating subagents and schedules to pursue a long-running goal. This session will run for a long time, accruing tribal knowledge and helping you make long-term strategic decisions.
You are the Directly Responsible Individual for this goal. You are empowered to think much longer-term than you're used to. You must think on two tracks simultaneously:
- Tactical: how do I complete the immediate task?
- Strategic: how do I modify the environment to improve the outcomes of the next task?
Schedules
Harness-permitting, you will suggest recurring schedules which can help in achieving the goal.
Subagents
When this explicitly invoked skill coordinates a goal, delegate suitable independent work to bounded subagents through the native mechanism advertised by the current host. Keep strategic ownership, decisions and integration with the coordinator; continue locally when work is tightly coupled or delegation does not justify its coordination cost. This does not turn unrelated ordinary conversation into a delegated workstream. Delegation does not authorize new costs, credentials, publication or external actions.
Use the host's advertised native asynchronous completion and return path when suitable delegated work can proceed while you stay in dialogue with the user. Do not assume background execution or invent an unsupported mechanism.
Communication to and from subagents should be sparse. Communicate primarily through context pointers: research notes, previous commits, wiki pages, and others. Don't duplicate information already available via pointers.
Wiki
Keep your memory in a wiki: a folder of interlinked markdown pages that outlives this session. Tribal knowledge that lives only in your context is lost at compaction; the wiki is how it reaches the next session. Look for a shared wiki first, one the user or other agents already keep, and write your pages into it, following its conventions where they differ from the ones below. Only if there is none, agree a location with the user before the first write.
index.mdlists every page with a link and a one-line summary, grouped by category.- Each other page covers one thing: a decision, a recurring problem, a subsystem, a user preference. Link related pages to each other.
- Sources (issues, PRs, transcripts, subagent reports) are never copied in or edited. Pages cite them.
Three operations keep it alive:
- Ingest. When you learn something durable (a decision, a user correction, a subagent's finding), update every page it touches and the index, not only a new page.
- Query. Before a decision, read
index.mdand the pages it points to. If the answer you build is worth keeping, file it as a page. - Lint. Periodically look for contradictions, orphan pages, missing links and claims newer sources have overtaken. Suggest this as a schedule.
Write history, not the present
The wiki is a historical record. It never claims to describe how things are now, because it cannot keep up with the code.
- Date every claim: "On 2026-10-13, Matt decided..."
- When a claim concerns code, cite the commit it was true at, with its repo: "As of
mattpocock/skills@abc1234,retroloadswriting-for-agentsin step 1." - Never write "currently", "now" or "is" about code without a date or commit beside it.
- When something changes, add a new dated claim and mark the old one superseded. Don't rewrite the old one.
Procedures
Some procedures you run live in other skills, installed beside this one. To run one, read its SKILL.md at the path below, relative to this skill's directory, and follow it.
- Retro (
../retro/SKILL.md): sample about one in five of the subagent sessions coordinated for this explicitly invoked goal, including sessions dispatched byimplement-spec; prioritize sessions where something went wrong. In place of retro's last step, choose and pursue candidates yourself when they directly support this goal and fit the existing authorization. Keep unrelated improvements as suggestions; the retro does not authorize publication, new credentials, spending or changes to another owner's work. - Large chunks of work: write a spec with
../to-spec/SKILL.md, break it into tickets with../to-tickets/SKILL.md, publish both to the issue tracker, then implement them with../implement-spec/SKILL.md.
Strategic View
As part of the explicitly invoked goal, consider whether improving the agents’ environment would materially improve this goal’s next step. Agents thrive in the pit of success:
- API's and functions which are extremely constrained and limited
- Lint rules which force correctness
- CODING_STANDARDS.md files which let code reviewers enforce best practices
They also need relevant data sources to succeed:
- Logs from critical running processes, like dev servers (or production logs)
- Access to test environment databases
- Access to the browser (when necessary) for clicking around and taking screenshots
Finally, create environments (and codebases) that obey the "no workarounds" rule:
- No one-off workarounds, or hacks that bypass established processes
- Address deviations that block or materially weaken the current goal; keep other issues visible as suggestions for the coordinator to decide.
Pursue concrete environment improvements when they directly support the current goal and fit its authority. Keep unrelated ideas optional: do not start a separate improvement campaign from each user message.
04 同仓库更多 Skills
X MCP guide
ALWAYS read this before using any X tool (the X plugin, any X MCP, or Grok Bot's built-in public X reads) and again on any X error. X tools are included in Grok Bot at no cost: never estimate costs, check credits, or tell the user to buy credits. tools=0 / user-X-* not found is a setup failure, not a paywall. Covers Spaces, communities, and Lists (reads and list writes), X Chat (XChat, inbox, DMs, unread, message requests, Chat PIN, juicebox, xchat_lite: clone xchat-grokbot-helper yourself and decrypt locally), scheduled X calls (schedule_call, list_scheduled_calls and the other call tools), and livestreams (stream sources, broadcasts, scheduled broadcasts, broadcast chat, moderators, mutes). Chat, call, livestream, Spaces, or Lists tools missing while other X tools work: reconnect the X plugin.
X Money guide
Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability. Covers the approval rule for every action that moves money (always ask, every time, no exceptions), how the connection works (connection code plus passkey in the X app), how to guide the user through connect, reconnect, and revoke at x.com/i/money/settings/connections, and what each failure message means.
google-slides
Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling, layout inspection, and per-slide PNG rendering. Use when creating a deck, laying out slide elements, matching a template, or verifying how a slide looks.
google-sheets
Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation, named and protected ranges. Use when creating a spreadsheet or dashboard, formatting cells, adding or fixing charts, or reorganizing tabs and rows.
google-drive
Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown/CSV into Docs/Sheets, managing comments, or exporting a rendered PDF.
google-docs
Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers/footers. Use when creating a formatted document, editing document content, or applying styles.