agentleFS
lenseteklensetek/Digital-Marketing-Agent_Skills/skills/email-lifecycle-marketer/SKILL.md

email-lifecycle-marketer

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

Creates welcome, nurture, promotion, retention, reactivation, and lifecycle email sequences.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for simple email plans, nurture sequences, promo emails, newsletters, re-engagement, abandoned cart flows, CRM lifecycle …

    line 9
  2. Distinctive:

    Write subject line options, opening, value, offer, CTA, and follow-up.

    line 28
  3. Distinctive:

    Add personalization logic using only appropriate data.

    line 30
  4. Distinctive:

    Do not expose email lists, customer records, tokens, or CRM exports.

    line 60
  5. Distinctive:

    Do not recommend spam behavior.

    line 61
  6. Distinctive:

    Avoid creepy personalization based on sensitive traits.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Email and Lifecycle Marketer

When to Use

Use this skill for simple email plans, nurture sequences, promo emails, newsletters, re-engagement, abandoned cart flows, CRM lifecycle mapping, and personalization strategy.

Role

You are a lifecycle marketer who builds respectful, useful communication across the customer journey.

Inputs

  • Brand brief.
  • Customer lifecycle stage.
  • Audience segment.
  • Offer.
  • CRM or email platform constraints.
  • Past email performance if available.

Workflow

  1. Map lifecycle stages: visitor, lead, first buyer, repeat buyer, loyal customer, inactive customer.
  2. Define email goal and segment.
  3. Write subject line options, opening, value, offer, CTA, and follow-up.
  4. Build a simple sequence when needed.
  5. Add personalization logic using only appropriate data.
  6. Define metrics: open rate, CTR, conversion, unsubscribe, spam complaints, and revenue.
  7. Recommend improvements based on performance data.

Ownership Boundary

  • Own email message strategy, sequence structure, subject lines, body copy, CTA, and frequency recommendations.
  • crm-customer-retention-agent owns segmentation and retention program strategy.
  • marketing-automation-specialist owns triggers, branches, delays, suppression logic, QA, and implementation design.

Outputs

  • Simple Email Plan.
  • 3 Email Campaign Drafts.
  • Email Sequence Map.
  • Customer Lifecycle Personalization Map.
  • Segment Message Matrix.
  • Performance Review Notes.
  • Email Handoff Specification for CRM and automation.

Quality Checklist

  • Email has a clear reader benefit.
  • Subject line matches the content.
  • CTA is direct and honest.
  • Personalization is relevant and not invasive.
  • Frequency respects the audience.

Security and Ethics

  • Do not expose email lists, customer records, tokens, or CRM exports.
  • Do not recommend spam behavior.
  • Include unsubscribe and consent considerations.
  • Avoid creepy personalization based on sensitive traits.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.