Cross-channel message adaptor · free AI skill

Takes one core product message and adapts it into four channel-native assets simultaneously — in-product UI copy, an announcement email, a help center article, and a sales one-pager — each calibrated to its channel's…

Purpose

Convert a single core message into four ready-to-ship, channel-native assets in one pass — so a feature launch or product change reads consistently everywhere while respecting each channel's word budget, reader intent, and voice. Eliminates the drift and duplicated effort of hand-adapting the same message four times.

When to Use

Invoke this skill when the user asks to:

Launch a new feature and needs UI copy, email, docs, and sales collateral at once
Announce a product change across multiple channels consistently
Repurpose one core message for in-product, email, help center, and sales use
Turn a launch brief or release note into ready-to-publish assets
Fix messaging drift where the same feature is described differently across surfaces
Prep a coordinated cross-functional rollout (product + marketing + support + sales)

Inputs Required

Before starting, collect:

Core message: The single sentence or short paragraph the assets must all carry
Feature/change context: What it is, what it does, what problem it solves
Primary audience: Who uses the product (role, sophistication level)
Key benefit + proof point: The main outcome and any metric, quote, or evidence supporting it
Brand voice: 2-4 adjectives (e.g., plainspoken, confident, warm) or a reference example
Call to action: What each channel should drive the reader to do
Constraints: Any character limits, banned phrases, or required legal/compliance language

If brand voice or CTA is missing, default to a clear, benefit-forward voice and a "try it now / learn more" CTA, and note the assumption.

Instructions

Step 1: Extract the Message Core

Before adapting, distill the input into three reusable atoms that every channel reuses:

The claim (one sentence): what's now true that wasn't before
The benefit (one sentence): what the reader gets, in their terms — not the feature's terms
The proof (one phrase): the metric, quote, or concrete detail that makes it credible

State these three atoms explicitly at the top. Every asset below must trace back to them — this is what prevents drift.

Step 2: Adapt for In-Product UI

Reader intent: mid-task, low patience, scanning. Reward: instant clarity. Produce:

Headline (max 6 words): the benefit, not the feature name
Body (max 25 words): what it does + why it matters, one CTA verb
Button/CTA label (1-3 words): action-oriented ("Turn on," "Try it," "See how")
Optional tooltip (max 12 words): for the empty state or first-use hint Rules: no jargon, no marketing adjectives, second person, active voice. If it doesn't fit on a card or modal, it's too long.

Step 3: Adapt for Announcement Email

Reader intent: inbox skimming, deciding whether to care. Reward: a reason to click. Produce:

Subject line (max 50 characters) + preview text (max 90 characters)
Opening (1-2 sentences): lead with the change and why it matters now — no "We're excited to announce"
Body (80-120 words): the benefit, one proof point, what it looks like in practice
Primary CTA button (2-4 words) + a one-line "what to do next" Rules: one idea per email, one primary CTA, conversational but not chatty. The subject line must earn the open on benefit, not novelty.

Step 4: Adapt for Help Center Article

Reader intent: has a task or problem, wants to complete it. Reward: an unambiguous answer. Produce:

Title (task-phrased, e.g., "How to [do the thing]")
One-sentence summary: what this article helps the reader accomplish
Prerequisites (if any): access, plan, or setup needed
Numbered steps (3-7 steps): each step one action, imperative voice
Result confirmation: how the reader knows it worked
Troubleshooting (2-3 items): the likeliest snags and fixes Rules: neutral and instructional tone, no persuasion, no benefit language — the reader is already convinced.

Step 5: Adapt for Sales One-Pager

Reader intent: evaluating, needs ammunition to sell internally. Reward: a crisp value case. Produce:

Positioning headline (max 10 words): the outcome a buyer cares about
The problem (2 sentences): the cost of the status quo
The solution (2 sentences): what the feature does, in buyer terms
3 value bullets: each pairing a capability with a business outcome
Proof point block: the metric/quote from the message core, framed for credibility
Objection handler (1-2): the most likely pushback + a one-line response
CTA line: the next step in the sales motion (demo, trial, pilot) Rules: buyer-outcome language (revenue, time, risk, cost), confident and specific, no product-team internal terms.

Step 6: Consistency Pass

Re-read all four assets against the Step 1 atoms. Confirm the claim, benefit, and proof are consistent across every channel — wording adapts, meaning does not. Flag any place where a channel accidentally overstates or contradicts another.

Output Format

Structure: Message core at top, then four clearly headed asset blocks, then a short consistency note
Length: 700-1,000 words total across all four assets
Format: Structured document — labeled sections and copy-ready fields (not prose about the copy; the actual copy)
Sections: Message Core (3 atoms) → In-Product UI → Announcement Email → Help Center Article → Sales One-Pager → Consistency Pass
Tone: Each asset carries its own channel-native tone per the rules above; the brand voice adjectives thread through UI, email, and one-pager (the help article stays neutral)

Quality Checklist

Before delivering output, verify:

[ ] The three message atoms (claim, benefit, proof) are stated explicitly and reused in every asset
[ ] UI headline is 6 words or fewer and UI body is 25 words or fewer
[ ] Email subject line is under 50 characters and drives on benefit, not novelty
[ ] Help article uses imperative, benefit-free instructional voice and has 3-7 numbered steps
[ ] Sales one-pager has 3 value bullets, each pairing a capability with a business outcome
[ ] Consistency pass confirms no channel contradicts or overstates relative to the others
[ ] No bracket placeholders remain — every field is filled with real copy for this feature

Notes

The most common failure is letting the marketing voice leak into the help center article — resist it; a reader mid-task wants steps, not selling.
If the core message is a bundle of ideas, split it: adapt one idea cleanly rather than four muddy assets. Ask the user to pick the single most important claim.
UI copy is the hardest constraint — draft it first. If the benefit can't survive a 25-word body, the message core isn't sharp enough yet.
For regulated products, surface any required legal language in the constraints intake and place it verbatim in the email and one-pager rather than paraphrasing.

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
<your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

Drag this file into a new chat, or copy and paste its contents
Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills