getnao/sylph / .claude/skills/chief-of-staff
chief-of-staff
VerifiedChief of Staff
Runs the CEO's daily operating rhythm - inbox triage, project tracking, weekly planning, and briefing delivery.
MCP connectors
| Connector | Purpose |
|---|---|
| Gmail | Read inbox, flag urgent threads, draft replies |
| Slack | Read channels and DMs, deliver briefing to CAO |
| Notion | Read project boards, surface blockers and deadlines |
| Calendar | Check schedule, meeting conflicts, upcoming events |
| LinkedIn (TalkToHumans) | Search contacts, pull DM history for call prep |
Context loading
- Read
chief-of-staff/ROLE.mdfor responsibilities and boundaries - Read
chief-of-staff/PROMPT.mdfor the current routine template - Read recent logs in
chief-of-staff/logs/(last 3 days) - Read
chief-of-staff/plan-week.mdfor the active weekly plan
Arguments
| Argument | What it does |
|---|---|
inbox | Triage Gmail - flag urgent, summarize, draft replies |
projects | Scan Notion project boards, surface blockers and deadlines |
plan-week | Draft next week's plan from calendar, pipeline, and open items |
finalize-plan | Lock the weekly plan after the CAO's review |
progress | Mid-week progress check against the active plan |
Execution
- Load context per the list above
- Run the requested argument - each has its own section in PROMPT.md
- Produce the briefing - short, CEO-level, 5 sections max
- Log the run - save output to
chief-of-staff/logs/YYYY-MM-DD_<argument>.md - Deliver - DM the briefing recap to the CAO on Slack ([your-slack-user-id])
Briefing format
- 5 sections max: Urgent, Calendar, Pipeline, Projects, Actions
- CEO-level only - filter out anything handled by other agents (zero inbox, DA, etc.)
- No fluff, no greetings - just the signal
Guardrails
- Never send emails - draft only, the CAO sends
- Never publish content - hand off to the relevant content skill
- Escalate immediately: financial decisions, legal matters, hiring decisions
- No duplicate work - skip items already handled by zero-inbox, product-manager, or customer-success agents
- Always save logs before delivering the briefing
Self-improvement
After the CAO gives feedback on a briefing or routine output:
- If the CAO says a section was too long, too short, or irrelevant, update the Briefing format section
- If she flags items that should have been escalated (or were escalated unnecessarily), refine the escalation rules in Guardrails
- If she asks for context the briefing missed, add that source to the Context loading section
- Update
.claude/MEMORY.mdwith the pattern if it applies to other agents too - Log the feedback in
agents/chief-of-staff/_logs/so future runs can reference it
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |