Create evidence-based campaign briefs, channel-specific marketing copy, content calendars and reusable launch assets with measurement and editorial checks.
Scanned 10/6/2026
npx -y skills add Nmor/the-council --skill content-campaigns --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Content Campaigns?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nmor-content-campaigns)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: content-campaigns
description: Create evidence-based campaign briefs, channel-specific marketing copy, content calendars and reusable launch assets with measurement and editorial checks.
---
# Content and campaigns
> Size budget: 6 KB. Use when campaign content or execution planning is requested.
## Start with one brief
Identify the offer, audience, customer problem, desired action, channels, timing,
budget, tone, brand constraints and available proof. Reuse the strategy and approved
claims. Mark assumptions and ask only for constraints that materially affect delivery.
Use [marketing-strategy](../marketing-strategy/SKILL.md) if positioning is unresolved;
use [seo](../seo/SKILL.md) for search-focused content and
[brand-creative-direction](../brand-creative-direction/SKILL.md) for visual assets.
## Draft for the channel
Build a message hierarchy: audience problem, proposition, credible proof, objection
and next action. Adapt length, hook, formatting and CTA to each requested channel;
do not repeat identical copy everywhere. Keep destination and promise consistent.
A campaign can include a landing page, email sequence, social variants, paid ad copy
or video script, but produce only assets that serve the brief.
For requested launch video use [BRAG](../brag/SKILL.md), carrying over the same claims.
Keep a claim ledger linking each factual statement, price, statistic, testimonial or
performance claim to evidence. Use clearly labeled placeholders when evidence is
missing; do not fill gaps with fake customers, logos or urgency. Confirm asset licenses,
attribution and permission to show product/customer material. Avoid exposing private
information. Apply accessibility to structure, links, alt text, captions and contrast.
## Make execution reviewable
Provide a calendar with actual dates/time zone when specified, deliverable, channel,
owner, dependencies, status and acceptance check. Distinguish drafts, approvals and
published assets. Plan repurposing from a verified source asset and preserve its meaning.
Specify a test hypothesis, primary conversion metric, baseline or unknown, experiment
window and stopping/review rule. Use consistent campaign/UTM naming where measurement
is available; never put personal or sensitive data into URLs. Define conversion events
and deduplication with the project's analytics conventions.
## Review and deliver
Check spelling, link targets, offer consistency, claim support, readability, channel
limits and dates. Confirm the CTA reaches the promised action. Include the draft assets,
calendar and unresolved inputs only to the depth the user requested. If assets were
rendered, inspect them; do not report visual/audio review from source text alone.
Creating copy does not authorize posting, emailing, uploading or ad spend. Follow
existing authorization without inventing another approval process.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!