Individual skill
content-amplifier
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/boosting/dark 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. 复用达人内容 / 内容放量.
influencer/activate/content-amplifier/SKILL.md
Source commit 8be02f1f0b18253bd5f2b85f858278f042637b9a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,134
- Repository last updated
- Nov 12, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- geo Repository topic
- seo Repository topic
- agent-skills Repository topic
- content-optimization Repository topic
- generative-engine-optimization Repository topic
- marketing Repository topic
- influencer-marketing Repository topic
- paid-advertising Repository topic
- roas Repository topic
- email-marketing Repository topic
- marketing Derived category
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesSKILL.mdcore · 26,419 bytesreferences/atom-extraction.mddoc · 5,694 bytesreferences/templates.mddoc · 35,256 bytes
Read excerpt
# Content Amplifier
Extract 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](../creator-content-auditor/SKILL.md) and active scoped rights. Spark/boost paths additionally require the platform state and live post they depend on; a dark post need not have been published organically.
**Scope guard**: this skill does NOT score a deliverable for brand alignment, message accuracy, or FTC/disclosure compliance, and it does NOT compute a STAR Trust/Appeal score or run the `STAR-T1`/`STAR-T2` veto — that is the [creator-content-auditor](../creator-content-auditor/SKILL.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 / distribution execution calendar** (including the 30-day plan for launch content); the launch discipline's [momentum-planner](../../../launch/prove/momentum-planner/SKILL.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](../../../social/craft/social-calendar-builder/SKILL.md) and net-new idea-to-multi-platform package drafting to [social-creative-builder](../../../social/craft/social-creative-builder/SKILL.md) — this skill keeps repurposing of existing assets and ALL paid amplification, and the social discipline only flags boost-worthy organic winners to it.
## Mode selector
| Mode | Use when | Core output |
|------|----------|-------------|
| **paid** (default) | Extend the reach of organic creator content with paid spend | Content-selection scorecard, amplification strategy (whitelisting / boosting / dark posts), audience targeting, budget allocation, optimization playbook |
| **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 |
Pick with `--mode paid` or `--mode repurpose`. If unset: "boost / amplify / whitelisting / Spark Ads / dark post / paid spend / budget" → **paid**; "repurpose / reuse / turn one video into many / asset library / social proof on pages / 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.