How do I install the JSON Schema Emails skill?

Run npx skillmds@latest add provos/json-schema-emails in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is JSON Schema Emails safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with JSON Schema Emails?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is JSON Schema Emails free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published JSON Schema Emails?

provos (@provos) published this skill. Their other Agent Skills are listed on their SkillMD profile.

JSON Schema Emails by provos — Agent Skill

Name: JSON Schema Emails
Author: provos

JSON Schema Emails

Canonical shape of the .workflow/emails/emails.json file passed between the fetch and summarize states — required fields (sender, recipient, subject, date, body), types, and field semantics. Read this whenever you write or read emails.json so producer and consumer agree on the shape.

provos 29b1382 2 files · 3.1 KB Updated Sep 17, 2026

File contents

emails.json schema

The fetch state writes .workflow/emails/emails.json and the summarize state reads it. The file is a single JSON array of email objects. The canonical JSON Schema is in the sibling file schema.json; this document explains the fields and their semantics.

Top-level shape

A JSON array. Each element is an email object. The array order is preservation order — the consumer renders emails in the order they appear, so the producer should write them in the order it wants them rendered (typically newest-first as returned by the API).

Email object fields

All fields are required and must be strings unless noted.

sender — the From address. Format Name <addr@example.com> if the source provides a display name, else the bare address.
recipient — the To addresses, comma-separated. If the source has multiple To recipients they are joined with , (comma + space). CC and BCC are not represented in this schema.
subject — the email subject line, verbatim. Empty string is allowed if the source has no subject; do not substitute "(no subject)".
date — the date as it appears in the source headers (RFC 2822 or whatever the API returns). Do not reformat or normalize the timezone.
body — the message body as plain text. If the source is HTML, the producer is responsible for stripping tags before writing. Newlines are preserved; tabs are replaced with two spaces.

Validating

The sibling schema.json is a draft-2020-12 JSON Schema. Tooling that needs to validate the file structurally should load it from there; this document is the human-readable companion.

---name: json-schema-emailsdescription: Canonical shape of the .workflow/emails/emails.json file passed between the fetch and summarize states — required fields (sender, recipient, subject, date, body), types, and field semantics. Read this whenever you write or read emails.json so producer and consumer agree on the shape.---# emails.json schemaThe fetch state writes `.workflow/emails/emails.json` and the summarizestate reads it. The file is a single JSON array of email objects. Thecanonical JSON Schema is in the sibling file `schema.json`; this documentexplains the fields and their semantics.## Top-level shapeA JSON array. Each element is an email object. The array order ispreservation order — the consumer renders emails in the order theyappear, so the producer should write them in the order it wants themrendered (typically newest-first as returned by the API).## Email object fieldsAll fields are required and must be strings unless noted.- `sender` — the From address. Format `Name <addr@example.com>` if the source provides a display name, else the bare address.- `recipient` — the To addresses, comma-separated. If the source has multiple To recipients they are joined with `, ` (comma + space). CC and BCC are not represented in this schema.- `subject` — the email subject line, verbatim. Empty string is allowed if the source has no subject; do not substitute "(no subject)".- `date` — the date as it appears in the source headers (RFC 2822 or whatever the API returns). Do not reformat or normalize the timezone.- `body` — the message body as plain text. If the source is HTML, the producer is responsible for stripping tags before writing. Newlines are preserved; tabs are replaced with two spaces.## ValidatingThe sibling `schema.json` is a draft-2020-12 JSON Schema. Tooling thatneeds to validate the file structurally should load it from there; thisdocument is the human-readable companion.

Frequently asked questions