Skip to content
Security
Skill

/email-formatting

Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house

BOOST
From plugin
ironcurtain
6147 skills2 agents
Install
$ npx -y skills add provos/ironcurtain --skill email-formatting --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/email-formatting

Context preview

The summary Claude sees to decide when to auto-load this skill.

Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house

SKILL.md

email-formatting.SKILL.md
name: email-formatting
description: Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.

Email formatting conventions

Use these conventions whenever you write a markdown file that summarizes email content.

Heading depth

  • The document has exactly one `#` heading at the top: the report title.
  • Each individual email gets a `##` heading whose text is the email subject.
  • Do not use `###` or deeper for per-email metadata; use a bullet list instead.

Per-email metadata

For each email, render metadata as an unordered list immediately under the `##` subject heading, in this order:

  • `From: <sender>`
  • `To: <recipient(s), comma-separated>`
  • `Date: <as it appears in the source, no reformatting>`
  • `Summary: <1-2 sentences in prose>`

Line length and whitespace

  • Soft-wrap at roughly 80 columns. Don't hard-break inside a sentence.
  • Exactly one blank line between sections; never two or more.
  • No trailing whitespace at end of lines.

Emoji policy

Do not use emoji in summary documents. They render inconsistently across mail clients that may consume the markdown downstream.

Preamble and outro

There is no preamble (no "Here is the summary..." opener) and no outro (no "Let me know if..." closer). The document opens with the `#` title.

Provenance footer (required)

The document MUST end with the literal HTML comment marker on a line by itself, separated from the last email's `Summary:` bullet by exactly one blank line:

<!-- email-summary/v1 -->

This marker is how downstream tooling identifies the generator and schema version. Producers that omit it are non-compliant; producers that change the spelling, casing, or version segment break parsers that depend on the literal string. Do not localize, prettify, or expand the marker — it is a machine-readable token, not human prose.

Read more
Ships withironcurtain

A secure\* runtime for autonomous AI agents, where security policy is derived from a human-readable constitution. _\*When someone writes "secure," you should immediately be skeptical. What do we mean by secure?_

Get the whole plugin

Other skills on ironcurtain.