accessibility
Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when…
End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel
$ npx -y skills add affaan-m/ECC --skill marketing-campaign --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/marketing-campaignContext preview
The summary Claude sees to decide when to auto-load this skill.
End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel
name: marketing-campaign description: End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy. metadata: origin: ECC
Plan and execute launch campaigns that convert — not just campaigns that ship.
1. Define positioning before writing any copy. All copy flows from the angle. 2. Research the audience before assuming you know their language or fears. 3. Each deliverable must serve one clear purpose in the campaign arc. 4. Specificity beats adjectives in every format and on every channel. 5. The same voice must run across every channel and every piece. 6. No copy ships without passing the quality gate.
Use `market-research` to:
Deliverable: a short research brief (audience profile + competitive summary + key insights).
Produce:
Do not write any copy until positioning and angle are approved.
Produce in this order — each layer informs the next:
1. **Landing page copy** (all sections: hero, problem, solution, features, how it works, proof, CTA) 2. **Email sequence** (each email has one purpose; follow the arc: problem → education → agitation → solution → proof → urgency → final CTA) 3. **Social posts** (platform-native via `content-engine`; LinkedIn and X are different formats, not the same copy resized) 4. **Short-form video scripts** (timestamp-blocked; written for screen and ear, not the page) 5. **Ad copy variants** (3–4 variants testing different angles or audience segments) 6. **Content calendar** (day-by-day schedule with channel, type, timing, and dependencies)
Gate every deliverable:
A full campaign delivers:
1. **Positioning brief** — angle, core benefit statement, tone profile 2. **Landing page copy** — hero, problem, solution, features, how it works, proof, CTA 3. **Email sequence** — subject + preview + body + CTA for each email, labelled by day and purpose 4. **LinkedIn posts** — 3+ platform-native posts with distinct angles 5. **X posts** — 5+ standalone posts + 1 thread 6. **Short-form video scripts** — 2+ timestamp-blocked scripts with visual direction notes 7. **Ad copy variants** — short headline / long headline / body per variant 8. **Content calendar** — day-by-day schedule with channel, content type, timing, and dependencies 9. **Copy review summary** — flagged issues and open questions before anything goes live
Before delivering any piece:
Delete and rewrite any:
Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills
Repo: affaan-m/ECC
Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when…
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures,…
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when…
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent's…
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails…
Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer…