[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEBAVCNNTK3XJ6B6V2C3F4":3,"skill-same:01M7AEBAVCNNTK3XJ6B6V2C3F4":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7AEBAVCNNTK3XJ6B6V2C3F4","content-amplifier",null,"Use when the user asks to \"amplify influencer content with paid media\", \"set up whitelisting or Spark Ads\", \"decide which posts to boost\", \"repurpose influencer content\", \"turn one video into multiple ads\", or \"build a UGC asset library\"; produces (paid mode) a content-selection scorecard, a paid amplification strategy (whitelisting\u002Fboosting\u002Fdark posts), audience targeting, and a budget+optimization plan, or (repurpose mode) a rights-tracked content inventory, a 1-video-to-10+-asset repurposing map, per-format transformation specs, and a 30-day distribution plan. Not for gating whether a deliverable is publishable or FTC-compliant — use creator-content-auditor; not for the always-on brand posting calendar — use social-calendar-builder; not for drafting a net-new idea into platform-native packages — use social-creative-builder. 复用达人内容 \u002F 内容放量.","iamwaqargulzar\u002FMarketing-Agent-OS","iamwaqargulzar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96654715?v=4","01M7ACMBN0TACNXY53QYG8KDF6","Waqar Gulzar","01M7ACMBNP5ZX60H8CD3JK0633",8,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Factivate\u002Fcontent-amplifier\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: content-amplifier\nslug: content-amplifier\ndisplayName: \"Content Amplifier · 内容放量\"\nsummary: \"把跑赢的创作者内容用付费放大，并将 UGC 复用到付费、网站、邮件与自然渠道\"\ndescription: 'Use when the user asks to \"amplify influencer content with paid media\", \"set up whitelisting or Spark Ads\", \"decide which posts to boost\", \"repurpose influencer content\", \"turn one video into multiple ads\", or \"build a UGC asset library\"; produces (paid mode) a content-selection scorecard, a paid amplification strategy (whitelisting\u002Fboosting\u002Fdark posts), audience targeting, and a budget+optimization plan, or (repurpose mode) a rights-tracked content inventory, a 1-video-to-10+-asset repurposing map, per-format transformation specs, and a 30-day distribution plan. Not for gating whether a deliverable is publishable or FTC-compliant — use creator-content-auditor; not for the always-on brand posting calendar — use social-calendar-builder; not for drafting a net-new idea into platform-native packages — use social-creative-builder. 复用达人内容 \u002F 内容放量.'\nversion: \"20.1.0\"\nlicense: Apache-2.0\ncompatibility: \"Claude Code and compatible agent-skill hosts\"\nhomepage: \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"\nwhen_to_use: \"Use when a brand has a frozen, auditor-approved creator asset with active scoped rights and wants to extract more value from it. Paid mode: extend reach with paid spend — choosing which posts to boost, setting up whitelisted Partnership Ads or TikTok Spark Ads, planning dark posts, allocating an ad budget across creators and platforms, building audience targeting off creator lookalikes, running an optimization and scale\u002Fpause playbook. Repurpose mode: reuse one asset across paid, website, email, and organic social — generating ad variations from organic clips, building a searchable rights-tracked library, populating product pages with social proof, or planning a multi-channel rollout from a small source set.\"\nargument-hint: \"[--mode paid|repurpose] \u003Ccampaign or content set> [budget] [platforms\u002Fchannels]\"\nmetadata: {\"author\": \"aaron-he-zhu\", \"version\": \"20.1.0\", \"discipline\": \"influencer\", \"phase\": \"activate\", \"geo-relevance\": \"low\", \"hermes\": {\"tags\": [\"marketing\", \"influencer\", \"activate\"], \"category\": \"influencer\"}, \"openclaw\": {\"emoji\": \"📣\", \"homepage\": \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"}}\n---\n\n# Content Amplifier\n\nExtract more value from a frozen, approved creator asset. Two modes: **paid** (extend reach with paid spend — whitelisting, Spark Ads, dark posts, budget + optimization) and **repurpose** (reuse one asset across paid, website, email, and social — inventory, repurposing map, format specs, distribution plan). Both start from the exact version cleared by [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) and active scoped rights. Spark\u002Fboost paths additionally require the platform state and live post they depend on; a dark post need not have been published organically.\n\n**Scope guard**: this skill does NOT score a deliverable for brand alignment, message accuracy, or FTC\u002Fdisclosure compliance, and it does NOT compute a STAR Trust\u002FAppeal score or run the `STAR-T1`\u002F`STAR-T2` veto — that is the [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) gate's job. This skill works the downstream lever: turning approved content into paid reach or many-channel assets, then hands off. In a product launch, this skill owns the **repurposing map and the paid-amplification \u002F distribution execution calendar** (including the 30-day plan for launch content); the launch discipline's [momentum-planner](..\u002F..\u002F..\u002Flaunch\u002Fprove\u002Fmomentum-planner\u002FSKILL.md) schedules only the launch *moments* and hands the distribution work here. In always-on organic social the split is the same shape: the standing brand posting calendar belongs to [social-calendar-builder](..\u002F..\u002F..\u002Fsocial\u002Fcraft\u002Fsocial-calendar-builder\u002FSKILL.md) and net-new idea-to-multi-platform package drafting to [social-creative-builder](..\u002F..\u002F..\u002Fsocial\u002Fcraft\u002Fsocial-creative-builder\u002FSKILL.md) — this skill keeps repurposing of existing assets and ALL paid amplification, and the social discipline only flags boost-worthy organic winners to it.\n\n## Mode selector\n\n| Mode | Use when | Core output |\n|------|----------|-------------|\n| **paid** (default) | Extend the reach of organic creator content with paid spend | Content-selection scorecard, amplification strategy (whitelisting \u002F boosting \u002F dark posts), audience targeting, budget allocation, optimization playbook |\n| **repurpose** | Reuse one approved asset across paid, website, email, and social | Rights-tracked inventory, 1-video-to-10+ repurposing map, format transformation specs, 30-day distribution plan, content library + rights tracker |\n\nPick with `--mode paid` or `--mode repurpose`. If unset: \"boost \u002F amplify \u002F whitelisting \u002F Spark Ads \u002F dark post \u002F paid spend \u002F budget\" → **paid**; \"repurpose \u002F reuse \u002F turn one video into many \u002F asset library \u002F social proof on pages \u002F multi-channel rollout\" → **repurpose**. If the request spans both (e.g. \"cut ad variations *and* plan the paid spend\"), run **repurpose** first to produce the assets, then hand to **paid** — do not silently merge; state which mode you ran.\n\n## Quick Start\n\nShortest invocation:\n\n```\nWhich frozen auditor-approved asset with current active paid rights should we amplify from [campaign]?  # paid\nHow can we repurpose this frozen approved asset within its evidenced active destination scope?           # repurpose\n```\n\nCommon scenarios:\n\n```\n--mode paid: Create a $5,000 TikTok\u002FInstagram plan from these frozen approved assets and supplied current active scoped-rights records\n--mode repurpose: Build a 30-day plan from these 3 frozen approved videos and supplied current active rights records covering the requested destinations\n```\n\nOutput expectation — **paid**: every evidence-complete candidate scored, tiered, and given a spend that sums to budget, plus a scale\u002Fpause playbook. Any candidate missing organic-performance evidence or a Hook\u002FMessage\u002FQuality\u002FCTA observation remains `NOT_SCORED\u002FNEEDS_INPUT` with no `\u002F25`, rank, tier, or spend. **repurpose**: every source asset rights-tagged, at least one eligible asset mapped to 3+ formats across 2+ channels, plus a dated distribution plan.\n\n## Skill Contract\n\n- **Reads**:\n  - *paid* — stable opaque `creator_ref` values plus transient creator locators, platform, content type, dated organic reach\u002Fengagement\u002Fviews evidence, separate dated Hook\u002FMessage\u002FQuality\u002FCTA observations, amplification budget, campaign objective (awareness\u002Ftraffic\u002Fconversions), target platforms, any prior performance data the user provides, and each candidate asset's current rights status\u002Fevidence plus existing placements when present.\n  - *repurpose* — source UGC assets (videos, reels, reviews, images), stable opaque `creator_ref` values plus transient creator locators and platforms, exact frozen `approved_asset_ref`, opaque authorized `source_ref`, usage rights per asset, rights status with observation time\u002Fevidence, original performance metrics, target channels, and existing placements. For atomizing a source, the pasted transcript\u002Fcaption\u002Freview text is transient evidence bound to that three-ref source identity; a raw handle or content URL never becomes `source_ref`.\n  - Both pull prior campaign context from `memory\u002Fhot-cache.md` when `memory-management` is active.\n- **Writes**: return the mode's deliverable and handoff inline by default; save to `memory\u002Finfluencer\u002Fcontent-amplifier\u002FYYYY-MM-DD-\u003Ctopic>.md` only with exact WARM-save authorization. Saved artifacts and handoffs reuse an explicitly carried opaque `creator_ref`, or a verified creator-registry aggregate ID; otherwise generate one random `creator-\u003CUUIDv4>` once for the lineage. Never persist a raw handle, creator name, profile\u002Fcontent URL, email, provider ID, or deterministic hash as identity. Keep only `creator_ref`, frozen asset\u002Fapproval refs, opaque evidence\u002Frights\u002Fcontact\u002Fplacement refs, and non-identifying campaign data; every saved atom source must carry `creator_ref` + exact `approved_asset_ref` + opaque `source_ref`. If no authorized resolver exists, mark identity unresolved and require the transient locator again when needed.\n- **Promotes**: only with separate exact authorization, promote durable facts — *paid*: chosen amplification mix, per-creator spend tiers, winning audiences, scale\u002Fpause thresholds; *repurpose*: rights levels, expiration dates, library naming convention, top-performing source assets — to `memory\u002Fhot-cache.md`. A newly observed revocation, dispute, expiry, or other rights-status change is not made canonical here: offer only a separately authorized handoff to the existing [creator-registry](..\u002F..\u002F..\u002Fprotocol\u002Fcreator-registry\u002FSKILL.md) proposal path with the exact status evidence. This skill does not append or accept that proposal.\n- **Done when**:\n  - *paid* — (1) each evidence-complete candidate has dated evidence for organic performance plus Hook\u002FMessage\u002FQuality\u002FCTA and is scored \u002F25 before any tier or spend; every incomplete candidate is `NOT_SCORED\u002FNEEDS_INPUT` with no total\u002Frank\u002Ftier\u002Fspend; (2) a budget allocation across only evidence-complete eligible content, objectives, and platforms sums to the stated budget; (3) an optimization plan with supplied KPI targets and scale\u002Fpause rules is recorded, or those rules stay `NEEDS_INPUT`; (4) every selected asset has current `active` rights evidence covering the intended use.\n  - *repurpose* — (1) every source asset has a rights level, expiration, `active | expired | revoked | disputed | unknown` status, `status_observed_at`, and `status_evidence_ref`; (2) at least one source asset is mapped to 3+ distinct output formats across 2+ channels; (3) a dated distribution plan with an asset checklist exists; (4) any existing placement affected by a non-active or out-of-scope status appears in the manual removal queue.\n- **Primary next skill**: *paid* → [performance-analyzer](..\u002F..\u002Freport\u002Fperformance-analyzer\u002FSKILL.md) once campaigns are live; *repurpose* → [landing-optimizer](..\u002F..\u002Freport\u002Flanding-optimizer\u002FSKILL.md) to place the repurposed social proof where it converts.\n\n### Handoff Summary\n\n> Emit the standard shape from [skill-contract.md §Handoff Summary Format](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md). State which mode ran. Label every metric Measured \u002F User-provided \u002F Calculated \u002F Estimated \u002F Unknown. Never fill a missing CPM, ROAS, view count, rights date, or decision threshold with an example value: ask for the export or use `Unknown`\u002F`NEEDS_INPUT`. Organic performance and the Hook\u002FMessage\u002FQuality\u002FCTA observations are selection evidence, not forecast fields: if any is missing, do not substitute `Estimated`; set that asset to `NOT_SCORED\u002FNEEDS_INPUT` and emit no `\u002F25`, rank, tier, or spend. Use Estimated elsewhere only when the user supplied or approved the calculation inputs and assumptions, and show that basis.\n\n## Data Sources\n\nThis family is Tier 1: both modes work with no live integrations. Ask the user for the mode's inputs and produce the supported portion of the artifact from those. Never invent reach, engagement, CPM, ROAS, rights numbers, or selection observations. Missing organic reach\u002Fengagement\u002Fviews evidence or Hook\u002FMessage\u002FQuality\u002FCTA evidence is never `Estimated`; it makes that asset `NOT_SCORED\u002FNEEDS_INPUT`. Other forecast fields may be Estimated only from supplied or explicitly approved inputs and assumptions; otherwise use `Unknown\u002FNEEDS_INPUT`.\n\nWhere a connector could sharpen the output (all optional, opt-in Tier 2\u002F3):\n\n- `~~social platform analytics` — pull organic reach, engagement rate, and view counts (both modes) instead of asking the user to paste them.\n- `~~ad platform` (Meta Ads Manager, TikTok Ads Manager, Google Ads) — read live CPM\u002FCTR\u002FCPC\u002FROAS for the paid optimization playbook, and confirm Spark Ads \u002F Partnership Ad authorization status.\n- `~~influencer database` — verify creator audience demographics for lookalike targeting (paid); transiently resolve creator locators while retaining only `creator_ref`, platform, and contract-rights refs in saved repurpose artifacts.\n- `~~DAM \u002F asset library` — store and tag processed assets; enforce the naming convention (repurpose).\n- `~~CRM` — supply retargeting\u002Fexclusion audiences (paid); reconcile creator records with usage-rights expirations (repurpose).\n\nSee [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) for the verified free\u002Fkeyless recipe per category. None are required; absent a connector, the user supplies the numbers.\n\n## Instructions\n\nSelect the mode first (see Mode selector), then run that mode's steps. Each step has a fill-in template in [references\u002Ftemplates.md](references\u002Ftemplates.md) — produce the populated artifact, do not skip the table.\n\n### Mode: paid\n\n1. **Assess available content** — build the content inventory: campaign, piece count, budget, `creator_ref`, platform\u002Ftype, and dated organic reach\u002FER\u002Fviews values with evidence refs. Do not create an organic-performance score from an absent, undated, or unevidenced metric. [Paid Step 1 template](references\u002Ftemplates.md#paid-1-content-inventory-step-1).\n2. **Select content for amplification** — record separate 1–5 observations for organic performance, Hook, Message, Quality, and CTA, each with `source_ref` and `observed_at`. Only when all five are present may the asset receive `\u002F25`, rank, tier, or spend. If any component or its evidence is missing, preserve supplied observations, set `score_state: NOT_SCORED` and execution `NEEDS_INPUT`, list the exact gaps, and do not estimate, normalize, prorate, or hand-calculate a partial total. [Paid Step 2 template](references\u002Ftemplates.md#paid-2-content-selection-step-2).\n3. **Develop amplification strategy** — describe three operational methods neutrally: whitelisting \u002F Partnership \u002F Spark Ads use the creator identity and require matching platform authorization; brand-account ads use the brand identity and require the licensed asset in the brand ad account; dark posts are unpublished ad-account placements. Do not claim that one method improves engagement, preserves authenticity, boosts credibility, or performs better\u002Fworse without supplied comparative evidence. Treat method choice and budget mix as a declared test or user decision. [Paid Step 3 template](references\u002Ftemplates.md#paid-3-amplification-strategy-step-3-method-detail).\n4. **Set up targeting** — primary lookalike off the creator's engaged audience, plus expansion segments (interest\u002Fbehavioral\u002Fdemographic for awareness; retargeting\u002Fcustom\u002Flookalike for conversions), ad sets per platform, and exclusions. [Paid Step 4 template](references\u002Ftemplates.md#paid-4-audience-targeting-step-4).\n5. **Allocate budget** — split the stated budget only across rights-eligible, fully scored assets, then by objective and platform; set a pacing schedule (learning → optimization → scaling). Allocations must sum to the stated budget. If no fully scored eligible asset remains, return `NEEDS_INPUT` and no hypothetical allocation. [Paid Step 5 template](references\u002Ftemplates.md#paid-5-budget-allocation-step-5).\n6. **Optimization playbook** — KPI table (CPM, CTR, CPC, CVR, ROAS) with below\u002Fabove-target actions, an optimization schedule, A\u002FB tests, and explicit scale-up \u002F pause \u002F creative-refresh thresholds. [Paid Step 6 template](references\u002Ftemplates.md#paid-6-optimization-playbook-step-6).\n7. **Platform-specific setup** — verify the frozen asset version is auditor-approved and its rights tracker says `active` with a dated evidence reference; separately confirm the grant is unexpired and scoped to the intended platform, territory, format, and paid use. `expired`, `revoked`, `disputed`, or `unknown` fails closed for new use. Spark\u002Fboost or other existing-post methods also require the matching live post and platform authorization; dark-post setup does not require prior organic publication. Missing approval, required live state, or usable rights stops activation with `NEEDS_INPUT`; none may be inferred. [Paid Step 7 guide](references\u002Ftemplates.md#paid-7-platform-specific-setup-step-7).\n\nReturn the populated artifact inline. Offer its exact WARM path for save authorization, then ask separately before any HOT promotion. Any ad-account setup, upload, launch, or spend is a further external mutation requiring exact action approval.\n\n### Mode: repurpose\n\n1. **Audit available content** — build a content inventory and rights summary: every asset gets an ID, creator, platform, type, rights level\u002Fexpiry, rights status, `status_observed_at`, and `status_evidence_ref`. [Repurpose Step 1 template](references\u002Ftemplates.md#repurpose-1-content-inventory-step-1).\n2. **Map repurposing opportunities** — for each source asset, list output formats, target channels, modifications, and effort (one video → 10+ assets). [Repurpose Step 2 template](references\u002Ftemplates.md#repurpose-2-repurposing-opportunity-map-step-2).\n3. **Create the repurposing plan** — rank source assets by performance and rights, then lay out a channel distribution plan across paid, owned, social, and sales. [Repurpose Step 3 template](references\u002Ftemplates.md#repurpose-3-repurposing-plan-step-3).\n4. **Specify format transformations** — give aspect ratio, duration, and modification specs for video→video, video→static, quote\u002Freview, and image conversions. Per-platform specs live in [references\u002Fplatforms\u002F](..\u002F..\u002F..\u002Freferences\u002Fplatforms). [Repurpose Step 4 specs](references\u002Ftemplates.md#repurpose-4-format-transformation-specs-step-4).\n5. **Apply channel guidelines** — website, email, paid (incl. a creative testing matrix), and organic social best practices. [Repurpose Step 5 guidelines](references\u002Ftemplates.md#repurpose-5-channel-specific-guidelines-step-5).\n6. **Build the content library** — folder structure, the `[campaign]_[creator_ref]_[platform]_[type]_[variation]_[date]` naming convention, and metadata fields. [Repurpose Step 6 structure](references\u002Ftemplates.md#repurpose-6-content-library-structure-step-6).\n7. **Track rights** — rights-by-content matrix, expiring-rights alerts, rights-expansion opportunities, and a manual removal queue derived only from existing placements. Before recommending a destination, require `status: active` with `status_observed_at` and `status_evidence_ref`, then verify that the grant is unexpired and covers that channel, territory, format, and use. `expired`, `revoked`, `disputed`, `unknown`, and out-of-scope rights remain blocked for new use. Put affected existing placements in the queue with destination, owner, `due_at`, and `completion_ref`; a blank completion reference means removal is not proven. [Repurpose Step 7 tracker](references\u002Ftemplates.md#repurpose-7-usage-rights-tracker-step-7).\n\nFor slicing one source into many output atoms, apply the 7-tier extraction in [references\u002Fatom-extraction.md](references\u002Fatom-extraction.md). Bind every atom to `creator_ref`, exact `approved_asset_ref`, and an opaque authorized `source_ref`. Any atom ranking, virality score, near-duplicate threshold, paid-placement choice, or hero-placement choice requires a user-approved rule or source-dated rule ref; without one, retain the atoms as `NOT_SCORED\u002FNEEDS_INPUT` and do not auto-rank\u002Fdrop\u002Fselect them. Return the populated artifact inline; request one exact authorization for its WARM save and a separate authorization for any HOT promotion.\n\nFor either mode, the removal queue is a hand-operated follow-up view, not authorization to remove or edit anything. Never pause an ad, delete a post, unpublish a page, edit a platform, or mark `completion_ref` without separate exact action approval and completion evidence. When rights status changes, offer the exact evidence to the existing creator-registry proposal workflow only after separate authorization; do not create a new rights registry or treat the WARM tracker as canonical.\n\n## Decision Gates\n\n- **Stop and ask** — only when a mode input needed to proceed is missing and not inferable: (1) *paid* has no budget — ask for the amplification budget; (2) a paid candidate lacks dated\u002Fevidenced organic metrics or any Hook\u002FMessage\u002FQuality\u002FCTA observation — return that asset as `NOT_SCORED\u002FNEEDS_INPUT` with no total\u002Frank\u002Ftier\u002Fspend; (3) either mode lacks the frozen asset's auditor-approval reference, has assets whose rights are `expired`, `revoked`, `disputed`, `unknown`, lack dated status evidence, or do not cover the intended channel\u002Fterritory\u002Fformat\u002Fuse — return `NEEDS_INPUT` for the exact approval or rights gap before recommending activation or reuse, because neither approval nor a restricted grant may be guessed through.\n- **Continue silently** — do not stop for a missing optional connector or a platform absent from the reference set; use user-supplied evidence or the nearest documented format analog and disclose it. You may continue rights inventory or evidence-gap reporting for an incomplete candidate, but may not deep-dive, rank, tier, allocate spend, or create a paid recommendation for it.\n\n## Example\n\n**paid** — *User*: \"The dated organic export supplies views\u002FER and Hook observations for five frozen, auditor-approved assets with active scoped paid rights, but we have no Message, Quality, or CTA observations. Allocate our $5,000 budget.\"\n\n```markdown\nEvidence basis: organic metrics, Hook observations, frozen approval refs, and rights status\u002Fscope are user-provided; Message, Quality, and CTA evidence is missing.\n\n| Creator Ref | Organic | Hook | Message | Quality | CTA | Score State | Total \u002F Rank \u002F Spend |\n|-------------|---------|------|---------|---------|-----|-------------|----------------------|\n| [creator_ref per asset] | supplied | supplied | Unknown | Unknown | Unknown | `NOT_SCORED\u002FNEEDS_INPUT` | none |\n\nNo `\u002F25`, rank, tier, or allocation is emitted. Request dated Message\u002FQuality\u002FCTA observations with opaque evidence refs; never fill them with `Estimated` or force a partial total.\n```\n\n**repurpose** — *User*: \"Use three supplied frozen, auditor-approved assets mapped to `creator_ref-1`, `creator_ref-2`, and `creator_ref-3`. Their rights records are `active`, dated, evidenced, unexpired, and cover the requested derivative edits and US paid, website, email, organic-social, and YouTube destinations. Build a 30-day reuse plan.\" → Map only those evidenced uses and retain `creator_ref` plus opaque asset\u002Fevidence refs in the plan.\n\nIf either request omitted the frozen approval reference or current scoped-rights evidence, return `NEEDS_INPUT` with those exact gaps and do not rank, allocate, transform, or schedule the asset. Paid selection additionally stays `NOT_SCORED\u002FNEEDS_INPUT` when organic metrics\u002Fevidence or any Hook\u002FMessage\u002FQuality\u002FCTA observation\u002Fevidence is missing.\n\nFull rankings, strategies, setups, and both worked examples: [references\u002Ftemplates.md](references\u002Ftemplates.md).\n\n## Reference Materials\n\n- [templates.md](references\u002Ftemplates.md) — fill-in templates for every step of both modes, platform setup guides, format transformation specs, both worked examples, and tips.\n- [atom-extraction.md](references\u002Fatom-extraction.md) — 7-tier content-atom extraction, the virality heuristic, and the Jaccard near-duplicate flag for slicing one source into many (repurpose mode).\n- Per-platform format & placement specs: [tiktok](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Ftiktok.md) · [youtube](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Fyoutube.md) · [linkedin](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Flinkedin.md) · [x](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Fx.md) · [reddit](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Freddit.md) · [grokipedia](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Fgrokipedia.md).\n- [star-benchmark.md](..\u002F..\u002F..\u002Freferences\u002Fstar-benchmark.md) — the STAR framework; the Trust vetoes (`STAR-T1` FTC disclosure, `STAR-T2` claim integrity) that creator-content-auditor enforces before this skill runs.\n- [skill-contract.md](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md) — shared contract and Handoff Summary format.\n- [state-model.md](..\u002F..\u002F..\u002Freferences\u002Fstate-model.md) — HOT\u002FWARM\u002FCOLD memory tiers and save conventions.\n- [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) — free\u002Fkeyless data recipe per connector category.\n- Sibling skills: [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md), [contract-helper](..\u002Fcontract-helper\u002FSKILL.md), [landing-optimizer](..\u002F..\u002Freport\u002Flanding-optimizer\u002FSKILL.md), [budget-optimizer](..\u002F..\u002Ftarget\u002Fbudget-optimizer\u002FSKILL.md), [performance-analyzer](..\u002F..\u002Freport\u002Fperformance-analyzer\u002FSKILL.md).\n\n## Save Results\n\nAfter delivering findings inline, ask: \"Save these results for future sessions?\" If yes, obtain exact authorization for `memory\u002Finfluencer\u002Fcontent-amplifier\u002FYYYY-MM-DD-\u003Ctopic>.md` and write the one-line verdict\u002Fheadline, top 3-5 actionable items, open loops or blockers, and opaque source references. Saved identity is `creator_ref` only; remove raw handles, names, profile\u002Fcontent URLs, emails, and provider IDs. Saving does not authorize HOT promotion or any ad-platform mutation. This skill hands veto-like risks (missing disclosure, unsubstantiated claims) to [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) rather than judging them here.\n\n## Next Best Skill\n\n**Primary**:\n- *paid mode* → [performance-analyzer](..\u002F..\u002Freport\u002Fperformance-analyzer\u002FSKILL.md) — measure amplification results once campaigns are live.\n- *repurpose mode* → [landing-optimizer](..\u002F..\u002Freport\u002Flanding-optimizer\u002FSKILL.md) — drop the repurposed testimonials, hero videos, and quote cards onto the pages that convert.\n\n**Alternates**:\n- [content-amplifier --mode paid](SKILL.md) — when repurposed ad variations are ready for paid spend (run only if repurpose ran this session and paid has not).\n- [contract-helper](..\u002Fcontract-helper\u002FSKILL.md) — secure or expand usage rights before reuse (repurpose).\n- [budget-optimizer](..\u002F..\u002Ftarget\u002Fbudget-optimizer\u002FSKILL.md) — reallocate paid budget across the recommended tiers (paid).\n\n**Termination**: maintain a visited-set this session. If a recommended target (including the sibling mode of this skill) already ran, STOP and report the chain complete rather than re-invoking it. Max chain depth 3. When routing is ambiguous, present the options and stop instead of auto-following.\n","# Content Amplifier\n\nExtract more value from a frozen, approved creator asset. Two modes: **paid** (extend reach with paid spend — whitelisting, Spark Ads, dark posts, budget + optimization) and **repurpose** (reuse one asset across paid, website, email, and social — inventory, repurposing map, format specs, distribution plan). Both start from the exact version cleared by [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) and active scoped rights. Spark\u002Fboost paths additionally require the platform state and live post they depend on; a dark post need not have been published organically.\n\n**Scope guard**: this skill does NOT score a deliverable for brand alignment, message accuracy, or FTC\u002Fdisclosure compliance, and it does NOT compute a STAR Trust\u002FAppeal score or run the `STAR-T1`\u002F`STAR-T2` veto — that is the [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) gate's job. This skill works the downstream lever: turning approved content into paid reach or many-channel assets, then hands off. In a product launch, this skill owns the **repurposing map and the paid-amplification \u002F distribution execution calendar** (including the 30-day plan for launch content); the launch discipline's [momentum-planner](..\u002F..\u002F..\u002Flaunch\u002Fprove\u002Fmomentum-planner\u002FSKILL.md) schedules only the launch *moments* and hands the distribution work here. In always-on organic social the split is the same shape: the standing brand posting calendar belongs to [social-calendar-builder](..\u002F..\u002F..\u002Fsocial\u002Fcraft\u002Fsocial-calendar-builder\u002FSKILL.md) and net-new idea-to-multi-platform package drafting to [social-creative-builder](..\u002F..\u002F..\u002Fsocial\u002Fcraft\u002Fsocial-creative-builder\u002FSKILL.md) — this skill keeps repurposing of existing assets and ALL paid amplification, and the social discipline only flags boost-worthy organic winners to it.\n\n## Mode selector\n\n| Mode | Use when | Core output |\n|------|----------|-------------|\n| **paid** (default) | Extend the reach of organic creator content with paid spend | Content-selection scorecard, amplification strategy (whitelisting \u002F boosting \u002F dark posts), audience targeting, budget allocation, optimization playbook |\n| **repurpose** | Reuse one approved asset across paid, website, email, and social | Rights-tracked inventory, 1-video-to-10+ repurposing map, format transformation specs, 30-day distribution plan, content library + rights tracker |\n\nPick with `--mode paid` or `--mode repurpose`. If unset: \"boost \u002F amplify \u002F whitelisting \u002F Spark Ads \u002F dark post \u002F paid spend \u002F budget\" → **paid**; \"repurpose \u002F reuse \u002F turn one video into many \u002F asset library \u002F social proof on pages \u002F multi-channel rollout\" → **repurpose**. If the request spans both (e.g. \"cut ad variations *and* plan the paid spend\"), run **repurpose** first to produce the assets, then hand to **paid** — do not silently merge; state which mode you ran.\n\n## Quick Start\n\nShortest invocation:\n\n```\nWhich frozen auditor-approved asset with current active paid rights should we amplify from [campaign]?  # paid\nHow can we repurpose this frozen approved asset within its evidenced active destination scope?           # repurpose\n```\n\nCommon scenarios:\n\n```\n--mode paid: Create a $5,000 TikTok\u002FInstagram plan from these frozen approved assets and supplied current active scoped-rights records\n--mode repurpose: Build a 30-day plan from these 3 frozen approved videos and supplied current active rights records covering the requested destinations\n```\n\nOutput expectation — **paid**: every evidence-complete candidate scored, tiered, and given a spend that sums to budget, plus a scale\u002Fpause playbook. Any candidate missing organic-performance evidence or a Hook\u002FMessage\u002FQuality\u002FCTA observation remains `NOT_SCORED\u002FNEEDS_INPUT` with no `\u002F25`, rank, tier, or spend. **repurpose**: every source asset rights-tagged, at least one eligible asset mapped to 3+ formats across 2+ channels, plus a dated distribution plan.\n\n## Skill Contract\n\n- **Reads**:\n  - *paid* — stable opaque `creator_ref` values plus transient creator locators, platform, content type, dated organic reach\u002Fengagement\u002Fviews evidence, separate dated Hook\u002FMessage\u002FQuality\u002FCTA observations, amplification budget, campaign objective (awareness\u002Ftraffic\u002Fconversions), target platforms, any prior performance data the user provides, and each candidate asset's current rights status\u002Fevidence plus existing placements when present.\n  - *repurpose* — source UGC assets (videos, reels, reviews, images), stable opaque `creator_ref` values plus transient creator locators and platforms, exact frozen `approved_asset_ref`, opaque authorized `source_ref`, usage rights per asset, rights status with observation time\u002Fevidence, original performance metrics, target channels, and existing placements. For atomizing a source, the pasted transcript\u002Fcaption\u002Freview text is transient evidence bound to that three-ref source identity; a raw handle or content URL never becomes `source_ref`.\n  - Both pull prior campaign context from `memory\u002Fhot-cache.md` when `memory-management` is active.\n- **Writes**: return the mode's deliverable and handoff inline by default; save to `memory\u002Finfluencer\u002Fcontent-amplifier\u002FYYYY-MM-DD-\u003Ctopic>.md` only with exact WARM-save authorization. Saved artifacts and handoffs reuse an explicitly carried opaque `creator_ref`, or a verified creator-registry aggregate ID; otherwise generate one random `creator-\u003CUUIDv4>` once for the lineage. Never persist a raw handle, creator name, profile\u002Fcontent URL, email, provider ID, or deterministic hash as identity. Keep only `creator_ref`, frozen asset\u002Fapproval refs, opaque evidence\u002Frights\u002Fcontact\u002Fplacement refs, and non-identifying campaign data; every saved atom source must carry `creator_ref` + exact `approved_asset_ref` + opaque `source_ref`. If no authorized resolver exists, mark identity unresolved and require the transient locator again when needed.\n- **Promotes**: only with separate exact authorization, promote durable facts — *paid*: chosen amplification mix, per-creator spend tiers, winning audiences, scale\u002Fpause thresholds; *repurpose*: rights levels, expiration dates, library naming convention, top-performing source assets — to `memory\u002Fhot-cache.md`. A newly observed revocation, dispute, expiry, or other rights-status change is not made canonical here: offer only a separately authorized handoff to the existing [creator-registry](..\u002F..\u002F..\u002Fprotocol\u002Fcreator-registry\u002FSKILL.md) proposal path with the exact status evidence. This skill does not append or accept that proposal.\n- **Done when**:\n  - *paid* — (1) each evidence-complete candidate has dated evidence for organic performance plus Hook\u002FMessage\u002FQuality\u002FCTA and is scored \u002F25 before any tier or spend; every incomplete candidate is `NOT_SCORED\u002FNEEDS_INPUT` with no total\u002Frank\u002Ftier\u002Fspend; (2) a budget allocation across only evidence-complete eligible content, objectives, and platforms sums to the stated budget; (3) an optimization plan with supplied KPI targets and scale\u002Fpause rules is recorded, or those rules stay `NEEDS_INPUT`; (4) every selected asset has current `active` rights evidence covering the intended use.\n  - *repurpose* — (1) every source asset has a rights level, expiration, `active | expired | revoked | disputed | unknown` status, `status_observed_at`, and `status_evidence_ref`; (2) at least one source asset is mapped to 3+ distinct output formats across 2+ channels; (3) a dated distribution plan with an asset checklist exists; (4) any existing placement affected by a non-active or out-of-scope status appears in the manual removal queue.\n- **Primary next skill**: *paid* → [performance-analyzer](..\u002F..\u002Freport\u002Fperformance-analyzer\u002FSKILL.md) once campaigns are live; *repurpose* → [landing-optimizer](..\u002F..\u002Freport\u002Flanding-optimizer\u002FSKILL.md) to place the repurposed social proof where it converts.\n\n### Handoff Summary\n\n> Emit the standard shape from [skill-contract.md §Handoff Summary Format](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md). State which mode ran. Label every metric Measured \u002F User-provided \u002F Calculated \u002F Estimated \u002F Unknown. Never fill a missing CPM, ROAS, view count, rights date, or decision threshold with an example value: ask for the export or use `Unknown`\u002F`NEEDS_INPUT`. Organic performance and the Hook\u002FMessage\u002FQuality\u002FCTA observations are selection evidence, not forecast fields: if any is missing, do not substitute `Estimated`; set that asset to `NOT_SCORED\u002FNEEDS_INPUT` and emit no `\u002F25`, rank, tier, or spend. Use Estimated elsewhere only when the user supplied or approved the calculation inputs and assumptions, and show that basis.\n\n## Data Sources\n\nThis family is Tier 1: both modes work with no live integrations. Ask the user for the mode's inputs and produce the supported portion of the artifact from those. Never invent reach, engagement, CPM, ROAS, rights numbers, or selection observations. Missing organic reach\u002Fengagement\u002Fviews evidence or Hook\u002FMessage\u002FQuality\u002FCTA evidence is never `Estimated`; it makes that asset `NOT_SCORED\u002FNEEDS_INPUT`. Other forecast fields may be Estimated only from supplied or explicitly approved inputs and assumptions; otherwise use `Unknown\u002FNEEDS_INPUT`.\n\nWhere a connector could sharpen the output (all optional, opt-in Tier 2\u002F3):\n\n- `~~social platform analytics` — pull organic reach, engagement rate, and view counts (both modes) instead of asking the user to paste them.\n- `~~ad platform` (Meta Ads Manager, TikTok Ads Manager, Google Ads) — read live CPM\u002FCTR\u002FCPC\u002FROAS for the paid optimization playbook, and confirm Spark Ads \u002F Partnership Ad authorization status.\n- `~~influencer database` — verify creator audience demographics for lookalike targeting (paid); transiently resolve creator locators while retaining only `creator_ref`, platform, and contract-rights refs in saved repurpose artifacts.\n- `~~DAM \u002F asset library` — store and tag processed assets; enforce the naming convention (repurpose).\n- `~~CRM` — supply retargeting\u002Fexclusion audiences (paid); reconcile creator records with usage-rights expirations (repurpose).\n\nSee [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) for the verified free\u002Fkeyless recipe per category. None are required; absent a connector, the user supplies the numbers.\n\n## Instructions\n\nSelect the mode first (see Mode selector), then run that mode's steps. Each step has a fill-in template in [references\u002Ftemplates.md](references\u002Ftemplates.md) — produce the populated artifact, do not skip the table.\n\n### Mode: paid\n\n1. **Assess available content** — build the content inventory: campaign, piece count, budget, `creator_ref`, platform\u002Ftype, and dated organic reach\u002FER\u002Fviews values with evidence refs. Do not create an organic-performance score from an absent, undated, or unevidenced metric. [Paid Step 1 template](references\u002Ftemplates.md#paid-1-content-inventory-step-1).\n2. **Select content for amplification** — record separate 1–5 observations for organic performance, Hook, Message, Quality, and CTA, each with `source_ref` and `observed_at`. Only when all five are present may the asset receive `\u002F25`, rank, tier, or spend. If any component or its evidence is missing, preserve supplied observations, set `score_state: NOT_SCORED` and execution `NEEDS_INPUT`, list the exact gaps, and do not estimate, normalize, prorate, or hand-calculate a partial total. [Paid Step 2 template](references\u002Ftemplates.md#paid-2-content-selection-step-2).\n3. **Develop amplification strategy** — describe three operational methods neutrally: whitelisting \u002F Partnership \u002F Spark Ads use the creator identity and require matching platform authorization; brand-account ads use the brand identity and require the licensed asset in the brand ad account; dark posts are unpublished ad-account placements. Do not claim that one method improves engagement, preserves authenticity, boosts credibility, or performs better\u002Fworse without supplied comparative evidence. Treat method choice and budget mix as a declared test or user decision. [Paid Step 3 template](references\u002Ftemplates.md#paid-3-amplification-strategy-step-3-method-detail).\n4. **Set up targeting** — primary lookalike off the creator's engaged audience, plus expansion segments (interest\u002Fbehavioral\u002Fdemographic for awareness; retargeting\u002Fcustom\u002Flookalike for conversions), ad sets per platform, and exclusions. [Paid Step 4 template](references\u002Ftemplates.md#paid-4-audience-targeting-step-4).\n5. **Allocate budget** — split the stated budget only across rights-eligible, fully scored assets, then by objective and platform; set a pacing schedule (learning → optimization → scaling). Allocations must sum to the stated budget. If no fully scored eligible asset remains, return `NEEDS_INPUT` and no hypothetical allocation. [Paid Step 5 template](references\u002Ftemplates.md#paid-5-budget-allocation-step-5).\n6. **Optimization playbook** — KPI table (CPM, CTR, CPC, CVR, ROAS) with below\u002Fabove-target actions, an optimization schedule, A\u002FB tests, and explicit scale-up \u002F pause \u002F creative-refresh thresholds. [Paid Step 6 template](references\u002Ftemplates.md#paid-6-optimization-playbook-step-6).\n7. **Platform-specific setup** — verify the frozen asset version is auditor-approved and its rights tracker says `active` with a dated evidence reference; separately confirm the grant is unexpired and scoped to the intended platform, territory, format, and paid use. `expired`, `revoked`, `disputed`, or `unknown` fails closed for new use. Spark\u002Fboost or other existing-post methods also require the matching live post and platform authorization; dark-post setup does not require prior organic publication. Missing approval, required live state, or usable rights stops activation with `NEEDS_INPUT`; none may be inferred. [Paid Step 7 guide](references\u002Ftemplates.md#paid-7-platform-specific-setup-step-7).\n\nReturn the populated artifact inline. Offer its exact WARM path for save authorization, then ask separately before any HOT promotion. Any ad-account setup, upload, launch, or spend is a further external mutation requiring exact action approval.\n\n### Mode: repurpose\n\n1. **Audit available content** — build a content inventory and rights summary: every asset gets an ID, creator, platform, type, rights level\u002Fexpiry, rights status, `status_observed_at`, and `status_evidence_ref`. [Repurpose Step 1 template](references\u002Ftemplates.md#repurpose-1-content-inventory-step-1).\n2. **Map repurposing opportunities** — for each source asset, list output formats, target channels, modifications, and effort (one video → 10+ assets). [Repurpose Step 2 template](references\u002Ftemplates.md#repurpose-2-repurposing-opportunity-map-step-2).\n3. **Create the repurposing plan** — rank source assets by performance and rights, then lay out a channel distribution plan across paid, owned, social, and sales. [Repurpose Step 3 template](references\u002Ftemplates.md#repurpose-3-repurposing-plan-step-3).\n4. **Specify format transformations** — give aspect ratio, duration, and modification specs for video→video, video→static, quote\u002Freview, and image conversions. Per-platform specs live in [references\u002Fplatforms\u002F](..\u002F..\u002F..\u002Freferences\u002Fplatforms). [Repurpose Step 4 specs](references\u002Ftemplates.md#repurpose-4-format-transformation-specs-step-4).\n5. **Apply channel guidelines** — website, email, paid (incl. a creative testing matrix), and organic social best practices. [Repurpose Step 5 guidelines](references\u002Ftemplates.md#repurpose-5-channel-specific-guidelines-step-5).\n6. **Build the content library** — folder structure, the `[campaign]_[creator_ref]_[platform]_[type]_[variation]_[date]` naming convention, and metadata fields. [Repurpose Step 6 structure](references\u002Ftemplates.md#repurpose-6-content-library-structure-step-6).\n7. **Track rights** — rights-by-content matrix, expiring-rights alerts, rights-expansion opportunities, and a manual removal queue derived only from existing placements. Before recommending a destination, require `status: active` with `status_observed_at` and `status_evidence_ref`, then verify that the grant is unexpired and covers that channel, territory, format, and use. `expired`, `revoked`, `disputed`, `unknown`, and out-of-scope rights remain blocked for new use. Put affected existing placements in the queue with destination, owner, `due_at`, and `completion_ref`; a blank completion reference means removal is not proven. [Repurpose Step 7 tracker](references\u002Ftemplates.md#repurpose-7-usage-rights-tracker-step-7).\n\nFor slicing one source into many output atoms, apply the 7-tier extraction in [references\u002Fatom-extraction.md](references\u002Fatom-extraction.md). Bind every atom to `creator_ref`, exact `approved_asset_ref`, and an opaque authorized `source_ref`. Any atom ranking, virality score, near-duplicate threshold, paid-placement choice, or hero-placement choice requires a user-approved rule or source-dated rule ref; without one, retain the atoms as `NOT_SCORED\u002FNEEDS_INPUT` and do not auto-rank\u002Fdrop\u002Fselect them. Return the populated artifact inline; request one exact authorization for its WARM save and a separate authorization for any HOT promotion.\n\nFor either mode, the removal queue is a hand-operated follow-up view, not authorization to remove or edit anything. Never pause an ad, delete a post, unpublish a page, edit a platform, or mark `completion_ref` without separate exact action approval and completion evidence. When rights status changes, offer the exact evidence to the existing creator-registry proposal workflow only after separate authorization; do not create a new rights registry or treat the WARM tracker as canonical.\n\n## Decision Gates\n\n- **Stop and ask** — only when a mode input needed to proceed is missing and not inferable: (1) *paid* has no budget — ask for the amplification budget; (2) a paid candidate lacks dated\u002Fevidenced organic metrics or any Hook\u002FMessage\u002FQuality\u002FCTA observation — return that asset as `NOT_SCORED\u002FNEEDS_INPUT` with no total\u002Frank\u002Ftier\u002Fspend; (3) either mode lacks the frozen asset's auditor-approval reference, has assets whose rights are `expired`, `revoked`, `disputed`, `unknown`, lack dated status evidence, or do not cover the intended channel\u002Fterritory\u002Fformat\u002Fuse — return `NEEDS_INPUT` for the exact approval or rights gap before recommending activation or reuse, because neither approval nor a restricted grant may be guessed through.\n- **Continue silently** — do not stop for a missing optional connector or a platform absent from the reference set; use user-supplied evidence or the nearest documented format analog and disclose it. You may continue rights inventory or evidence-gap reporting for an incomplete candidate, but may not deep-dive, rank, tier, allocate spend, or create a paid recommendation for it.\n\n## Example\n\n**paid** — *User*: \"The dated organic export supplies views\u002FER and Hook observations for five frozen, auditor-approved assets with active scoped paid rights, but we have no Message, Quality, or CTA observations. Allocate our $5,000 budget.\"\n\n```markdown\nEvidence basis: organic metrics, Hook observations, frozen approval refs, and rights status\u002Fscope are user-provided; Message, Quality, and CTA evidence is missing.\n\n| Creator Ref | Organic | Hook | Message | Quality | CTA | Score State | Total \u002F Rank \u002F Spend |\n|-------------|---------|------|---------|---------|-----|-------------|----------------------|\n| [creator_ref per asset] | supplied | supplied | Unknown | Unknown | Unknown | `NOT_SCORED\u002FNEEDS_INPUT` | none |\n\nNo `\u002F25`, rank, tier, or allocation is emitted. Request dated Message\u002FQuality\u002FCTA observations with opaque evidence refs; never fill them with `Estimated` or force a partial total.\n```\n\n**repurpose** — *User*: \"Use three supplied frozen, auditor-approved assets mapped to `creator_ref-1`, `creator_ref-2`, and `creator_ref-3`. Their rights records are `active`, dated, evidenced, unexpired, and cover the requested derivative edits and US paid, website, email, organic-social, and YouTube destinations. Build a 30-day reuse plan.\" → Map only those evidenced uses and retain `creator_ref` plus opaque asset\u002Fevidence refs in the plan.\n\nIf either request omitted the frozen approval reference or current scoped-rights evidence, return `NEEDS_INPUT` with those exact gaps and do not rank, allocate, transform, or schedule the asset. Paid selection additionally stays `NOT_SCORED\u002FNEEDS_INPUT` when organic metrics\u002Fevidence or any Hook\u002FMessage\u002FQuality\u002FCTA observation\u002Fevidence is missing.\n\nFull rankings, strategies, setups, and both worked examples: [references\u002Ftemplates.md](references\u002Ftemplates.md).\n\n## Reference Materials\n\n- [templates.md](references\u002Ftemplates.md) — fill-in templates for every step of both modes, platform setup guides, format transformation specs, both worked examples, and tips.\n- [atom-extraction.md](references\u002Fatom-extraction.md) — 7-tier content-atom extraction, the virality heuristic, and the Jaccard near-duplicate flag for slicing one source into many (repurpose mode).\n- Per-platform format & placement specs: [tiktok](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Ftiktok.md) · [youtube](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Fyoutube.md) · [linkedin](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Flinkedin.md) · [x](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Fx.md) · [reddit](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Freddit.md) · [grokipedia](..\u002F..\u002F..\u002Freferences\u002Fplatforms\u002Fgrokipedia.md).\n- [star-benchmark.md](..\u002F..\u002F..\u002Freferences\u002Fstar-benchmark.md) — the STAR framework; the Trust vetoes (`STAR-T1` FTC disclosure, `STAR-T2` claim integrity) that creator-content-auditor enforces before this skill runs.\n- [skill-contract.md](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md) — shared contract and Handoff Summary format.\n- [state-model.md](..\u002F..\u002F..\u002Freferences\u002Fstate-model.md) — HOT\u002FWARM\u002FCOLD memory tiers and save conventions.\n- [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md) — free\u002Fkeyless data recipe per connector category.\n- Sibling skills: [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md), [contract-helper](..\u002Fcontract-helper\u002FSKILL.md), [landing-optimizer](..\u002F..\u002Freport\u002Flanding-optimizer\u002FSKILL.md), [budget-optimizer](..\u002F..\u002Ftarget\u002Fbudget-optimizer\u002FSKILL.md), [performance-analyzer](..\u002F..\u002Freport\u002Fperformance-analyzer\u002FSKILL.md).\n\n## Save Results\n\nAfter delivering findings inline, ask: \"Save these results for future sessions?\" If yes, obtain exact authorization for `memory\u002Finfluencer\u002Fcontent-amplifier\u002FYYYY-MM-DD-\u003Ctopic>.md` and write the one-line verdict\u002Fheadline, top 3-5 actionable items, open loops or blockers, and opaque source references. Saved identity is `creator_ref` only; remove raw handles, names, profile\u002Fcontent URLs, emails, and provider IDs. Saving does not authorize HOT promotion or any ad-platform mutation. This skill hands veto-like risks (missing disclosure, unsubstantiated claims) to [creator-content-auditor](..\u002Fcreator-content-auditor\u002FSKILL.md) rather than judging them here.\n\n## Next Best Skill\n\n**Primary**:\n- *paid mode* → [performance-analyzer](..\u002F..\u002Freport\u002Fperformance-analyzer\u002FSKILL.md) — measure amplification results once campaigns are live.\n- *repurpose mode* → [landing-optimizer](..\u002F..\u002Freport\u002Flanding-optimizer\u002FSKILL.md) — drop the repurposed testimonials, hero videos, and quote cards onto the pages that convert.\n\n**Alternates**:\n- [content-amplifier --mode paid](SKILL.md) — when repurposed ad variations are ready for paid spend (run only if repurpose ran this session and paid has not).\n- [contract-helper](..\u002Fcontract-helper\u002FSKILL.md) — secure or expand usage rights before reuse (repurpose).\n- [budget-optimizer](..\u002F..\u002Ftarget\u002Fbudget-optimizer\u002FSKILL.md) — reallocate paid budget across the recommended tiers (paid).\n\n**Termination**: maintain a visited-set this session. If a recommended target (including the sibling mode of this skill) already ran, STOP and report the chain complete rather than re-invoking it. Max chain depth 3. When routing is ambiguous, present the options and stop instead of auto-following.\n",{"name":5,"slug":5,"license":15,"summary":24,"version":25,"homepage":26,"metadata":27,"description":7,"displayName":37,"when_to_use":38,"argument-hint":39,"compatibility":40},"把跑赢的创作者内容用付费放大，并将 UGC 复用到付费、网站、邮件与自然渠道","20.1.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills",{"phase":28,"author":29,"hermes":30,"version":25,"openclaw":34,"discipline":33,"geo-relevance":36},"activate","aaron-he-zhu",{"tags":31,"category":33},[32,33,28],"marketing","influencer",{"emoji":35,"homepage":26},"📣","low","Content Amplifier · 内容放量","Use when a brand has a frozen, auditor-approved creator asset with active scoped rights and wants to extract more value from it. Paid mode: extend reach with paid spend — choosing which posts to boost, setting up whitelisted Partnership Ads or TikTok Spark Ads, planning dark posts, allocating an ad budget across creators and platforms, building audience targeting off creator lookalikes, running an optimization and scale\u002Fpause playbook. Repurpose mode: reuse one asset across paid, website, email, and organic social — generating ad variations from organic clips, building a searchable rights-tracked library, populating product pages with social proof, or planning a multi-channel rollout from a small source set.","[--mode paid|repurpose] \u003Ccampaign or content set> [budget] [platforms\u002Fchannels]","Claude Code and compatible agent-skill hosts","main","ad108f7eb3f6764136d02fb875772ebb34f54078","upstreams\u002Fsource-a\u002Finfluencer\u002Factivate\u002Fcontent-amplifier",2,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar","iamwaqargulzar.com","2026-11-03 21:14:34",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill content-amplifier",{"tool":55,"command":56},"bunx","bunx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill content-amplifier",{"tool":58,"command":59},"pnpm","pnpm dlx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill content-amplifier","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Factivate\u002Fcontent-amplifier\u002FSKILL.md",true,[63,69],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fatom-extraction.md","REFERENCE","参考文档",5694,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Factivate\u002Fcontent-amplifier\u002Freferences\u002Fatom-extraction.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Ftemplates.md",35256,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Finfluencer\u002Factivate\u002Fcontent-amplifier\u002Freferences\u002Ftemplates.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AG5VYEX7J2R2AAD54A7YT7","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'record a product demo,' 'feature demo video,' 'in-app demo,' 'video pipeline,' 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AG5FMXWA33FQDNS9PS1TE6","social","When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter\u002FX, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' 'create a reel,' 'social listening,' 'brand mentions,' 'competitor monitoring,' 'top posts to comment on,' 'find people asking for,' 'carousel,' 'slide-by-slide,' or 'document post.' Use this for social content, repurposing, scheduling, video scripts, and listening. Posts avoid AI tells like 'it's not X, it's Y' reveals and broetry. For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsocial\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7AG559W96W3DGE31KXYY78S","sms","When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional\u002Fauth SMS. Also use when the user mentions \"SMS marketing,\" \"text message campaigns,\" \"SMS sequence,\" \"SMS automation,\" \"abandoned cart text,\" \"post-purchase SMS,\" \"Klaviyo SMS,\" \"Postscript,\" \"Attentive,\" \"Twilio,\" \"A2P 10DLC,\" \"TCPA,\" \"SMS compliance,\" \"short code,\" \"toll-free SMS,\" \"MMS campaign,\" \"should I do SMS,\" \"SMS vs email,\" \"WhatsApp marketing,\" \"WhatsApp Business API,\" \"WhatsApp templates,\" or \"click-to-WhatsApp.\" For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsms\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7AG4WJ9EDSECNTQN0FEAYCQ","site-architecture","When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions \"sitemap,\" \"site map,\" \"visual sitemap,\" \"site structure,\" \"page hierarchy,\" \"information architecture,\" \"IA,\" \"navigation design,\" \"URL structure,\" \"breadcrumbs,\" \"internal linking strategy,\" \"website planning,\" \"what pages do I need,\" \"how should I organize my site,\" \"site navigation,\" \"which website builder should I use,\" \"migrate my website,\" or \"add a blog to my existing site.\" Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsite-architecture\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7AG4MH58GRMSHC0TADAWQ69","signup","When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup form optimization,\" \"free trial signup,\" \"reduce signup dropoff,\" \"account creation flow,\" \"people aren't signing up,\" \"signup abandonment,\" \"trial conversion rate,\" \"nobody completes registration,\" \"too many steps to sign up,\" or \"simplify our signup.\" Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsignup\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7AG4CGGH35KYDFHYSS1BQZ5","seo-audit","When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" \"SEO health check,\" \"my traffic dropped,\" \"lost rankings,\" \"not showing up in Google,\" \"site isn't ranking,\" \"Google update hit me,\" \"page speed,\" \"core web vitals,\" \"crawl errors,\" \"indexing issues,\" \"stuck on page 2,\" \"striking distance keywords,\" \"title tag rewrite,\" \"low CTR,\" \"local SEO,\" \"Google Business Profile,\" or \"map pack.\" Use this even if the user just says something vague like \"my SEO is bad\" or \"help with SEO\" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fseo-audit\u002FSKILL.md",[],[]]