marketing-campaign
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 w
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 9299bb0a41877cab… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Marketing Campaign
Plan and execute launch campaigns that convert — not just campaigns that ship.
When to Activate
- planning a product or feature launch
- building a full content suite from a single product brief
- defining positioning and campaign angle before writing any copy
- orchestrating multiple content types across channels
- reviewing copy for conversion quality and brand consistency
Non-Negotiables
- Define positioning before writing any copy. All copy flows from the angle.
- Research the audience before assuming you know their language or fears.
- Each deliverable must serve one clear purpose in the campaign arc.
- Specificity beats adjectives in every format and on every channel.
- The same voice must run across every channel and every piece.
- No copy ships without passing the quality gate.
Campaign Workflow
Phase 1: Research
Use market-research to:
- profile the target audience (jobs-to-be-done, fears, language, alternatives they use)
- map 3+ direct or adjacent competitors (positioning, gaps, messaging weaknesses)
- identify 1–3 audience insights the campaign angle will exploit
Deliverable: a short research brief (audience profile + competitive summary + key insights).
Phase 2: Positioning
Produce:
- core benefit statement (one sentence, no feature list, no jargon)
- positioning formula: "[Product] helps [audience] [achieve outcome] by [mechanism]"
- campaign angle: the specific tension, insight, or moment the whole campaign lives in
- tone profile: lock before writing (delegate to
brand-voicefor durable, session-reusable voice capture)
Do not write any copy until positioning and angle are approved.
Phase 3: Content Production
Produce in this order — each layer informs the next:
- Landing page copy (all sections: hero, problem, solution, features, how it works, proof, CTA)
- Email sequence (each email has one purpose; follow the arc: problem → education → agitation → solution → proof → urgency → final CTA)
- Social posts (platform-native via
content-engine; LinkedIn and X are different formats, not the same copy resized) - Short-form video scripts (timestamp-blocked; written for screen and ear, not the page)
- Ad copy variants (3–4 variants testing different angles or audience segments)
- Content calendar (day-by-day schedule with channel, type, timing, and dependencies)
Phase 4: Review
Gate every deliverable:
- 5-second test on all hero / above-fold copy (clear who it's for, what it does, why act now)
- CTA audit (one per piece, specific, earned — not demanded)
- Tone consistency check across all channels
- Claim audit (every claim is specific and supportable)
- Cross-channel consistency (ad claims match landing page; email body matches subject)
Output Contract
A full campaign delivers:
- Positioning brief — angle, core benefit statement, tone profile
- Landing page copy — hero, problem, solution, features, how it works, proof, CTA
- Email sequence — subject + preview + body + CTA for each email, labelled by day and purpose
- LinkedIn posts — 3+ platform-native posts with distinct angles
- X posts — 5+ standalone posts + 1 thread
- Short-form video scripts — 2+ timestamp-blocked scripts with visual direction notes
- Ad copy variants — short headline / long headline / body per variant
- Content calendar — day-by-day schedule with channel, content type, timing, and dependencies
- Copy review summary — flagged issues and open questions before anything goes live
Quality Gate
Before delivering any piece:
- every deliverable sounds like the same author
- no hollow superlatives or filler adjectives remain
- every CTA is specific and earned (never "learn more" or "click here")
- no copy is duplicated verbatim across platforms
- hero copy passes the 5-second test
- email subjects match email body (no bait-and-switch)
- ad claims match landing page claims exactly
- no copy would work unchanged for any other product in the category
Hard Bans
Delete and rewrite any:
- "game-changing", "revolutionary", "world-class", "cutting-edge"
- "In today's competitive landscape"
- fake urgency not backed by a real deadline
- hollow social proof without specifics ("thousands trust us")
- generic CTAs ("learn more", "find out more", "click here")
- copy that could be unplugged and dropped into a competitor's campaign unchanged
Related Skills
brand-voice— source-derived voice capture (run before content production)content-engine— platform-native content productioncrosspost— multi-platform distributionmarket-research— audience and competitive intelligenceseo— on-page optimisation for landing page copy
Files
1- SKILL.md
f4d2501b1a5.2 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from affaan-m/everything-claude-code8
Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels, accessibility traits and hints, focus management, contrast, target size, and screen-reader support. Use when building or auditing UI for accessibility compliance, keyboard n
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent ap
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 choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent's tool set, action space, or observation format.
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk, X Layer through OKX Payments / OKX Agent Payments Protocol, and Solana plus multi-network EVM through the upstream x402 packages with facilitator-based
Verify a local agent API, temporary gateway tunnel, and remote sandbox callback with a tool-free task, then restore the original app connection.
Security hardening guidance for AI agent frameworks that process untrusted content, invoke tools, write workspace files, manage runtime identifiers, or handle credentials. Use when building or reviewing an agent runtime, autonomous worker, tool gateway, memory service, or multi-tenant agent deployme
Related methodology skillsscan passed
Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Reviews a branch, pull request or uncommitted change for the interface problems it introduced or regressed, across accessibility, layout, writing, typography, color and UI.
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (S
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).