Repurpose one source idea across channels without drifting claims
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 agent.
Methods
Turn one idea into several B2B content pieces
Steps
- Start from a single idea backed by something dated you can show, such as notes from a call, your own numbers or a past post.
- Record what the buyer is asking, phrased as they would say it, plus what your source cannot back up.
- Draft the main long article first, since every other piece will be cut from it.
- Keep a claims list: each claim, where it comes from, its limits and which pieces may use it.
- Give each piece one job for its reader, and skip pieces that would just repeat another.
- Name one reviewer who checks every piece against the claims list before scheduling.
- Close each piece with a single next step, and see anyone who reacts as someone to qualify, not a buyer.
- Note: Our own-words summary of Oxygen's guide by Tim Scheuer, in its order; the original has a worked example and the Oxygen setup. Oxygen sells a tool for the drafting and scheduling.
Run this method with your agent
Download .mdCopied 0
--- name: "gtm-content-waterfall-oxygen-method" description: "Use when you need to Repurpose one source idea across channels without drifting claims. Turn one idea into several B2B content pieces" --- # Turn one idea into several B2B content pieces Job: [Repurpose one source idea across channels without drifting claims](https://aiagents.org/canai/gtm-content-waterfall-oxygen) ## Need - AI agent ## Steps 1. Start from a single idea backed by something dated you can show, such as notes from a call, your own numbers or a past post. 2. Record what the buyer is asking, phrased as they would say it, plus what your source cannot back up. 3. Draft the main long article first, since every other piece will be cut from it. 4. Keep a claims list: each claim, where it comes from, its limits and which pieces may use it. 5. Give each piece one job for its reader, and skip pieces that would just repeat another. 6. Name one reviewer who checks every piece against the claims list before scheduling. 7. Close each piece with a single next step, and see anyone who reacts as someone to qualify, not a buyer. 8. Note: Our own-words summary of Oxygen's guide by Tim Scheuer, in its order; the original has a worked example and the Oxygen setup. Oxygen sells a tool for the drafting and scheduling. ## Credit Method author Oxygen (guide by Tim Scheuer) Source: https://oxygen-agent.com/guides/gtm-content-waterfall
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/gtm-content-waterfall-oxygen - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "gtm-content-waterfall-oxygen",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}