ceo-exec-assistant
Skill1 starsChanged 17 days agoMITView on GitHub
Use this skill when the person running a small agency needs to know what the week actually demands, pulled from the project tool and the calendar rather than from memory. Produces a short brief: what is committed today and this week, what is at risk, what the calendar makes impossible, and the three things to do first. Also use for "what's on this week", "am I missing anything", "catch me up before Monday", "what's slipping".
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- plain-language-copy-checkSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Read-only by default. The brief proposes task changes and calendar blocks.
- Distinctive: line 42
MUST calculate available hours before reading the task list.
- Distinctive: line 43
MUST name what will not happen when commitments exceed capacity.
- Distinctive: line 44
MUST limit the priorities to three, each one finishable.
- Distinctive: line 45
MUST keep the brief read-only unless asked to make a change, and confirm before changing more than one item.
- Distinctive: line 46
MUST treat prep for a client presentation as a task with a due date.
- Distinctive: line 47
NEVER pull from email. Two sources only.
- Distinctive: line 48
NEVER carry an item that has been overdue for more than a week without flagging it for a decision.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Applies at the start of the week, or any morning the day has got away from its owner. Produces a brief read in two minutes that names what to do first and what will not happen.
The play
- Pull two sources and nothing else. From Asana, every task assigned to them or where they are the approver, with due dates inside the next ten days. From Google Calendar, the week's committed hours. Email is not a source here; email is a to-do list written by other people.
- Work out the real capacity before looking at the task list. Committed meeting hours subtracted from working hours, minus a fixed admin allowance. The arithmetic and the default allowance are in references/capacity-math.md. Doing this first is what keeps the brief honest, because a task list read without capacity in hand always looks achievable.
- Sort what is left into four buckets: due today, due this week, at risk, and waiting on someone else. The sorting rules, including what makes a task at risk, are in references/triage-rules.md.
- Name what will not happen. If committed work exceeds capacity, say which items are being dropped or moved rather than listing everything and letting the week decide. This is the part that makes the brief worth reading and the part most likely to be softened out of it.
- Branch by what the calendar shows:
- A day with more than four meeting hours: no deep work scheduled that day. Put only small items against it.
- A client presentation or pitch this week: prep time is a task with a due date, not something that happens in the gaps. If it is not on the calendar, that is the first finding.
- A day with no meetings: this is the only real capacity in the week. Protect it before anything else gets scheduled into it.
- Overdue items more than a week old: they are not tasks any more. Flag them for deleting or rescheduling, not for doing.
- End with three priorities, ordered, each one a thing that gets finished rather than worked on. Not five.
- Read-only by default. The brief proposes task changes and calendar blocks; it never edits either without being asked. Any change to more than one item is confirmed first.
What good looks like
- First thing I check that most people skip: the gap between what the calendar says is committed and what the task list assumes is available. Almost every overloaded week is visible in that one number before anyone opens a task.
- The mediocre version: the task list reprinted in a nicer font, with a cheerful summary line. It tells the owner what they already knew, in an order they already had, and does not say what to drop.
- I know the brief is right when something gets explicitly dropped. A brief where everything fits has not been read against the calendar.
- Second test: the three priorities are things that can be finished, not projects. "Finish the Harbour proposal" passes. "Work on Harbour" does not.
- Red flag: the same item appearing in the at-risk bucket three weeks running. It is not at risk, it is declined, and somebody should say so.
Rules
- MUST calculate available hours before reading the task list.
- MUST name what will not happen when commitments exceed capacity.
- MUST limit the priorities to three, each one finishable.
- MUST keep the brief read-only unless asked to make a change, and confirm before changing more than one item.
- MUST treat prep for a client presentation as a task with a due date.
- NEVER pull from email. Two sources only.
- NEVER carry an item that has been overdue for more than a week without flagging it for a decision.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

