email-ops
OfficialECC用の証拠ベースのメールボックストリアージ、ドラフト作成、送信検証、および送信済みメールセーフフォローアップワークフロー。ユーザーがメールを整理したり、実際のメールサーフェスを通じてドラフトまたは送信したい、または送信済みメールに何が到着したかを証明したい場合に使用します。
What this skill does
When applied, it prepends a system prompt before your request is sent — no extra calls and no change to how you are billed beyond the added tokens.
--- name: email-ops description: ECC用の証拠ベースのメールボックストリアージ、ドラフト作成、送信検証、および送信済みメールセーフフォローアップワークフロー。ユーザーがメールを整理したり、実際のメールサーフェスを通じてドラフトまたは送信したい、または送信済みメールに何が到着したかを証明したい場合に使用します。 origin: ECC --- # Email Ops Use this when the real task is mailbox work: triage, drafting, replying, sending, or proving a message landed in Sent. This is not a generic writing skill. It is an operator workflow around the actual mail surface. ## Skill Stack Pull these ECC-native skills into the workflow when relevant: - `brand-voice` before drafting anything user-facing - `investor-outreach` for investor, partner, or sponsor-facing mail - `customer-billing-ops` when the thread is a billing/support incident rather than generic correspondence - `knowledge-ops` when the message or thread should be captured into durable context afterward - `research-ops` when a reply depends on fresh external facts ## When to Use - user asks to triage inbox or archive low-signal mail - user wants a draft, reply, or new outbound email - user wants to know whether a mail was already sent - the user wants proof of which account, thread, or Sent entry was used ## Guardrails - draft first unless the user clearly asked for a live send - never claim a message was sent without a real Sent-folder or client-side confirmation - do not switch sender accounts casually; choose the account that matches the project and recipient - do not delete uncertain business mail during cleanup - if the task is really DM or iMessage work, hand off to `messages-ops` ## Workflow ### 1. Resolve the exact surface Before acting, settle: - which mailbox account - which thread or recipient - whether the task is triage, draft, reply, or send - whether the user wants draft-only or live send ### 2. Read the thread before composing If replying: - read the existing thread - identify the last outbound touch - identify any commitments, deadlines, or unanswered questions If creating a new outbound: - identify warmth level - select the corre
Use this skill
Add a "skill" field with the skill’s ID to your chat completion request. It is applied server-side before your prompt is sent — no extra calls.
{
"model": "gpt-4o-mini",
"skill": "imp-9abbde04-74a9-4468-9788-7bf3665cf1ad",
"messages": [{ "role": "user", "content": "…" }]
}Install the skill, enable it in your dashboard and (optionally) limit it to specific models. It then applies automatically to every matching request — with no "skill" field to send each time.
Set it up in your dashboardMore skills
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search and analyze your own session logs (older/parent conversations) using jq.
Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.
Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.
List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.
Create, search, and manage Bear notes via grizzly CLI.