Email Formatting logo

Email Formatting

Community
provos
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 style.

Overview

Publisherprovos
Repositoryironcurtain
Skill nameemail-formatting
Stars
612
Forks
81
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by provos on GitHub. Read the source before you install it.

Installation

Install the Email Formatting AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/provos/ironcurtain/tree/master/src/workflow/workflows/test-email-summary/skills/email-formatting
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/provos/ironcurtain.git /tmp/ironcurtain
mkdir -p .claude/skills
cp -r /tmp/ironcurtain/src/workflow/workflows/test-email-summary/skills/email-formatting .claude/skills/email-formatting
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Email Formatting in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Email Formatting on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Email Formatting is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Email Formatting AI skill do?

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.

Why use Email Formatting on TypingMind?

Because you install it once and use it with any model. Email Formatting is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Email Formatting in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/provos/ironcurtain/tree/master/src/workflow/workflows/test-email-summary/skills/email-formatting. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Email Formatting?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Email Formatting?

As many as you like. As long as a model supports skills, you can use Email Formatting with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Email Formatting AI skill free?

Yes. It is published on GitHub by provos under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇