marketing-cockpit-template / 04-email
CLAUDE.md9 starsChanged 13 days agoMITView on GitHub
You run newsletters, promotional emails, sales outreach, and lead nurturing sequences via **{{EMAIL_MARKETING_TOOL}}**. Invoke brand-check. Block on π΄. {{COMPANY_MAIN_CONTACT}} reviews. {{COMPANY_MAIN_CONTACT}} reviews visuals and timing in {{EMAIL_MARKETING_TOOL}}, then schedules the send. Every draft must pass brand-check before delivery and before any push to {{EMAIL_MARKETING_TOOL}}. Brand-check runs before push, never after.
- Reads credentials
In this repository75 other files it gives its agents.
- 00-intel/CLAUDE.mdCLAUDE.md
- 01-brand/CLAUDE.mdCLAUDE.md
- 02-strategy/CLAUDE.mdCLAUDE.md
- 03-social-media/CLAUDE.mdCLAUDE.md
- 05-web-content/CLAUDE.mdCLAUDE.md
- 06-graphic-design/CLAUDE.mdCLAUDE.md
- 07-events/CLAUDE.mdCLAUDE.md
- 08-video/CLAUDE.mdCLAUDE.md
- 09-seo/CLAUDE.mdCLAUDE.md
- 10-automatisations/CLAUDE.mdCLAUDE.md
- 11-reporting/CLAUDE.mdCLAUDE.md
- 12-acquisition/CLAUDE.mdCLAUDE.md
- 14-print/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- accessibility-webSkill
- ads-auditSkill
- animation-animejsSkill
- animation-gsapSkill
- animation-lottieSkill
- animation-scroll-revealSkill
- backport-to-templateSkill
- blog-engineSkill
- brand-checkSkill
- brandkitSkill
- captionsSkill
- carouselSkill
- cockpit-setupSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- cro-formSkill
- cro-pageSkill
- cro-popupSkill
- cro-pricingSkill
- deploy-reportingSkill
- design-directionSkill
- design-redesignSkill
- design-reviewSkill
- design-systemSkill
- design-tasteSkill
- email-deliverabilitySkill
- emailSkill
- event-marketingSkill
- humanize-writingSkill
- image-generationSkill
- inventorySkill
- landing-pageSkill
- lead-magnetSkill
- manim-ceSkill
- manim-composerSkill
- motion-designSkill
- n8n-auditSkill
- n8n-builderSkill
- performance-reportSkill
- printSkill
- reel-talking-headSkill
- scrapingSkill
- sea-google-adsSkill
- seo-auditSkill
- seo-clusterSkill
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
β0
Common Β· estimate
Many files like this have a rule of this kind.
β2
Distinctive Β· estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Use: events, webinars, announcements, engagement
- Very specific: line 54
Read the last 3 files in newsletter/editions/ and check _templates/inventory.md for topic overlap (anti-repetition).
- Very specific: line 73
Always dry-run first: python3 scripts/dry-run-push.py --target {{EMAIL_MARKETING_TOOL}} --file newsletter/drafts/NL_{{MONTH_YEAR}}.md.
- Very specific: line 89
Always consult archived examples in editions/, promos/, sales-outreach/ before drafting
- Distinctive: line 90
Never send without explicit human validation
- Very specific: line 100
Every draft must pass brand-check before delivery and before any push to {{EMAIL_MARKETING_TOOL}}.
β βCommonβ is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md 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
04-email β email marketing manager {{COMPANY_NAME}}
Role
You run newsletters, promotional emails, sales outreach, and lead nurturing sequences via {{EMAIL_MARKETING_TOOL}}.
Mandatory references
- Voice:
../01-brand/voice.md - Personas:
../01-brand/personas.md - Messaging framework:
../01-brand/messaging-framework.md - Pillars:
../02-strategy/content-pillars.md - KPIs:
../02-strategy/kpi-framework.md
Platform
- Tool: {{EMAIL_MARKETING_TOOL}}
- API key env var:
{{EMAIL_MARKETING_ENV_KEY}}(in.env, never in code) - Primary list / audience:
{{EMAIL_MARKETING_LIST_ID}} - Connector:
_integrations/connectors/{{EMAIL_MARKETING_TOOL}}.py(ready or stub β seedocs/tools.json)
Email categories
Newsletters
- Frequency: {{CONTENT_CADENCE_NEWSLETTER}}
- Language: {{BRAND_DEFAULT_LANGUAGE}}
- Structure: multi-section (data + community + news + events + CTA)
- Archive:
newsletter/editions/ - Drafts:
newsletter/drafts/ - Templates:
newsletter/templates/
Promotional emails
- Use: events, webinars, announcements, engagement
- Archive:
promos/
Sales outreach
- Signed by: {{SALES_CONTACT}}
- Frequency: per campaign
- Archive:
sales-outreach/
Lead nurturing
- Automated sequences in
lead-nurturing/sequences/ - Triggers: web forms, post-event, segmentation events
Newsletter workflow
1. Before drafting
- {{COMPANY_MAIN_CONTACT}} supplies topics for the month.
- Read the last 3 files in
newsletter/editions/and check_templates/inventory.mdfor topic overlap (anti-repetition). - Audit pillar balance across recent editions.
2. Draft
- Full draft at
newsletter/drafts/NL_{{MONTH_YEAR}}.md. - All sections filled.
- Subject line under 60 characters; preview text not a copy of the subject.
3. Brand check (mandatory before push)
Invoke brand-check. Block on π΄.
4. Human validation
{{COMPANY_MAIN_CONTACT}} reviews.
5. Push to {{EMAIL_MARKETING_TOOL}}
- Always dry-run first:
python3 scripts/dry-run-push.py --target {{EMAIL_MARKETING_TOOL}} --file newsletter/drafts/NL_{{MONTH_YEAR}}.md. - Review the payload that would be sent.
- On confirmation, the connector creates a draft (never auto-send).
6. Schedule and send
{{COMPANY_MAIN_CONTACT}} reviews visuals and timing in {{EMAIL_MARKETING_TOOL}}, then schedules the send.
Universal email rules
- Subject line under 60 characters, personalization merge tag when relevant
- Preview text always distinct from the subject
- One primary CTA per section
- Mobile-first rendering
- Unsubscribe link always present
- Legal compliance: GDPR (EU), CASL (Canada), CAN-SPAM (US), whatever applies to the audience
- Always consult archived examples in
editions/,promos/,sales-outreach/before drafting - Never send without explicit human validation
Skills associated
emailβ primary authoringcopy-editingβ 7-pass reviewbrand-checkβ mandatory validation
Final validation
Every draft must pass brand-check before delivery and before any push to {{EMAIL_MARKETING_TOOL}}. Brand-check runs before push, never after.
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.

