calendar-prep
Skill8 starsChanged 5 months agoMITView on GitHub
Turns an event page, calendar invite, email, or notes into key details, an agenda, a preparation checklist, and follow-up reminders. Use when the user wants to prepare for a meeting, event, or appointment, or asks for meeting prep, an agenda, or a prep checklist before an upcoming event.
In this repository46 other files it gives its agents.
- answerSkill
- api-to-exampleSkill
- bilingual-readerSkill
- caption-assistantSkill
- chart-explainerSkill
- code-translatorSkill
- competitor-snapshotSkill
- coupon-hunterSkill
- course-fit-checkSkill
- cover-letter-builderSkill
- deal-checkerSkill
- draft-from-notesSkill
- explainSkill
- fact-checkSkill
- fix-grammarSkill
- hook-generatorSkill
- improve-writingSkill
- interview-prepSkill
- job-application-assistantSkill
- job-fit-reviewSkill
- job-offer-compareSkill
- landing-page-critiqueSkill
- linkedin-outreachSkill
- localize-textSkill
- meeting-follow-upSkill
- outline-builderSkill
- paper-readerSkill
- portfolio-project-reviewSkill
- product-review-summarizerSkill
- pronunciation-and-usageSkill
- regex-decoderSkill
- reply-assistantSkill
- repo-onboarderSkill
- rewrite-longerSkill
- rewrite-shorterSkill
- social-post-generatorSkill
- source-finderSkill
- source-listSkill
- study-planSkill
- style-matchSkill
- summarizeSkill
- table-to-csvSkill
- term-explainerSkill
- terminology-keeperSkill
- tone-rewriterSkill
- translateSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 18
Add follow-up reminders only for explicit deadlines, named required actions, or missing/ambiguous logistics or attendance statuses that the …
- Distinctive: line 19
If key details like date, time, or location are missing or ambiguous, flag them so the user can confirm before relying on the prep.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Calendar Prep
Turn the user's event page, calendar invite, email, or notes into everything they need to show up prepared. Work only from what is present; never invent attendees, times, locations, commitments, questions, or follow-up actions.
- Extract title, date/time, timezone, location or link, attendees, RSVP/status labels, purpose, agenda items, documents, and deadlines.
- Identify what the user should read, prepare, bring, decide, or ask before the event, but include only items directly supported by the source.
- Draft a short agenda from stated agenda items, purpose, or required decisions.
- Add follow-up reminders only for explicit deadlines, named required actions, or missing/ambiguous logistics or attendance statuses that the source itself exposes.
- If key details like date, time, or location are missing or ambiguous, flag them so the user can confirm before relying on the prep.
Return these sections, omitting any that do not apply: Event summary, Prep checklist, Agenda, Questions to ask, Follow-up reminders. Preserve names, numbers, links, dates, and attendee RSVP/status labels exactly as given. Do not infer availability or RSVP status: if someone is listed as maybe, declined, no response, optional, accepted, or similar, keep that label or omit attendance status rather than rewriting it as confirmed attendance. Treat Questions to ask as optional: include it only when the source states an uncertainty, missing detail, blocker, deadline, required decision, or explicit topic the user must ask about; do not convert ordinary agenda items into generic questions. Treat Follow-up reminders as optional and factual: do not add recap emails, stakeholder sign-offs, capacity checks, separate follow-ups, or decision prompts unless the source explicitly requires them. When unsure, omit the optional item rather than inventing useful-sounding prep. Respond in the same language as the user's request.
Example
Invite (selected text):
Subject: Q3 roadmap review Thu, time TBD — Zoom (link to follow) With Priya (PM), Marcus (eng lead) Bring updated estimates; decide whether billing fix ships this quarter
Output:
Event summary
- Q3 roadmap review with Priya (PM) and Marcus (eng lead), Thursday on Zoom.
- Goal: align on the roadmap and decide whether the billing fix ships this quarter.
Prep checklist
- Update and bring your estimates.
- Review the current billing fix status before the call.
Agenda
- Walk through updated estimates.
- Decide: does the billing fix ship this quarter?
Questions to ask
- What's blocking the billing fix today?
Follow-up reminders
- Confirm the start time (listed as TBD) and watch for the Zoom link.
Date is set but the start time and meeting link aren't in the invite — confirm both before the meeting.
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.

