professional-email

Drafts clear professional emails with appropriate tone, structure, and calls to action.

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/openagentskills-professional-email

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Drafts clear professional emails with appropriate tone, structure, and calls to action. Use when writing work email, follow-ups, apologies, requests, or stakeholder updates.

Use cases: writing, productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/professional-email

What's inside

Skill name: professional-email
Description: Drafts clear professional emails with appropriate tone, structure, and calls to action. Use when writing work email, follow-ups, apologies, requests, or stakeholder updates.
License: MIT
Instructions: 50 lines in SKILL.md · view on GitHub

Files (2)

SKILL.md
skill.manifest.yaml

SKILL.md (first lines)

# Professional Email

## Gather (ask if missing)

- Recipient relationship (peer, manager, client, external)
- Goal (inform, request, apologize, escalate)
- Desired response and deadline
- Tone preference (neutral, warm, firm)

## Structure

1. **Subject** — Specific, ≤60 chars when possible
2. **Opening** — Purpose in first sentence
3. **Body** — Context → ask → rationale (short paragraphs)
4. **Close** — Clear CTA + thanks/sign-off

## Tone matrix

| Situation | Tone |
|-----------|------|
| Routine update | Neutral, concise |
| Request | Polite, specific deadline |
| Delay/bad news | Direct, accountable, next step |
| Escalation | Factual, no blame language |

## Template

```
Subject: [Specific subject]

Hi [Name],

[One-sentence purpose.]

[2–4 short paragraphs with bullets if listing items.]

[Clear ask: "Could you confirm by Friday?"]

Thanks,
[Name]
```

## Rules

- No passive-aggressive phrasing
- One main ask per email when possible
- Avoid jargon with external recipients
- Do not send on user's behalf — output draft only unless tool can send

From openagentskills/betterskills, MIT.

Signals

Stars: 0
Forks: 1
Open issues: 25
Last commit (this folder): Jun 1, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/openagentskills/betterskills
Website: github.com/shahravir/betterskills#quick-start
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from openagentskills

Cite this page

professional-email skill. Agent Mart. https://agentmart.dev/skills/openagentskills-professional-email (last updated 2026-10-24)