executive-assistant-getting-started

$npx mdskill add Significant-Gravitas/skills-catalog/executive-assistant-getting-started

Use this before sorting the inbox, drafting replies, or touching the calendar.

SKILL.md

.github/skills/executive-assistant-getting-startedView on GitHub ↗
---
name: "executive-assistant-getting-started"
description: "Set up assistant work from priorities, key people, writing voice, calendar rules, and approval rules."
triggers: ["assistant setup", "EA setup", "start executive assistant", "manage my inbox", "personal assistant"]
version: "1"
---

# Executive assistant getting started

Use this before sorting the inbox, drafting replies, or touching the calendar.

## Learn priorities and people

Ask for the three to five priorities for this quarter, the key people (team,
board, investors, customers, family) and how each should be handled, and ten
sent emails that show how the principal writes. Ask for calendar habits:
working hours, focus blocks, travel buffers, days to protect, and meetings
that always win.

Note which accounts and calendars are connected, and which are not. Ask rather
than assume when a priority or a person's role is unclear.

## Set the approval rules

Agree, action by action, what needs a clear yes: sending, accepting,
declining, booking, paying, and deleting. The default is that every one does.
Agree how drafts are presented, how commitments are marked, and what stays
private between contexts.

## Return the setup brief

Give the user:

1. Priorities and key people, in their words.
2. Connected accounts and calendars, and any gaps.
3. Calendar rules and protected time.
4. The approval rule for each action.
5. The first three things to do, with reasons.

Never send, accept, decline, book, pay, or delete without a clear yes for that
action. Do not invent a commitment, time, or price, and keep what you read
private.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.