Add Email Coach skill

[Tony Brooks (Fab-Tony)]

Adds submissions/email-coach/ — a skill that coaches a draft email rather than
just proofreading it: it returns a reader's-eye read-back, a redraft, and the
reasoning behind each change, so the writer improves over time.

Why this one. The writing tag currently covers brand voice, style analysis,
content quality, blog structure, LinkedIn and outreach — but nothing for the
single most common piece of business writing. This fills that gap.

What's in it

• Three coaching layers in order: intent → content → expression, so prose never
  gets polished on top of a broken foundation.
• A full house standard: inverted-pyramid structure, one coherent purpose per
  email, explicit ask with a by-when, a single named owner to avoid diffusion of
  responsibility, active voice, specific subject lines.
• Difficult situations: bad news without tipping into passive-aggressive, the
  late reply, and chasing a thread that's being ignored.
• An anti-pattern list including an inlined AI-tells catalogue.
• A cited evidence base (Concordia, Ohio State, plainlanguage.gov, Lumen, and
  You et al., Journal of Marketing 2020 on thank-you versus sorry).

Microsoft 365 integration. The redraft is always delivered in chat with the
coaching attached. If the official Microsoft 365 connector is present, the skill
then offers to create an Outlook draft under strict rules: recipient fields stay
empty so an accidental send is harmless, a bold AI-disclosure line sits above the
greeting that the user must delete, and it never sends. No other mail connector
is offered. Without the connector it falls back to a paste-safe copy block.

Shape. SKILL.md + metadata.json + README.md. Fully self-contained — no
scripts/, references/ or assets/, so no download bundle is generated.

Validation. Run locally against this repo at main:

• npm run check:submissions — all submissions pass
• npm run import:submissions — generates src/content/skills/email-coach.md
• npm run build — 385 pages built, detail page renders the README correctly

This is a fork PR, so CI runs validate-only and no generated files are committed
back to the branch. src/content/skills/email-coach.md is therefore not included
here — happy to commit the generated page if you'd prefer it in the PR, otherwise
npm run import:submissions after merge will produce it.

Provenance and licence. Adapted from FutureAbility's internal email coach,
generalised for public use. Contributed under the repository's MIT licence.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new “Email Coach” submission, including metadata and a detailed skill spec, to support coaching users on rewriting emails with explanations and (optionally) creating Microsoft 365 Drafts safely.

Changes:

• Added metadata.json describing the Email Coach submission (name, platforms, tags, author, version, dates).
• Added a comprehensive SKILL.md defining coaching modes, drafting rules, and Microsoft 365 Drafts constraints.
• Added a README.md summarizing the skill’s purpose, behavior, and setup expectations.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
submissions/email-coach/metadata.json	Introduces submission metadata used for cataloging and discovery.
submissions/email-coach/SKILL.md	Defines the skill behavior and detailed coaching/drafting rules (core of the submission).
submissions/email-coach/README.md	Provides user-facing overview and operational notes for the submission.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Tony Brooks (Fab-Tony)]

@microsoft-github-policy-service agree company="FutureAbility Pty Ltd"

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.