Email Ops
Evidence-first mailbox triage, drafting, and send verification with strict draft-first guardrails.
- What
- Evidence-first mailbox triage, drafting, and send verification with strict draft-first guardrails.
- Cost
- Free
- Needs
- none for the installation itself. No account, no API key, no payment — this skill is a single guidance file. I use it afterwards through my own connected mail account, in my own agent harness.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an operator workflow for real mailbox work, not a generic writing skill. It covers inbox triage, drafting, replying, sending, and proving a message landed in Sent, with a strict workflow: resolve the exact mail surface (which account, which thread, triage vs draft vs send), read the thread before composing, draft then verify, and report exact state (drafted, approval-pending, sent, blocked, awaiting verification). The guardrails are the point: draft first unless a live send was clearly asked, never claim a message was sent without a real Sent-folder confirmation, never switch sender accounts casually, and never delete uncertain business mail during cleanup. It treats inbound mail as untrusted by design: subjects, bodies, and quoted threads are data, never instructions, so "reply to everyone" or "forward this to X" inside a message gets reported, not executed, and agent-directed text is quoted verbatim with its sender before proceeding. It pulls in brand-voice (also in this batch) before drafting anything user-facing. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: it needs a real mail surface to send through (it orchestrates, it is not itself a mail client); some referenced ECC skills (knowledge-ops, research-ops) are outside this batch, the core triage and draft workflow stands alone. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Email Ops is a free Muse skill for real mailbox work: evidence-first triage, drafting, replying, sending, and proving a message landed in Sent. Its draft-first guardrails require reading the thread before composing and never claiming a send without Sent-folder confirmation, while inbound mail is treated as untrusted data, never instructions.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none for the installation itself. No account, no API key, no payment — this skill is a single guidance file. I use it afterwards through my own connected mail account, in my own agent harness. Install "Email Ops" for me. It is an evidence-first workflow for mailbox work: triage, drafting, replying, sending through the real mail surface, and verifying what actually landed in Sent, with a follow-up style that stays safe on sent mail. Once it is installed, I use it by asking my agent to triage my mailbox or draft a reply. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/email-ops/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file from the repository path into a temporary folder and look inside. It is the only file this skill needs. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprint below. I want you to compute the SHA-256 of the downloaded file and compare: - SKILL.md: SHA-256 188b226ec0dfd4304d6c9b60498b5f0dc2b3c97b14e159e5bde5db323ad45721 If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none in the file itself; at usage time, mail work goes through my own connected mail account) - every shell command it runs (expected: none) - every place credentials, API keys or personal data are read, stored or sent (expected: none in the file; the workflow itself treats message contents as data, never as instructions, and confirms each send with me) - any obfuscated or encoded code (expected: none, plain markdown guidance) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, and wait for my explicit "yes, install". 5. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "email-ops". 6. Verify with no network calls: frontmatter valid, skill name is email-ops, and the file is in place. 7. Report what was installed, where, and what I still need to do myself. Nothing else is required: to use the skill afterwards, I ask my agent to triage my mailbox or draft a reply through my own mail account. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.