What is office:email-management?

A skill for handling email tasks and related calendar work. It covers finding messages, drafting replies, preserving conversation threads, extracting action items, and adding events.

Use it to review inboxes, draft replies for approval, manage threads, triage email in bulk, and turn event details from messages into calendar entries.

It reduces common email mistakes such as replying in the wrong conversation, omitting recipients, or creating calendar conflicts.

office:email-management — Skill for Claude Code by harperreed

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 email-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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/harperreed/office-admin-claude/email-management/github.svg)](https://agentmods.dev/skills/harperreed/office-admin-claude/email-management)

Your own site

<a href="https://agentmods.dev/skills/harperreed/office-admin-claude/email-management"><img src="https://agentmods.dev/badge/skills/harperreed/office-admin-claude/email-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/harperreed/office-admin-claude/email-management"><img src="https://agentmods.dev/badge/skills/harperreed/office-admin-claude/email-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,480 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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.02480
Opus 5	$0.00019	$0.01240
Sonnet 5	$0.00008	$0.00496
Haiku 4.5	$0.00004	$0.00248

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

Security

Grade A, and why

office:email-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 10d 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/email-management/SKILL.md · 342 lines

How it starts

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

Email Management with Office Admin

Use this skill when handling:

Checking inbox or finding specific emails
Drafting email replies
Adding events from emails to calendar
Managing email workflows
Bulk email triage

Core Principles

Always draft, never send - Save emails as drafts for user review before sending
Threading is critical - Replies must appear in the correct conversation thread
Match user's voice - Reference their office-admin config for tone and style
Extract structured data - Pull event details, action items, contact info from emails
Proactive calendar integration - Auto-check conflicts and add events

User Style Configuration

Before drafting emails, load the user's style from ~/.claude/office-admin-config.json:

{
  "email": {
    "tone": "ultra-terse" | "conversational" | "professional" | "warm",
    "signature": "none" | "minimal" | "full",
    "formality": "casual" | "standard" | "formal",
    "responseLength": "minimal" | "balanced" | "detailed",
    "patterns": ["common phrases they use"],
    "customGuidelines": "Additional freeform style notes"
  }
}

If config doesn't exist, prompt user to run /setup-office-admin first.

Email Drafting Workflow

Step 1: Find the Thread

When drafting a reply, ALWAYS search for the original email first:

Search for: [subject] from [sender name]
Get: Full email content, thread ID, message ID, recipient email

Why: You need context AND threading information. Skipping this = standalone draft instead of threaded reply.

Step 2: Get Threading Details

Extract from search results:

thread_id - Links all messages in the conversation
message_id - The specific message you're replying to (usually most recent)
recipient_email - The To: address (CRITICAL - tool doesn't auto-extract!)

Critical: All three are required for proper threading. Missing any = broken draft.

Step 3: Draft Using User's Voice

Reference their config for:

Read the full file on GitHub · 342 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.

10d ago First seen · 342 lines · 39 tokens per session scan A 25466ab44ea9

Subscribe to this mod's changes

office:email-management is a skill published in the GitHub repository harperreed/office-admin-claude (5 stars, last pushed 9mo ago), licensed MIT. It adds 39 tokens to every session and 2,480 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.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

office:email-management