Chief of Staff
Chief of Staff Skill
The capstone orchestrator that reads across every team member’s namespace to produce a single daily agenda and weekly review of everything in flight.
Application: Personal Assistant · Database:
alh_personal· Read-only — no namespace of its own
Purpose
The chief-of-staff is a cross-view over your executive AI team — decisions (advisor), communications (scribe), research (analyst), operations (ops), and career moves (career). It is not a task assistant; it is an orchestrator with a synoptic view of your priorities across every team member. It routes work and ranks stakes; the individual skills do the work.
It is read-only by design. It defines no schema and writes nothing. It reads whichever team-member namespaces (ops-, advsr-, scribe-, anlst-, career-) already exist in the shared alh_personal database and degrades gracefully (available: false) for any skill you have not installed. Because it has no entities of its own, this skill has no data model — every field it surfaces belongs to the owning skill.
Earn it first. This capstone 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, then graduate to the chief-of-staff when orchestration — not capability — becomes your bottleneck.
What it reads
One section per team member, all read-only. A missing namespace surfaces as available: false rather than failing the rollup.
| Section | Source namespace | What surfaces |
|---|---|---|
| Operations | ops- |
open/overdue commitments, upcoming meeting preps, live/trial 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 |
Each agenda item carries the owning entity’s id, so it deep-links back into that skill’s dashboard for detail and action.
Commands
Run with uv run --project skills/chief-of-staff python skills/chief-of-staff/chief_of_staff.py <command>.
| Command | What it does |
|---|---|
daily-agenda |
JSON cross-skill agenda: ops today + advisor reviews due + scribe pieces awaiting review + analyst gates pending + career deadlines |
report-agenda |
Markdown daily agenda for the operator |
weekly-review |
JSON rollup — same collectors, wider lens for the weekly narrative |
report-week |
Markdown weekly review scaffold for the agent to narrate |
The agent’s job is to sensemake, not relay — rank by stakes and dates, name the one or two items that genuinely need the operator today, and propose which team member to engage for each.
How it fits the suite
The chief-of-staff sits on top of the other five personal-assistant skills as a read-only aggregator. It reads the shared alh_personal database and its dashboard appears at /chief when that database is selected in the hub’s switcher. Because it writes nothing, it is safe to run anytime — create and update entities through the owning skill’s CLI so their workflows and audits apply. Each agenda item deep-links into the owning skill’s dashboard. Coach lives in the same family but is not part of the agenda rollup.
See the Personal Assistant overview and the sibling skills it orchestrates: ops, advisor, scribe, analyst, and career.