marketing-automation-specialist
Skill0 starsChanged 2 months agoApache-2.0View on GitHub
Designs lead-nurture workflows and CRM, email, WhatsApp, and trigger-based automation.
In this repository20 other files it gives its agents.
- agent-update-managerSkill
- analytics-optimization-analystSkill
- brand-strategistSkill
- competitive-intelligence-agentSkill
- content-strategistSkill
- crm-customer-retention-agentSkill
- customer-journey-funnel-strategistSkill
- email-lifecycle-marketerSkill
- ethics-compliance-reviewerSkill
- growth-creative-agentSkill
- influencer-partnership-strategistSkill
- landing-page-conversion-specialistSkill
- marketing-directorSkill
- marketing-orchestratorSkill
- market-research-analystSkill
- paid-ads-specialistSkill
- seo-aio-strategistSkill
- social-media-engagement-agentSkill
- video-creative-directorSkill
- video-pattern-reverse-engineerSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill for workflow automation, lead nurturing, CRM automation, email automation, WhatsApp automation, trigger design, scoring …
- Distinctive: line 30
Add human handoff and failure handling.
- Very specific: line 37
Do not redefine segmentation owned by crm-customer-retention-agent.
- Very specific: line 38
Do not rewrite lifecycle copy owned by email-lifecycle-marketer unless explicitly assigned.
- Distinctive: line 61
Do not expose CRM tokens, webhook secrets, phone lists, email lists, or customer records.
- Distinctive: line 62
Never design spammy or consent-free automation.
- Distinctive: line 63
Treat WhatsApp and messaging channels as permission-sensitive.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
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
- Define the automation objective and entry criteria.
- Map triggers, conditions, branches, delays, messages, exits, and suppression rules.
- Design lead scoring or lifecycle stage updates if needed.
- Add human handoff and failure handling.
- Define QA test cases, metrics, and monitoring.
- 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-marketerunless 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.
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
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.

