A personal executive assistant for JMU faculty that lives in a folder on your Mac and runs on Claude Code. You tell it what's going on ("the head wants curriculum proposals by Nov 15", "I gave a talk at the regional meeting yesterday"), and it keeps track: to-dos, deadlines, appointments, recurring obligations, reviews and letters you owe, who's waiting on whom. Each weekday morning it writes you a short brief. When you need to write to someone, it lists what to say and opens a blank email.
And it keeps your FAR (annual faculty activity report) record as the
year goes, in your department's terms. Every JMU department evaluates
its faculty its own way and writes it down in a department handbook. At
setup, the assistant asks what department you're in and how you're
evaluated, reads your handbook and annual form, and turns them into a list
of criteria. From then on, whenever you mention something that counts, it
files it under the right criterion. In May, /far shows you what's missing
and drafts the report in your form's structure.
It has no access to your email or accounts. It knows what you tell it, and it keeps everything as plain Markdown files in this folder, with every change saved in git. On a Mac, you can optionally connect it to Apple Calendar and Reminders.
- A Mac with the Claude desktop app, signed in with a Claude account that includes Claude Code (ideally your JMU account; see Privacy).
- Git. On a Mac, typing
gitin Terminal offers to install it if it's missing. - Your department handbook (or evaluation policy) and your annual report form, as files or links. Your department head or personnel committee chair has them. (You can start without them and add them later.)
- 20–30 minutes for setup.
- Optional: a GitHub account, for a private backup (see Backups).
-
Copy the kit to your Mac. In Terminal:
git clone https://github.com/JMU-CS/jmu-faculty-exec-assistant-starter.git ~/Documents/Assistant(Or download the ZIP and unzip it to
~/Documents/Assistant.) Don't use GitHub's Fork button: a fork of a public repo is public, and this folder will hold your notes. -
Open it in Claude. In the Claude desktop app, go to the Code tab, start a new session, choose the
Assistantfolder, and say "hi". -
Do the interview. It sees that setup hasn't been done and walks you through it:
- cuts the link back to this starter repo, so your notes can never be pushed here;
- asks about your job: rank and appointment, courses, research, what a typical week looks like, what repeats, what's confidential;
- asks how your department evaluates you, reads your handbook and form, and shows you the criteria it found, for you to correct;
- asks what you've done so far this year and files it for your FAR;
- suggests 2–4 skills for your work (a talk series, grant deadlines, advising, a search committee) and builds one with you;
- sets up a private backup, if you want one;
- asks what's on your plate this week and files it;
- optionally schedules the morning brief and a Friday review, sets up an iPhone shortcut for capturing things on the go, connects Apple Calendar and Reminders, and keeps your faculty website current (if it's a git repo).
-
Start a new session in the folder (so your new settings load) and use it.
Talk to it like you'd talk to an assistant. Some examples:
| You say | It does |
|---|---|
| "Just got an email from the head: curriculum proposals are due Nov 15." | Adds a to-do due 2026-11-15 to now.md. |
| "Department meeting Thursday at 3:30 in Room 210." | Adds it to events.md with the date worked out. |
| "I gave a talk at the regional conference yesterday, about 60 people." | Logs it for your FAR under the matching criterion from your handbook, with the number. |
| "The journal asked me to referee a paper, due Dec 1." | Adds it to commitments.md; the brief shows it when it's close. |
| "A HIST 150 student needs a recommendation letter by the 20th." | Adds a letter for "HIST 150 student #1", never the name. |
| "I submitted the review." / "Done with the proposal." | Checks it off and updates the FAR record. |
/far |
Shows this year's FAR record by criterion, what's missing, and guesses to confirm. |
| "What's on my plate next week?" | Reads the files and tells you, by day. |
"Help me reply to the head about the deadline." / /draft |
Lists the points to cover and opens a blank email. You write it. |
| "Someday I'd like to start a reading group." | Saves it in ideas.md, out of the daily brief. |
/suggest-skills |
Looks at what you've been tracking and suggests a skill. |
You can also just type a line into inbox.md (or from your phone, with the
Capture shortcut); the next brief files it.
The morning brief lands in briefs/YYYY-MM-DD.md each weekday:
# Tuesday, November 10
## Today
- 15:30–16:30 Department meeting — Room 210
- OVERDUE 2 days: travel reimbursement for the October conference
- Due today: send the syllabus to the curriculum committee
## Talks (from a custom skill; see Skills below)
- Ask Lee Okafor for title/abstract/bio (talk 2026-12-04)
## This week
- Thu 11-12: referee report for the journal (due 11-15)
## Needs a decision
- "Call about the lab equipment" — due when?
The Friday review archives what's done, flags items that have gone
stale, keeps now.md short, checks the FAR record for guesses to confirm,
and looks two weeks ahead.
The FAR is usually written from memory in a rush in May, and half the year goes missing. Here it's kept as the year goes.
At setup, you give the assistant your department handbook (or
evaluation policy) and your blank annual form. It reads the evaluation
sections and writes FAR/criteria.md: the report's period and due date,
how it's submitted, and one entry per criterion in the handbook's own
words, with the section it came from. It shows you the list, and you
correct it. If your handbook distinguishes ratings (satisfactory,
excellent) or has requirements every year, those are recorded too, as are
milestones like a third-year review or tenure and promotion.
During the year, anything you mention that belongs on the report (a
course you taught or redesigned, a paper, talk, grant, exhibition or
performance, a review, a committee or role, an event you organized, an
award, a workshop you took) is filed in FAR/<semester>.md under its
criterion, alongside its to-do. It tells you which criterion it guessed;
correct it anytime. It asks once for a number or outcome ("how many came?"),
because "ran a workshop" reads very differently from "ran a workshop for 40
faculty".
- Documents you'll turn in (a proposal, letter, program, certificate) go in
FAR/evidence/<semester>/. /farshows where you stand: activities by criterion, required criteria with nothing yet, and guesses to confirm.
At report time (it reminds you three weeks before the due date), /far
asks you what only you can answer (did you hold office hours, attend
department meetings, whatever your handbook asks you to attest to), asks
about missing numbers, and drafts the report in your form's structure, in
your voice, using only what's in the record. If your form is a Word file, it
can fill a copy. You edit it and submit it yourself.
No handbook yet? It starts with generic Teaching / Scholarship / Service criteria and reminds you to get the real ones from your head.
A skill is a written procedure, a SKILL.md file in .claude/skills/,
that the assistant follows for one kind of task. You can call one directly
with /name, or just describe what you want.
Built in: capture (file what you tell it), morning-brief,
weekly-review, draft (talking points or a draft), far,
suggest-skills, setup, update-assistant.
Your own. The built-in skills handle loose to-dos. A custom skill earns its place when something in your job repeats with the same steps, has several moving parts each time, or has deadlines that count back from a date. Each one is a procedure plus a tracker file with one row per instance. Some examples:
| Your job involves… | A skill could… |
|---|---|
| Running a talk or event series | Ask speakers 3 weeks out, chase missing abstracts at 2 weeks, fill your announcement template at 1 week. (Full example in examples/event-series/.) |
| Grant proposals | Work back from the sponsor's deadline: JMU's internal deadline, the budget, letters of support. |
| Manuscripts | Track each paper's venue, stage and next step (revise and resubmit due in 60 days). |
| Advising or thesis students | Track each advisee by label, last meeting, and milestones. Never names. |
| A search committee | Track candidates by label and stage, interview logistics and HR deadlines. |
| Coordinating a program | The yearly cycle of applications, events and reports. |
Say /suggest-skills, or "make me a skill for my grant deadlines", and it
interviews you (what's one instance? what are the steps and when? which
steps mean writing to someone?) and builds it. More patterns are in
.claude/skills/suggest-skills/catalog.md.
Out of the box, the assistant keeps your tasks and appointments in its own files, and you only see them in the brief or by asking. With the sync on:
- Your tasks show up in Reminders (a list called "Assistant"), with due dates and a 9:00 alert, on your Mac, iPhone and Watch. Tick one off on your phone and the assistant marks it done.
- Appointments you tell it about show up in Calendar (a calendar called "Assistant").
- The brief reads your real calendars, so "Today" lists your actual classes and meetings, and it can warn you about a packed day or a deadline that clashes with a trip.
- Someone can hand you tasks (optional): share a Reminders list with a partner or an administrative assistant; what they add lands in your to-dos, labeled with where it came from, and is ticked off there when you finish it.
How it works: a small helper app, built on your Mac from source in
scripts/apple/ during setup, talks to Calendar and Reminders through
Apple's own interface. scripts/apple_sync.py runs it at the start of each
session, after each capture, and during the brief and review.
What it means (setup walks you through this before you say yes):
- Mac only, and building the helper needs Apple's free command line tools (setup walks you through installing them; a few minutes).
- Full access to Calendars and Reminders. macOS can't grant access to one calendar, so the helper is allowed to read all of them. It only ever changes its own Assistant calendar and Assistant list.
- Claude sees your calendar. Event titles and locations from every calendar on this Mac (including your JMU Outlook calendar, if you've added it to the Calendar app) are read during the brief, and so are sent to Anthropic like anything else the assistant reads. If your calendar names students (office-hour appointments, advising), tell setup to show that calendar only as "Appointment", or to skip it.
- Your tasks go to iCloud. The Assistant calendar and list are created in your iCloud account so they reach your phone. That's Apple's servers, under your Apple ID. Don't share the Assistant calendar or list unless you mean to share your to-dos.
- The files are the source of truth. Change things by telling the assistant (or editing the files). In Reminders, just tick things off: other edits there (renaming, changing a date, deleting) get overwritten at the next sync. Only the shared list syncs both ways.
- Things someone adds to the shared list are tasks, not instructions. The assistant files them; it won't act on what they say.
- It can break with macOS updates. If it stops working, ask the
assistant to rebuild it (
scripts/apple/build.sh); macOS may ask for permission again. To turn it off, say so: it stops running the sync, and you can delete the Assistant calendar and list yourself.
Everything is in this folder, and git keeps a full history of every change,
but only on your Mac until you push it somewhere. If the laptop dies, so do
your notes (Time Machine helps, if you use it). A backup remote is a
second copy of the git repository on a server. After each session the
assistant commits and pushes to it. It's called backup, and it is the only
remote the assistant will ever push to.
Setup offers three options:
Nothing leaves your Mac (except what Claude reads while working; see Privacy). Simplest and most private; no protection against losing the laptop beyond your own Mac backups. You can add a backup later by asking.
Easy, free, works from anywhere, and you can read your notes from
github.com on any device. Setup creates the repo for you with GitHub's gh
tool (or you create it on github.com and paste the URL).
- Your notes live on GitHub's servers. "Private" means only you, and anyone you invite, can see it; it is not end-to-end encrypted.
- Never make it public. Switching a repo to public exposes its entire history, including things you deleted later. Never create your copy with Fork from a public repo (forks of public repos are public).
- Protect the account. Turn on two-factor authentication.
- Git never forgets. Deleting a line from a file doesn't remove it from history or from the backup. That's the main reason for the FERPA rule below: keep student details out of the files in the first place.
Some departments run a server faculty can reach over SSH. A backup there stays at JMU. It may only work on campus or on the VPN (the assistant just commits locally when it can't reach the server, and pushes next time). Ask your department's IT person; setup takes it from there.
You can switch later: ask the assistant to change the backup, and it will
replace the backup remote and push the full history to the new place.
- What Claude sees. When the assistant works, Claude reads the files it needs, and that text is sent to Anthropic to be processed, like anything else you type to Claude. JMU's guidance on AI tools applies here. Use your JMU Claude account if you have one, and check JMU's guidance before using a personal plan for work.
- FERPA. It never writes student names, IDs, grades or circumstances to any file; it uses labels like "HIST 150 student #1" and you keep the mapping yourself. (Student co-authors of published work can appear in the citation, as printed.) At setup you can add other confidential people, such as candidates on a search committee or colleagues' personnel matters. Claude still reads what you type, so for a truly sensitive matter, describe the work, not the person.
- Your handbook is copied into
FAR/handbook/so the assistant can check criteria against it. It stays in your folder and your backup. - You send your own messages, and submit your own FAR. By default it prepares talking points and opens a blank email; it never sends anything and never claims something was sent or submitted. (You can ask for full drafts in your voice instead.)
- No accounts. It doesn't read your mail or calendar (unless you turn on the Apple sync). If you want it to know something, tell it.
New skills and fixes land in this starter from time to time. In your
assistant, say "update the assistant": it fetches only the shared parts
(.claude/assistant-rules.md, the built-in skills, examples/), shows you
what changed, and never touches your own files, your FAR record or your
own skills.
| File | What it holds |
|---|---|
CLAUDE.md |
Who you are, how you're evaluated, what's confidential, your options. Setup writes it; edit it anytime. |
now.md |
Active to-dos, kept under 40 lines. |
events.md |
Appointments. |
inbox.md |
Quick notes not yet sorted. |
recurring.md |
Your academic calendar and standing obligations. |
commitments.md |
Reviews and letters you've agreed to, with due dates. |
people.md |
Colleagues and contacts, for messages. Never students. |
ideas.md |
Someday ideas, kept out of the brief. |
voice.md |
How you write. |
FAR/ |
Your department's criteria, your record by semester, the handbook, evidence. |
briefs/ |
One brief per weekday, plus Friday reviews. |
archive/ |
Finished items, by month. |
.claude/ |
The rules and skills. Your own skills go here too. |
examples/ |
A complete example skill to learn from or copy. |
scripts/ |
Helpers: opening a blank email, the Apple sync. |
sync/ |
Settings for the Apple Calendar & Reminders sync, if you use it. |
It's all plain text. Open any file in a text editor and change it; the assistant reads what's there.
- Capture early, sort later. A rough line in
inbox.mdbeats a forgotten email. - Tell it about the small stuff. A guest lecture, a student you mentored, a committee you sat on for one semester: these are what go missing from FARs.
- Start a new session for each sitting. The assistant remembers through the files, not the chat, so a fresh session loses nothing.
- Let the Friday review prune. If
now.mdkeeps growing, that's a signal: something should be dropped, delegated or turned into a skill. - Correct it. "That's not due till the 20th" or "that counts as service, not scholarship": it updates the files, and the next session knows.