Email Sequences
v1.1.0Create segmented email sequences for abandoned carts, post-purchase follow-up, win-back campaigns, and seasonal promotions for online stores.
⭐ 0· 80·0 current·0 all-time
byLeroyCreates@leooooooow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (email sequences for ecommerce) matches the content: the skill is purely a copy/strategy generator and platform-configuration guide. It requires no binaries, credentials, or installs, which is appropriate because it produces drafts and setup notes rather than connecting to ESPs.
Instruction Scope
SKILL.md is detailed but stays on task: it instructs gathering campaign inputs, mapping sequence structure, writing subject/preview/body copy, and specifying suppression and platform setup. It does not instruct the agent to read local files, system credentials, or transmit data to external endpoints beyond advising platform configuration steps.
Install Mechanism
No install spec and no code files are included; nothing will be written to disk or fetched at install time. This is the lowest-risk model and is proportionate to the skill's purpose.
Credentials
The skill requests no environment variables, credentials, or config paths. That matches its role as a drafting/strategy tool; if a user later wants the agent to push changes into an ESP, that would reasonably require separate credentials but this skill does not request them.
Persistence & Privilege
The skill is not marked always:true and does not request persistent privileges or modify other skills. Agent invocation is allowed (platform default) but this skill's instructions are non-destructive and do not demand elevated presence.
Assessment
This skill is an instruction-only drafting and strategy guide for ecommerce email campaigns; it does not connect to external services or request credentials. Before using: (1) be careful not to paste real customer PII into prompts you send to any external AI service or save in outputs, (2) if you later want the agent to push sequences into your ESP, require explicit, separate authorization and review how those credentials will be stored/used, and (3) verify any platform-specific steps against your ESP's current documentation and your legal/compliance requirements (GDPR/CASL/CAN-SPAM) before activating sequences that process subscriber data.Like a lobster shell, security has layers — review code before you run it.
latestvk977myzga2vx1etssk3d5tkv7s83wke6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.