office:calendar-management

office:calendar-management is a skill for Claude Code from harperreed/office-admin-claude. It costs 33 tokens per session (2,492 once invoked), scanned A, original, MIT.

A calendar-management guide for creating events and coordinating meetings. It handles working hours, availability, conflicts, recurring events, and time-zone conversions.

In plain words
What is it for?
Use it to add events from emails, check conflicts, reserve tentative time, block focus time, and schedule meetings around availability.
Why use it?
It helps prevent double-bookings and scheduling outside your preferred hours. It also makes international meeting times clearer by showing the relevant time zones.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Part of the office-admin plugin — 4 skills, 3 commands, 4 MCP servers shipped together

Good fit Use it to add events from emails, check conflicts, reserve tentative time, block focus time, and schedule meetings around availability.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/harperreed/office-admin-claude/calendar-management
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add harperreed/office-admin-claude --skill calendar-management
Clone the repo
git clone --depth 1 https://github.com/harperreed/office-admin-claude

Made for: Claude Code.

Or install office-admin, the plugin that ships this one along with the rest of its 4 skills, 3 commands, 4 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for office:calendar-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/harperreed/office-admin-claude/calendar-management/github.svg)](https://agentmods.dev/skills/harperreed/office-admin-claude/calendar-management)
Your own site
<a href="https://agentmods.dev/skills/harperreed/office-admin-claude/calendar-management"><img src="https://agentmods.dev/badge/skills/harperreed/office-admin-claude/calendar-management/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for office:calendar-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/harperreed/office-admin-claude/calendar-management"><img src="https://agentmods.dev/badge/skills/harperreed/office-admin-claude/calendar-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,492 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.02492
Opus 5 $0.00016 $0.01246
Sonnet 5 $0.00007 $0.00498
Haiku 4.5 $0.00003 $0.00249

Measured 12d ago against content hash 7acfce78e116, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

office:calendar-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/calendar-management/SKILL.md · 381 lines

How it starts

The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Calendar Management with Office Admin

When to Use This Skill

Use this skill when:

  • Adding events from emails
  • Checking for scheduling conflicts
  • Creating calendar holds for tentative events
  • Converting timezones for international contacts
  • Managing working hours and availability
  • Blocking focus time or recurring events

User Calendar Preferences

Load preferences from ~/.claude/office-admin-config.json:

{
  "personal": {
    "timezone": "America/Chicago",
    "workingHours": {
      "start": "09:30",
      "end": "16:30",
      "lunchStart": "12:00",
      "lunchEnd": "13:30"
    }
  },
  "calendar": {
    "defaultDuration": 30,
    "bufferMinutes": 15,
    "schedulingLink": "https://user.cal.com/schedule",
    "autoAddFromEmail": true,
    "eventNaming": {
      "includeLocation": true,
      "includeAttendees": false
    }
  }
}

Core Principles

  1. Always check conflicts first - Before committing to an event
  2. Respect working hours - Use user's configured schedule
  3. Handle timezones carefully - Convert accurately, show both zones
  4. Be proactive - Auto-add events from emails when configured
  5. Use descriptive titles - Include location/context per user preference

Adding Events from Emails

Step 1: Extract Event Details

Look for in the email:

  • Date and time (or phrases like "tomorrow", "next Tuesday", "in two weeks")
  • Duration (or use defaultDuration from config)
  • Location (physical address, restaurant name, virtual link)
  • Event type (meeting, lunch, coffee, party, etc.)
  • Attendees (who else is invited)
  • Special notes (dress code, what to bring, etc.)

Step 2: Parse Relative Dates

Handle conversational dates:

  • "tomorrow" → current date + 1 day
  • "next Monday" → next occurrence of Monday
  • "in two weeks" → current date + 14 days
  • "Dec 5" → December 5 of current year (or next if passed)

Step 3: Check Calendar for Conflicts

BEFORE creating the event:

# Get user's calendar for that date
mcp__pd__google_calendar-list-events(
  instruction="Get all events for [date], between [start_time - bufferMinutes] and [end_time + bufferMinutes]"
)

Read the full file on GitHub · 381 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 381 lines · 33 tokens per session scan A 7acfce78e116

Subscribe to this mod's changes

office:calendar-management is a skill published in the GitHub repository harperreed/office-admin-claude (5 stars, last pushed 9mo ago), licensed MIT. It adds 33 tokens to every session and 2,492 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories