chief-of-staff
Use when the operator asks for a cross-cutting view of everything in flight — daily agenda, weekly review, "what needs me today", or orchestration across the analyst, advisor, scribe, ops, and career skills.
- License 许可
- MIT
- 最近更新
- 2026-07-09
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- chief-of-staff
- triggers
- daily agenda, what needs me today, weekly review, chief of staff, everything in flight, cross-skill status, orchestrate, morning rollup
- description
- Use when the operator asks for a cross-cutting view of everything in flight — daily agenda, weekly review, "what needs me today", or orchestration across the analyst, advisor, scribe, ops, and career skills.
- read_strategy
- { "agenda": "SKILL.md § Daily Agenda", "review": "SKILL.md § Weekly Review", "orchestration": "SKILL.md § Orchestration Patterns" }
02 资源文件 10
- 参考文档.claude-plugin/plugin.json475 B
- 其他.python-version5 B
- 其他.standalone-db173 B
- 脚本chief_of_staff.py15.1 KB
- 脚本dashboard/lib.ts1.1 KB
- 其他dashboard/pages/chief/page.tsx7.8 KB
- 脚本dashboard/routes/agenda/route.ts392 B
- 参考文档dashboard/views/hub.yaml973 B
- 其他pyproject.toml269 B
- 参考文档skill.yaml1.2 KB
03 SKILL.md 正文
Chief of Staff — The Capstone
A cross-view over your executive AI team: decisions (advisor), communications (scribe), research (analyst), operations (ops), and career moves (career). Not a task assistant — an orchestrator with a synoptic view of your priorities across every team member.
Earn it first. This skill only pays off after you have real mileage with
each individual team member. If the underlying namespaces are empty, the
agenda is empty. Build the habit with analyst, advisor, scribe, and
ops individually; graduate to the chief of staff when orchestration — not
capability — is your bottleneck.
chief_of_staff.py is read-only: it defines no schema and never writes.
It reads whichever team-member namespaces exist in alh_personal and degrades
gracefully (available: false) for skills you haven't installed.
Prerequisites
- TypeDB running with the
alh_personaldatabase - At least one team-member skill installed with real data
Daily Agenda
CLI="uv run --project skills/chief-of-staff python skills/chief-of-staff/chief_of_staff.py"
$CLI daily-agenda # JSON for the agent
$CLI report-agenda # Markdown for the operator
What it pulls, per team member:
| Section | Source | What surfaces |
|---|---|---|
| Operations | ops- |
open/overdue commitments, upcoming meeting preps, live brief specs |
| Decisions | advsr- |
decisions in framing/debating/deciding, journal reviews past due |
| Communications | scribe- |
pieces in persona-review / operator-review |
| Research | anlst- |
missions running, missions awaiting the three-question gate |
| Career | career- |
opportunity deadlines within 14 days, active projects |
Agent workflow: run daily-agenda, then sensemake — don't just relay the
JSON. Rank by stakes and dates, name the one or two items that genuinely need
the operator today (⏸ OPERATOR CHECKPOINT items from the other skills), and
propose which team member to engage for each.
Weekly Review
$CLI weekly-review # JSON rollup
$CLI report-week # Markdown scaffold
The agent narrates the week: decisions closed and how they compare with what the journal expected, research delivered vs still gated, pieces shipped, commitments kept and dropped, career movement. Cross-reference the advisor's journal notes and feed durable lessons back into the advisor's context docs.
Orchestration Patterns
The chief of staff routes work; team members do it:
- Decision needs evidence → open an
analystmission with--decision-contextpointing at theadvsr-decisionid (soft ref). - Decision made, needs announcing → open a
scribepiece whose primer is the advisor's journal note. - Meeting tomorrow with a stakeholder →
ops show-stakeholderthenprep-meeting; pull anycareercollaborations with that person for context. - Research delivered → if it changes a decision, reopen it with the advisor; if it changes a relationship, log it in the ops dossier.
One graph, one database: people (alh-person) are shared between career
collaborators and ops stakeholder dossiers by design.
Command Reference
| Command | Output | Purpose |
|---|---|---|
daily-agenda |
JSON | Cross-skill items needing attention today |
weekly-review |
JSON | Wider rollup for the weekly narrative |
report-agenda |
Markdown | Operator-facing daily agenda |
report-week |
Markdown | Weekly review scaffold |
Command Output Pattern
uv run emits a VIRTUAL_ENV warning to stderr. Use 2>/dev/null when piping
output to a JSON parser — never 2>&1.
Common Mistakes
- Starting here. With empty namespaces the agenda is noise. Build mileage with individual team members first.
- Relaying JSON instead of judging. The value is ranking and routing, not reporting.
- Writing through the chief. It is read-only by design; create and update entities through the owning skill's CLI so its workflows and audits apply.
04 同仓库更多 Skills
scribe
Use when drafting board updates, emails, LinkedIn posts, or talks in the operator's voice, building or evolving a voice profile from their best writing, audience-testing a draft against reader personas, or iterating on a piece with dimension-scored feedback
ops
Use when the operator wants a morning brief, meeting prep, stakeholder context before a meeting, commitment tracking, a new recurring report/monitor designed, or status synthesis across channels — the operational powerhouse you never had headcount for.
coach
暂无简介
coach
Personal health & fitness monitoring — ingest HealthKit metrics, track goals, surface regressions, manage appointments
career
Manage your career graph — people, collaborators, projects, and potential new positions — plus the opportunity pipeline, skill gaps, and learning plan
analyst
Use when researching a question that serves a decision, running market/competitive/internal research, verifying AI-generated research, or aggregating multi-model consensus on contested claims