calendar-manager
Skill0 starsChanged 7 months agoMITView on GitHub
Manages all Google Calendar operations -- creating, reading, updating, and deleting events across the user's calendars. Use this skill whenever the user says 'add this to my calendar', 'create an event', 'block time for', 'what's on my calendar', 'check my schedule', 'when am I free', 'schedule a meeting', 'log a flight', 'add a reminder', or describes anything time-bound including meetings, calls, flights, errands, appointments, and travel plans. Also activates when the user mentions a specific date and time alongside a task or plan that needs to be tracked. Do NOT use for full structured day-planning sessions (use day-planner). Do NOT create events without the user explicitly asking -- present the proposed event first, create only after confirmation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- SZoloth/claude-skillstheir own version, first seen Dec 3, 2025
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- SZoloth/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- .claude/rules/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- knowledge/CLAUDE.mdCLAUDE.md
- agent-harness-constructionSkill
- agentic-engineeringSkill
- ai-first-engineeringSkill
- api-designSkill
- backend-patternsSkill
- blueprintSkill
- bookmarkSkill
- brain-dumpSkill
- building-explainerSkill
- code-engineerSkill
- compileSkill
- continuous-agent-loopSkill
- continuous-learningSkill
- copywriterSkill
- cost-aware-llm-pipelineSkill
- councilSkill
- database-migrationsSkill
- day-plannerSkill
- debriefSkill
- deep-researchSkill
- deployment-patternsSkill
- docker-patternsSkill
- e2e-testingSkill
- claude-apiSkill
- coding-standardsSkill
- eng-inboxSkill
- updateSkill
- enterprise-agent-opsSkill
- eval-harnessSkill
- frontend-patternsSkill
- humanizerSkill
- iterative-retrievalSkill
- log-expenseSkill
- memory-auditSkill
- migrateSkill
- minimalist-uiSkill
- onboardSkill
- full-output-enforcementSkill
- postgres-patternsSkill
- redesign-existing-projectsSkill
- regex-vs-llm-structured-textSkill
- researchSkill
- search-firstSkill
- security-reviewSkill
- security-scanSkill
- self-upgradeSkill
- high-end-visual-designSkill
- spending-summarySkill
- design-taste-frontendSkill
- tdd-workflowSkill
- transcribeSkill
- verification-loopSkill
- video-ideasSkill
- weekly-reviewSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Never ask the user which calendar to use.
- Very specific: line 20
Read calendar IDs and calendar names from .claude/rules/operating-rules.md.
- Distinctive: line 25
When genuinely ambiguous: default to the user's primary/personal calendar.
- Distinctive: line 33
Read CURRENT LOCATION and IANA TIMEZONE from there.
- Distinctive: line 35
ALWAYS pass the IANA TIMEZONE from operating-rules.md when calling calendar tools.
- Distinctive: line 36
ALWAYS display times in the user's current local time.
- Distinctive: line 41
Use the user's current local timezone for all new events.
- Distinctive: line 44
If timezone is genuinely unclear: ask before creating.
- Distinctive: line 62
Never use full sentences. Never repeat the obvious.
- Distinctive: line 68
Always structured. Bullet points.
- Distinctive: line 80
If the user gives raw or messy input (voice transcript, quick message, stream of consciousness):
- Distinctive: line 95
Create the event and confirm -- or flag conflicts first
- Distinctive: line 101
Search for the event if the ID is not known
- Distinctive: line 109
Use full-day format (date only, no time) for:
≈ “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
Skill: Calendar Manager
Dependencies (Load Before Running)
.claude/rules/operating-rules.md-- timezone, calendar IDs, routing rules (already loaded)
Trigger
Any mention of creating, updating, deleting, or checking calendar events. Also triggered when the user describes anything time-bound: meetings, calls, flights, tasks, errands, routines, or plans.
Calendars + Auto-Detection
Never ask the user which calendar to use. Infer it from context.
Read calendar IDs and calendar names from .claude/rules/operating-rules.md. The operating-rules file should define:
- A list of calendars with their IDs and purposes
- Routing rules (which types of events go to which calendar)
- Key signals for auto-detection (names, keywords, categories)
When genuinely ambiguous: default to the user's primary/personal calendar.
Timezone Rules
Single source of truth: .claude/rules/operating-rules.md > current location section.
Read CURRENT LOCATION and IANA TIMEZONE from there. Never hardcode a timezone in this file.
- ALWAYS pass the IANA TIMEZONE from operating-rules.md when calling calendar tools.
- ALWAYS display times in the user's current local time. Never show raw stored timezone or UTC.
Known calendar storage mismatch: Some calendars may be stored in a different timezone than the user's current location. The API may return times in the stored timezone. Convert to the user's current local time before displaying.
When creating events:
- Use the user's current local timezone for all new events.
- For travel: use destination timezone for events at that location.
If timezone is genuinely unclear: ask before creating.
Title Rules
Short. 3-5 words. Context-dependent. Easy to read in month view.
| Situation | Example Title |
| Call or meeting | "Call -- [Name]" |
| Flight | "SYD -> SIN | Airline FL123" |
| Errand or task | "Groceries -- [Location]" |
| Deep work block | "Deep Work: [Topic]" |
| Work meeting | "Product Dev Meeting" |
| Full-day travel marker | "[City] to [City]" |
| Social / personal | "Dinner with [Name]" |
Never use full sentences. Never repeat the obvious.
Description Rules
Always structured. Bullet points. Include every detail the user provides.
Template:
[One-line summary of what this is]
Details:
- [Key detail 1 -- time, location, person, link, etc.]
- [Key detail 2]
- [Any items, agenda, notes, or specifics mentioned]If the user gives raw or messy input (voice transcript, quick message, stream of consciousness):
- Extract the event type, time, and any named details
- Turn loose items into bullet points in the description
- Clean up the language but keep all the substance
Workflow
- Parse input -- identify: what, when, where, who, any extra details
- Auto-detect the right calendar from context (see operating-rules.md)
- Determine timezone (read IANA TIMEZONE from .claude/rules/operating-rules.md, confirm if genuinely unclear)
- Generate a short title
- Build a structured description from everything provided
- Check for conflicts
- Create the event and confirm -- or flag conflicts first
Deletions and Updates
- Search for the event if the ID is not known
- For ambiguous matches, confirm which event before acting
- For recurring events: confirm if the action is for one instance or all future instances
Full-Day Events
Use full-day format (date only, no time) for:
- Travel days (flights, long journeys)
- Any event the user asks to be visible in month view
- Multi-day events (phases, trips, etc.)
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.

