Skill

Draft email

Compose an email draft with the team's voice. Does not send. Use when the user wants to reply to or start an email thread and wants a draft to review.

npx claudepluginhub sitloboi2012/team-marketplace --plugin team-core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

**Invocation: user only.** This skill never sends. It drafts, and the user sends.

SKILL.md

Similar Skills

cache-components

139.3k

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Draft email

Invocation: user only. This skill never sends. It drafts, and the user sends.

Workflow

1. Understand the thread

If $ARGUMENTS is a Gmail thread ID or links to one, pull that thread via the Google Workspace MCP.

If $ARGUMENTS is "reply to " or similar, search the inbox and pick the most recent matching thread; confirm with the user before proceeding.

If $ARGUMENTS is a new recipient + topic, just draft new.

If the Google Workspace MCP isn't connected, stop and tell the user.

2. Gather context

Before drafting, quickly check whether the team has context that should inform the reply:

If the thread references a Notion page, link, or project, check Notion for it.

If the sender is someone the user has exchanged Slack DMs with recently, briefly scan the last ~48h.

Do this in parallel and don't block on it if nothing's there.

3. Draft

Show the draft in this format:

To: <recipient> Cc: <anyone, or blank> Subject: <subject> <body>

Voice rules (from team CLAUDE.md):

Short, direct, action-first. Lead with the ask or the answer.

No "I hope this finds you well" / "Just checking in" / "Wanted to circle back".

Explicit timezones when proposing times.

Sign off with just the user's first name unless the context is formal/external.

Length rules:

Most replies should be 3–7 sentences. Less if a one-liner will do.

If you find yourself writing 3+ paragraphs, consider whether this should be a Notion doc + a short email linking to it — and suggest that to the user.

4. Wait, then…

Show the draft. The user edits or approves. Do not use the Google Workspace MCP's send tool until the user explicitly says "send it" (or equivalent). On approval, send and report back the message ID.

Common mistakes to avoid:

Don't pre-fill a send_at or schedule. Just send when the user says send.

Don't CC people the user didn't mention.

Don't attach anything unless the user asked.

Draft email

Invocation: user only. This skill never sends. It drafts, and the user sends.

Workflow

1. Understand the thread

If $ARGUMENTS is a Gmail thread ID or links to one, pull that thread via the Google Workspace MCP.
If $ARGUMENTS is "reply to " or similar, search the inbox and pick the most recent matching thread; confirm with the user before proceeding.
If $ARGUMENTS is a new recipient + topic, just draft new.
If the Google Workspace MCP isn't connected, stop and tell the user.

2. Gather context

Before drafting, quickly check whether the team has context that should inform the reply:

If the thread references a Notion page, link, or project, check Notion for it.
If the sender is someone the user has exchanged Slack DMs with recently, briefly scan the last ~48h.
Do this in parallel and don't block on it if nothing's there.

3. Draft

Show the draft in this format:

To: <recipient>
Cc: <anyone, or blank>
Subject: <subject>

<body>

Voice rules (from team CLAUDE.md):

Short, direct, action-first. Lead with the ask or the answer.
No "I hope this finds you well" / "Just checking in" / "Wanted to circle back".
Explicit timezones when proposing times.
Sign off with just the user's first name unless the context is formal/external.

Length rules:

Most replies should be 3–7 sentences. Less if a one-liner will do.
If you find yourself writing 3+ paragraphs, consider whether this should be a Notion doc + a short email linking to it — and suggest that to the user.

4. Wait, then…

Common mistakes to avoid:

Don't pre-fill a send_at or schedule. Just send when the user says send.
Don't CC people the user didn't mention.
Don't attach anything unless the user asked.