Repurposing is useful when the idea survives the move between channels. It fails when one generic draft is shortened five times and presented as a content system.

Strawberry can work beside the approved brief, source material, product, customer evidence, brand examples, and live channel context. Your companion can preserve the proof behind the words, learn from edits, and adapt the structure and call to action without losing the accepted voice.

Start with the content job

Clarify the audience, outcome, source of truth, message, proof, format, channel, CTA, deadline, review point, and any brand or legal constraint. Use an accepted brief when one exists; resolve only the gaps that could materially change the work.

Want to try it?

Ask your Strawberry companion: “Create this marketing asset from our approved brief and evidence, then adapt it into useful variants for the channels we actually need.”

Skill

Create and repurpose marketing content

Create the anchor asset from an approved brief and evidence, then adapt it for the channels that matter.

Build the anchor from evidence

Use approved facts, quotes, examples, research, product details, and claims. Keep the source close enough to inspect and flag anything unsupported, stale, contradictory, or pending approval.

The draft should preserveWhat to avoid
The audience's real problem and languageA generic pain point that could describe any buyer
Specific proof and useful detailUnsupported superlatives or invented precision
The brand's rhythm and point of viewA style checklist pasted onto generic copy
One clear next actionCompeting calls to action added for completeness

Review the anchor asset before producing a large family of variants. Coach the angle, depth, proof, voice, and CTA while changes are still cheap.

Adapt the idea, not just the length

ChannelWhat should change
ArticleDepth, evidence, structure, examples, and a reason to keep reading.
EmailRelationship context, one useful promise, scannable proof, and a clear response or next step.
SocialA sharp idea, native pacing, credible specificity, and a format that fits the conversation.
Landing pageMessage hierarchy, objections, proof, CTA sequence, and continuity with the source campaign.

A variant should earn its format. Keep the central claim and evidence consistent while changing the entry point, structure, depth, proof, and CTA for the channel.

Review the work in context

Use the browser to inspect the draft beside the page, campaign, prior content, or channel where it will live. Check factual accuracy, brand fit, audience value, duplication, accessibility, links, and whether each version still makes sense on its own.

Preserve the edits that represent durable brand or audience judgment. Do not save one-off campaign language as a universal voice rule.

Keep production and publishing separate

Writing approval does not approve substantial visual production, CMS changes, scheduling, publishing, sending, audience uploads, or campaign launch. Follow the active permission for each account, destination, action, and condition, and verify completed external work.

Official Strawberry skill
Copy skill file Download skill file

Create and Repurpose Marketing Content

Produce useful, on-brand words from approved evidence, then adapt the idea to each channel without flattening every format into the same copy.

1. Understand the content job

Clarify the audience, desired outcome, source of truth, format and channel, message, proof, CTA, deadline, review point, and any legal or brand constraints. Use an accepted campaign or content brief when one exists.

Inspect approved brand examples, prior high-quality work, product material, research, customer evidence, and source assets. If the central claim or audience is still unclear, do the smallest useful research or route to strawberry/marketing/research-an-audience before drafting. Do not invent customer proof, product behavior, results, quotations, or first-person experience.

2. Establish the anchor

Identify the one useful promise, idea, argument, story, or demonstration the content should carry. Match the evidence to the claim and note any limitations a reviewer must see.

When the team wants many assets or the voice is uncertain, draft one representative piece or a small, varied set first. Let the reviewer correct the angle, voice, proof, structure, and CTA before expanding production.

3. Create the content

Write the agreed anchor asset in the format that best serves the job. It may be an article, email, social post, landing-page copy, product announcement, customer story, script, or another text-led asset.

Keep the voice natural and specific. Use the vocabulary the audience and brand actually use. Build the case from evidence, make uncertainty visible when it matters, and keep calls to action honest about what happens next.

4. Repurpose with intent

Create only the variants that have a real channel role. Preserve the central idea and source truth, but adapt the hook, structure, depth, proof, CTA, and pacing to the audience's behavior in that format. A social post is not merely a shortened article, and an email is not a landing page with a subject line.

Label each variant by channel, audience, purpose, and relationship to the source asset. Identify any visual, design, localization, compliance, or technical dependency rather than pretending the text finishes that work.

5. Validate and hand off

Check factual accuracy, source support, product claims, brand voice, audience fit, channel conventions, links, names, dates, CTA, variant differentiation, and consistency across the set. Remove unsupported superlatives, generic filler, and accidental contradictions.

Deliver the source map, anchor asset, requested variants, review notes, and unresolved dependencies. Substantial visual production, asset generation, publishing, scheduling, sending, and live CMS changes remain separate work.

Follow Strawberry's active scoped permission for every account, destination, and action. Draft or ask when permission is insufficient. Stop when identity, scope, impact, or sensitive-data handling changes. Verify completed external actions.

After acceptance, preserve the useful voice examples, source hierarchy, variant rules, review points, and destination constraints. Do not treat one successful asset as permission to publish future content automatically.