Agent SkillsNeverSight/learn-skills.dev › marketing-campaign

marketing-campaign

GitHub

端到端营销活动策划与执行技能,涵盖受众研究、定位、落地页文案、邮件序列、社媒帖子及广告脚本。作为多渠道产品发布的编排层,确保从策略到内容生产的全流程一致性与高转化率。

data/skills-md/affaan-m/everything-claude-code/marketing-campaign/SKILL.md NeverSight/learn-skills.dev

Trigger Scenarios

规划产品或功能发布 基于单一产品简介构建完整内容套件 在撰写任何文案前定义定位和营销角度 跨渠道协调多种内容类型 审查文案的转化质量和品牌一致性

Install

npx skills add NeverSight/learn-skills.dev --skill marketing-campaign -g -y
More Options

Non-standard path

npx skills add https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/affaan-m/everything-claude-code/marketing-campaign -g -y

Use without installing

npx skills use NeverSight/learn-skills.dev@marketing-campaign

指定 Agent (Claude Code)

npx skills add NeverSight/learn-skills.dev --skill marketing-campaign -a claude-code -g -y

安装 repo 全部 skill

npx skills add NeverSight/learn-skills.dev --all -g -y

预览 repo 内 skill

npx skills add NeverSight/learn-skills.dev --list

SKILL.md

Frontmatter
{
    "name": "marketing-campaign",
    "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."
}

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

  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.

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-voice for 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:

  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)

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:

  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

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 production
  • crosspost — multi-platform distribution
  • market-research — audience and competitive intelligence
  • seo — on-page optimisation for landing page copy

Version History

  • e0220ca Current 2026-07-05 23:58

Same Skill Collection

data/skills-md/00prabalk00/claude-skills/knowledge-base-gap-finder/SKILL.md
data/skills-md/01000001-01001110/agent-jira-skills/jira-agile/SKILL.md
data/skills-md/01000001-01001110/agent-jira-skills/jira-auth/SKILL.md
data/skills-md/01000001-01001110/agent-jira-skills/jira-issues/SKILL.md
data/skills-md/01000001-01001110/agent-jira-skills/jira-project-management/SKILL.md
data/skills-md/01000001-01001110/agent-jira-skills/jira-projects/SKILL.md
data/skills-md/01000001-01001110/agent-jira-skills/jira-safe/SKILL.md
data/skills-md/01000001-01001110/agent-jira-skills/jira-search/SKILL.md
data/skills-md/01000001-01001110/agent-jira-skills/jira-spaces/SKILL.md
data/skills-md/01000001-01001110/agent-jira-skills/jira-transitions/SKILL.md
data/skills-md/0731coderlee-sudo/wechat-publisher/wechat-publisher/SKILL.md
data/skills-md/0froq/skills/conventionalcommits/SKILL.md
data/skills-md/0froq/skills/nuxt/SKILL.md
data/skills-md/0froq/skills/oq/SKILL.md
data/skills-md/0froq/skills/pinia/SKILL.md
data/skills-md/0froq/skills/pnpm/SKILL.md
data/skills-md/0froq/skills/slidev/SKILL.md
data/skills-md/0froq/skills/tsdown/SKILL.md
data/skills-md/0froq/skills/turborepo/SKILL.md
data/skills-md/0froq/skills/unocss/SKILL.md
data/skills-md/0froq/skills/vitepress/SKILL.md
data/skills-md/0froq/skills/vitest/SKILL.md
data/skills-md/0froq/skills/vue-best-practices/SKILL.md
data/skills-md/0froq/skills/vue-router-best-practices/SKILL.md
data/skills-md/0froq/skills/vue-testing-best-practices/SKILL.md
data/skills-md/0froq/skills/vue/SKILL.md
data/skills-md/0froq/skills/vueuse-functions/SKILL.md
data/skills-md/0froq/skills/web-design-guidelines/SKILL.md
data/skills-md/0juano/agent-skills/bondterminal-x402/SKILL.md
data/skills-md/0juano/agent-skills/edgeone-pages-deploy/SKILL.md
data/skills-md/0juano/agent-skills/ley-ar/SKILL.md
data/skills-md/0juano/agent-skills/ticktick/SKILL.md
data/skills-md/0juano/agent-skills/x-image-cards/SKILL.md
data/skills-md/0juano/x-image-cards/x-image-cards/SKILL.md
data/skills-md/0x0funky/agent-sprite-forge/generate2dsprite/SKILL.md
data/skills-md/0x0funky/agent-sprite-forge/video2dsprite/SKILL.md
data/skills-md/0x2e/superpowers/brainstorming/SKILL.md
data/skills-md/0x2e/superpowers/dispatching-parallel-agents/SKILL.md
data/skills-md/0x2e/superpowers/executing-plans/SKILL.md
data/skills-md/0x2e/superpowers/finishing-a-development-branch/SKILL.md
data/skills-md/0x2e/superpowers/receiving-code-review/SKILL.md
data/skills-md/0x2e/superpowers/requesting-code-review/SKILL.md
data/skills-md/0x2e/superpowers/subagent-driven-development/SKILL.md
data/skills-md/0x2e/superpowers/systematic-debugging/SKILL.md
data/skills-md/0x2e/superpowers/test-driven-development/SKILL.md
data/skills-md/0x2e/superpowers/using-git-worktrees/SKILL.md
data/skills-md/0x2e/superpowers/using-superpowers/SKILL.md
data/skills-md/0x2e/superpowers/verification-before-completion/SKILL.md
data/skills-md/0x2e/superpowers/writing-plans/SKILL.md
data/skills-md/0x2e/superpowers/writing-skills/SKILL.md

Metadata

Files
0
Version
e0220ca
Hash
92168e34
Indexed
2026-07-05 23:58

Accueil - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-09 00:43
浙ICP备14020137号-1 $Carte des visiteurs$