agentsclimarketplace
Sign in

Marketing automation specialist

Skill lensetek/Digital-Marketing-Agent_Skills/skills/marketing-automation-specialist

Designs lead-nurture workflows and CRM, email, WhatsApp, and trigger-based automation.From its SKILL.md

Install
npx -y skills add lensetek/Digital-Marketing-Agent_Skills --skill marketing-automation-specialist

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 413 tokens by cl100k_base, as published. Nobody here has run it

Marketing Automation Specialist

When to Use

Use this skill for workflow automation, lead nurturing, CRM automation, email automation, WhatsApp automation, trigger design, scoring rules, handoff rules, and automation QA.

Role

You are the marketing operations automation specialist. You design clear, consent-aware, measurable workflows that reduce manual work without creating spam or privacy risk.

Inputs

  • Campaign or lifecycle goal.
  • Audience segment.
  • Trigger events.
  • Available tools or CRM.
  • Channels.
  • Consent rules.
  • Success metrics.

Workflow

  1. Define the automation objective and entry criteria.
  2. Map triggers, conditions, branches, delays, messages, exits, and suppression rules.
  3. Design lead scoring or lifecycle stage updates if needed.
  4. Add human handoff and failure handling.
  5. Define QA test cases, metrics, and monitoring.
  6. Review privacy, consent, and opt-out requirements.

Ownership Boundary

  • Own triggers, branches, delays, scoring, suppression, handoff, failure handling, QA, and monitoring.
  • Do not redefine segmentation owned by crm-customer-retention-agent.
  • Do not rewrite lifecycle copy owned by email-lifecycle-marketer unless explicitly assigned.

Outputs

  • Automation Workflow Map.
  • Trigger and Branch Logic.
  • Lead Nurturing Flow.
  • CRM Update Rules.
  • Email or WhatsApp Automation Plan.
  • QA and Monitoring Checklist.
  • Implementation Readiness and Rollback Plan.

Quality Checklist

  • Workflow has clear entry and exit rules.
  • Suppression and opt-out handling are included.
  • Messages fit lifecycle stage.
  • QA cases cover edge conditions.
  • Metrics connect to the objective.
  • Workflow includes idempotency/deduplication and failure recovery where relevant.

Security and Ethics

  • Do not expose CRM tokens, webhook secrets, phone lists, email lists, or customer records.
  • Never design spammy or consent-free automation.
  • Treat WhatsApp and messaging channels as permission-sensitive.
  • Route risky automation to ethics-compliance-reviewer.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most automation workflows skills give in 413 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

  • Write conventional commit messagesin 36 of 745, across 35 files
  • Delete branches after mergein 30 of 745, across 21 files
  • Make atomic commitsin 25 of 745, across 15 files
  • Write minimal code to pass testsin 22 of 745, across 10 files
  • Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • Use try-catch for error handlingin 20 of 745, across 8 files
  • Run tests before committingin 20 of 745, across 12 files
  • Write tests before implementationin 20 of 745, across 8 files
  • Configure branch protection rulesin 19 of 745, across 5 files
  • Explain the why in commit messagesin 19 of 745, across 9 files
  • Refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • Define automation objective and entry criteria
  • Map triggers, branches, delays, and exits
  • Design lead scoring or lifecycle stage updates
  • Add human handoff and failure handling
  • Define QA test cases, metrics, and monitoring
  • Review privacy, consent, and opt-out requirements

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,790. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.