affaan-m/ecc

marketing-campaign

End-to-end marketing campaign planning and execution.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/affaan-m/ecc --skill marketing-campaign

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
affaan-m
커뮤니티

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

설치 수
4
GitHub Stars
28.6만
업데이트
10월 20일
affaan-m
커뮤니티

autonomous-loops

Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems. Retained for compatibility only: when new autonomous loop guidance is needed, use continuous-agent-loop instead.

설치 수
4
GitHub Stars
28.6만
업데이트
10월 20일
affaan-m
커뮤니티

coding-standards

Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.

설치 수
4
GitHub Stars
28.6만
업데이트
10월 20일
affaan-m
커뮤니티

configure-ecc

Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under ./.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes.

설치 수
4
GitHub Stars
28.6만
업데이트
10월 20일