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 when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- marketing-campaign
- metadata
- { "origin": "ECC" }
- 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.
03 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
04 同仓库更多 Skills
higgsfield-websites
Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1/R2/KV/DO/Containers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references/website-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references/app-flow.md), `game` (realtime multiplayer rooms — references/game-flow.md). Routes to the right flow; each carries its own rules and deploy/publish gates. Use when: "build me a website", "make a landing page", "create a web app", "build a SaaS dashboard / portfolio", "make me a game", "deploy this site", "publish". Also owns GAME ART: "make a spritesheet", "tileable texture", "animate a 3D character", game music/SFX — see the game-* references. NOT for: single image/video/audio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback