GPTsApp Skillscommunity example · Use or study
email-drafter
Draft an email for review, using the recipient, purpose and your communication style.
github/awesome-copilotskills/email-drafter/SKILL.md
Before you use it
- Input
- Recipient, desired outcome, key points and relevant relationship context. Optional authorized correspondence can inform tone.
- Expected output
- A reviewable email draft, with a note on whether its tone came from prior correspondence or professional defaults; the source describes a local Markdown output file.
- Prerequisites
- The instructions recommend WorkIQ for Microsoft 365 context but describe a default-tone fallback without it. Check permissions before exposing correspondence. This directory neither reads your mailbox nor creates or sends an email.
Client setup and runtime behavior are not verified here; client installation is not individually established. The use notes below describe source preparation, inputs and limits.
Publisher documentation, static file observations and environment tests are different kinds of evidence. Runtime behavior has not been observed.
Use this method
Source-based preparation, not an installation or a completed run. Nothing is executed here.
- Good fit for
- Writing or revising a specific email while keeping a human review step before sending.
- Not for / limits
- Not an email sender, mailbox connector or guarantee of personal-tone matching. WorkIQ access is not provided or tested by this directory.
- Prepare
- Give the intended recipient, purpose and facts to communicate; exclude unrelated private threads and credentials.
- Apply
- Choose between an authorized correspondence-based style review and the source's professional-default fallback. Confirm which basis the draft actually used.
- Check
- Check factual details, recipient, tone and commitments yourself. The source describes draft-only behavior; sending remains a separate manual decision.
Sources read for this note
These exact files were read as text at the displayed commit. Other files and external tools were not reviewed. A repository LICENSE observation does not confirm Skill-specific applicability or dependency rights.
- skills/email-drafter/SKILL.md ↗
Read 2026-09-10T10:33:30.350Z
c3324d26f899149e5b664a02cad9fa4b1a615d9b2ce5bb7f6dfd908c17c622e8 - LICENSE ↗
Read 2026-09-10T10:33:31.265Z
e32449d23085399adc1222f7a17408b730550258e51627c153cb108ca9955823
Study the method
Examine the separation between recipient context, tone evidence and drafting. The no-history branch labels inferred tone instead of treating it as a measured personal style.
1 files in the observed scope; 0 in scripts/, 0 in references/, 0 in assets/.
Directory evidence checked 2026-09-08T14:47:50.063Z. Filenames and folder counts were observed; in that earlier check, helper file bodies were not read or executed. Later individual reads, when present, are listed in the use notes.
Zero files in scripts/ does not mean no execution, network access or file writes. Markdown and other folders may describe or contain executable behavior.
Source version and requirements
- Observed
- 2026-09-08T11:55:57.465Z
- Source commit
- f38fb6cf039b835990d0f49dc161d7c2af99ef69
- Content SHA-256
- c3324d26f899149e5b664a02cad9fa4b1a615d9b2ce5bb7f6dfd908c17c622e8
- License
- Unknown
- Author attribution
- Repository owner: github. Individual authorship is not independently established.
This page describes a pinned source snapshot, not the latest repository state. Changes after this commit have not been reconciled here. A repository license does not necessarily cover external models, datasets or services.
Open current repository ↗Reference note and manual copy
Repository license evidence
MIT text was read in the nearest repository license file at this commit. Skill-specific applicability has not been confirmed. This is not a redistribution grant for the Skill or its external services.
Read observed license file ↗- License evidence checked
- 2026-09-08T14:47:50.063Z
- License file SHA-256
- e32449d23085399adc1222f7a17408b730550258e51627c153cb108ca9955823