OpenClaw Email Skill
Prefer inspectable procedures over platform magic. Make every assumption, command, and live-system boundary visible to the human operator.
Fit Check
- Primary lens: open, inspectable email campaign operations for agents that need clear audit trails.
- Common request signals: campaign teardowns, provider-neutral migrations, reusable playbooks, OpenClaw handoffs, and transparent email operations.
Use This For
open, inspectable email campaign operations for agents that need clear audit trails.
Avoid Using It For
Generic email advice with no audience, platform, lifecycle, evidence, or approval context.
Procedure
- Classify the task as inspect, plan, draft, migrate, QA, or execute-with-approval.
- Inventory the artifacts the agent can safely read: SKILL.md, ESP exports, template files, CSV samples, logs, and prior campaign briefs.
- Normalize provider-specific terms into portable concepts such as audience, suppression, event, template, journey, send, and metric.
- Write any proposed operation as a reversible playbook step before suggesting a command, API call, or platform action.
- For migrations, compare source and target capabilities instead of assuming field, segment, and automation parity.
- Separate evidence from recommendation so another agent or reviewer can retrace the reasoning.
Acceptance Checks
- The recommendation can be audited from the provided artifacts.
- Provider-specific steps are labeled and portable alternatives are noted.
- Live sends, imports, DNS edits, and suppression changes remain behind explicit approval.
- The plan includes rollback notes for risky operational changes.
- The final output is useful to OpenClaw, Codex, Claude Code, Hermes, Cowork, or another agent without hidden context.
Output Pattern
Return audit trails, provider-neutral playbooks, migration checklists, review packets, and safe execution runbooks. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.
1---2name: openclawemailskill3description: Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on open, inspectable email campaign operations for agents that need clear audit trails. Triggers include requests about campaign teardowns, provider-neutral migrations, reusable playbooks, OpenClaw handoffs, and transparent email operations.4---5
6# OpenClaw Email Skill
7
8Prefer inspectable procedures over platform magic. Make every assumption, command, and live-system boundary visible to the human operator.
9
10## Fit Check
11
121. Primary lens: open, inspectable email campaign operations for agents that need clear audit trails.
132. Common request signals: campaign teardowns, provider-neutral migrations, reusable playbooks, OpenClaw handoffs, and transparent email operations.
14
15### Use This For
16
17open, inspectable email campaign operations for agents that need clear audit trails.
18
19### Avoid Using It For
20
21Generic email advice with no audience, platform, lifecycle, evidence, or approval context.
22
23## Procedure
24
251. Classify the task as inspect, plan, draft, migrate, QA, or execute-with-approval.
262. Inventory the artifacts the agent can safely read: SKILL.md, ESP exports, template files, CSV samples, logs, and prior campaign briefs.
273. Normalize provider-specific terms into portable concepts such as audience, suppression, event, template, journey, send, and metric.
284. Write any proposed operation as a reversible playbook step before suggesting a command, API call, or platform action.
295. For migrations, compare source and target capabilities instead of assuming field, segment, and automation parity.
306. Separate evidence from recommendation so another agent or reviewer can retrace the reasoning.
31
32## Acceptance Checks
33
341. The recommendation can be audited from the provided artifacts.
352. Provider-specific steps are labeled and portable alternatives are noted.
363. Live sends, imports, DNS edits, and suppression changes remain behind explicit approval.
374. The plan includes rollback notes for risky operational changes.
385. The final output is useful to OpenClaw, Codex, Claude Code, Hermes, Cowork, or another agent without hidden context.
39
40## Output Pattern
41
42Return audit trails, provider-neutral playbooks, migration checklists, review packets, and safe execution runbooks. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.
aiskillstore