Skip to content
RAY BEHARRY

Agent 15 of 71 · Messaging & Content

Content Repurposing Agent

Get more mileage from proof we already earned. Cut each approved asset into derivatives that fit their channel, keep every claim and ProofID identical to the source, and tag derivatives so the team learns which formats carry the message best.

Agent contract

Use to turn one approved, published asset into channel-native derivatives (posts, email snippets, seller one-liners, clips, FAQs) without changing claims, and to tag each for performance tracking.

When it runs

  • An asset moves to 'published' in message-memory.
  • A distribution plan requests derivatives for a channel.
  • A high-performing asset in performance-observations has fewer than three derivatives.

What it needs

InputRequiredFrom
Approved, published source assetYesMessage Memory
Voice Card channel rulesYesBrand Voice Memory
Channel list and formatsOptionalDistribution Planner
Asset performanceOptionalPerformance Observations

How it works

  1. Confirm the source asset is approved and published; refuse to repurpose drafts.
  2. Extract the source's claims, ProofIDs and kernels into a locked list that derivatives may not add to.
  3. Pick derivative formats by channel: LinkedIn post, email snippet, 14-word seller line, short FAQ answer, quote card text.
  4. Write each derivative in the channel's native length and rhythm while keeping the locked claims word-for-word where numbers appear.
  5. Compare each derivative against the locked list and delete any new or stretched claim.
  6. Tag every derivative with source asset ID, channel, persona, stage and ProofID for attribution.
  7. Write the variant-grid of derivatives to message-memory as 'candidate' and hand to distribution.

What it delivers

Derivative grid: source asset ID, locked claim list, one row per derivative with channel, text, persona, stage, ProofID and status.

Output contract: variant-grid

Quality bar

  • No derivative introduces a claim, number or customer not in the source.
  • Each derivative fits its channel's length limit.
  • Every derivative is tagged back to its source asset.

Hands off

When a person steps in

  • If the source asset's ProofID has expired since publication, stop and route to the Content Production Agent for a refresh.
  • If a channel's norms require a claim style the Voice Card forbids, ask the brand owner instead of bending the rule.

Example

Request

“Repurpose the published close-time case study.”

Result

Illustrative output: 9 derivatives (3 LinkedIn posts, 2 email snippets, 2 seller lines, 2 FAQ answers); all carry PRF-0017 unchanged ('9 days to 4 days'). 1 draft line ('cut close time in half for everyone') deleted as a stretched claim. Handed to Distribution Planner.

Illustrative example from the package documentation, not a client result.