email-writer

email-writer is a skill for Claude Code from bjorn-ingmanson/thefroject-plugins. It costs 14 tokens per session (938 once invoked), scanned A, original, MIT.

A guide for writing clear business emails. It starts by identifying the recipient, purpose, requested action, and deadline, then chooses a suitable structure and tone.

In plain words
What is it for?
Use it to draft requests, updates, follow-ups, introductions, escalations, and payment messages. It can also match a company voice by checking existing guidance and example emails.
Why use it?
It helps turn vague or overly long messages into emails with a clear purpose and an obvious next step for the reader.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the thefroject-customer-success plugin — 47 skills, 11 commands shipped together

Good fit Use it to draft requests, updates, follow-ups, introductions, escalations, and payment messages. It can also match a company voice by checking existing guidance and example emails.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bjorn-ingmanson/thefroject-plugins/email-writer
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 bjorn-ingmanson/thefroject-plugins --skill email-writer
Clone the repo
git clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-plugins

Made for: Claude Code.

Or install thefroject-customer-success, the plugin that ships this one along with the rest of its 47 skills, 11 commands.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/email-writer/github.svg)](https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/email-writer)
Your own site
<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/email-writer"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/email-writer/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 email-writer

Your own site · 80×15
<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/email-writer"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/email-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 938 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.00014 $0.00938
Opus 5 $0.00007 $0.00469
Sonnet 5 $0.00003 $0.00188
Haiku 4.5 $0.00001 $0.00094

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

Security

Grade A, and why

email-writer 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 9d 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.

customer-success/skills/email-writer/SKILL.md · 106 lines

How it starts

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

Email Writer

You write emails that get read and get responses. Every email has one job. Identify that job before writing a single word.

Gather Context First

Check context/ files for voice guidelines and audience information. If content-library/ has past emails to similar recipients or for similar purposes, scan one or two to match tone. Ask only for what is missing:

  1. Who is the recipient? Role, relationship, familiarity level.
  2. What is the purpose? Request, update, follow-up, introduction, escalation.
  3. What action do you need? Approval, reply, attendance, review, payment.
  4. What is the deadline? Explicit date or "no rush."

The SCQA Framework

Use Situation-Complication-Question-Answer for emails requiring persuasion or decision-making:

  • Situation: Shared context the reader already knows (1 sentence).
  • Complication: The problem, change, or tension (1-2 sentences).
  • Question: The implicit question this raises (often unstated but shapes the email).
  • Answer: Your recommendation or ask (the core of the email).

For simple informational emails, skip SCQA and use direct structure instead.

Email Anatomy

Subject Line (write last)

  • Under 50 characters. Specific, not clever.
  • Include the action needed: "Approval needed: Q3 budget by Friday"

Opening (1-2 sentences)

  • State why you are writing. No throat-clearing.
  • Good: "Following up on our Thursday call about the vendor contract."
  • Good: "Need your sign-off on the revised timeline before I send it to the client."

Body (2-4 short paragraphs)

  • Front-load the most important information.
  • One paragraph per point. No walls of text.
  • Use bold for key dates, numbers, or names the reader must not miss.
  • If listing more than 3 items, use bullet points.

Call to Action (1 sentence)

  • One CTA per email. Make it specific and time-bound.
  • Good: "Can you reply with your preferred option by end of day Wednesday?"
  • Bad: "Let me know your thoughts."

Read the full file on GitHub · 106 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. 9d ago First seen · 106 lines · 14 tokens per session scan A 7a416ed9571e

Subscribe to this mod's changes

email-writer is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 938 once invoked, about $0.0001 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens