agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/copilot-studio-gallery/submissions/sales-analyser/solution/botcomponents/crf9c_salesanalyser_WEs93i.file.skillmd_oCdhy/filedata/SKILL.md

newsletter-style-email-composer

Skill14 starsChanged 11 days agoMITView on GitHub

Use when the user asks to email a report, findings, or metrics to someone as a polished, newsletter-style message. Builds an Outlook-safe HTML email from figures that already exist (headline, KPI tiles, up to two bar charts drawn with HTML table cells so they render in classic Outlook, Gmail and dark mode, short findings, data notes and the non-audit disclaimer) using the shared brand tokens, attaches the PDF report, and creates a draft for the user to review. Do NOT use for a short plain-text status update, or for building the underlying analysis, charts, or report itself -- this skill only composes the email.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Recipients and subject: Ask if not given; the email is a draft, so a sensible subject is fine.

    line 19
  2. Very specific:

    No images in the body: - no base64 data: images, no SVG, no external image URLs.

    line 31
  3. Very specific:

    Use the Draft an email message tool: To, Subject, Body = contents of email.html, and Attachments = the PDF, named per …

    line 39
  4. Distinctive:

    If the tool rejects the attachment, tell the user and give them the PDF as a chat attachment instead.

    line 43
  5. Distinctive:

    Never upload it to SharePoint.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Newsletter-style email composer

Composes the email only. Figures, Data notes and the PDF come from the analysis and report skills - if they don't exist yet, run those first. Never recompute a number here.

Branding - edit here. Colours, font stack, eyebrow and the footer disclaimer come from spreadsheet-data-analysis-reporting/assets/style-tokens.json, the single brand file shared with the charts and the PDF. The template in this skill contains no colour values. Logo: not shown in the email by design. Without a base64 data: image the only options are an inline (CID) attachment - which the Draft an email tool can't create - or an externally hosted image URL, which most clients block by default. The logo appears in the attached PDF; swap it via brand.logo_path.

1. Gather (ask only for what's missing)

  • Recipients and subject. Ask if not given; the email is a draft, so a sensible subject is fine.
  • Content to reuse: headline, 2-4 KPIs, the figures behind 1-2 simple charts, up to 3 bullets per finding, recommendations, the Data notes.
  • The PDF (report.pdf) in the sandbox working folder, from the report skill.

2. Build the body

Copy assets/email-content-example.json to email_content.json, fill it in, then run:

python scripts/build_email.py email_content.json email.html --pdf report.pdf
  • Charts are HTML table-cell bars (bar_charts): mode: "bars" for values (use highlight for the focus item), mode: "variance" for change (positive/negative colours plus signed labels). Max 2 charts, 8 bars.
  • No images in the body - no base64 data: images, no SVG, no external image URLs. The full charts are in the attached PDF.
  • The script fills brand tokens, sets the hidden preheader (headline by default), adds the "full report is attached as a PDF" line, the Data notes footnote and the disclaimer, and warns if the body nears Gmail's 102 KB clipping limit or the PDF is large. It also writes email.html.attachment.json (PDF name and sandbox path).

3. Create the draft

Use the Draft an email message tool: To, Subject, Body = contents of email.html, and Attachments = the PDF, named per email.html.attachment.json and referenced by its sandbox file path. The tool reads the file from that path, so don't base64-encode the PDF or paste its content into the conversation.

  • If the tool rejects the attachment, tell the user and give them the PDF as a chat attachment instead. Never upload it to SharePoint.
  • Tell the user it's a draft waiting in their mailbox for review - nothing is sent.

Done when

Headline, KPIs, bars and bullets match the analysis; Data notes and disclaimer are present; the PDF is attached; build_email.py ran without errors; the draft exists with the right recipients and subject. Rendering rules and client quirks: references/email-rendering-and-accessibility-notes.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free