复制安装命令
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
This is the open-source content repository behind
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
来源文件:README.md
This is the open-source content repository behind Skill Store. It stores every approved Agent Skill, the records that go with it, and the automated security audits published with each skill.
This repo is a companion to the Skill Store platform, not the place to submit skills. Skills are added through skillstore.io — its review pipeline writes to this repo automatically. Please do not open a pull request here to add a skill; PRs adding skills will be closed. See Contributing a skill below.
The recommended way to install any skill is the skillstore CLI — one command works for both Claude Code and Codex:
npx skillstore add author/skill-name
For example:
npx skillstore add aiskillstore/code-review
It downloads the skill and drops it into the right skills/ directory for your tool. Claude Code auto-discovers it; for Codex, restart the session.
Prefer to do it by hand, or installing via Claude Web? See the full Installation Guides for every method (CLI, manual, and ZIP upload) and the scope directories (~/.agents/skills/, .claude/skills/, ~/.claude/skills/, .codex/skills/, …).
Submit through the platform — not through a pull request:
SKILL.md.SKILL.md — the skill definition (required, per the Agent Skills spec)LICENSE (recommended)Every submission is scanned automatically before it can be published. The audit flags things like:
eval, exec, raw system commands)Security analysis is report-only: findings inform maintainers and users, but a risk result does not automatically block an otherwise approved skill from being published. See our Security Trust Center for the methodology, limitations, and risk-level definitions.
Live Security Passport example:
.
├── skills/ # Approved, published skills (one folder each, with SKILL.md)
├── pending/ # Submissions awaiting review
├── packages/
│ ├── cli/ # The `skillstore` CLI (npx skillstore add …)
│ └── skillstore/
├── schemas/ # JSON schemas for skill records
├── scripts/ # Maintenance & scoring scripts
└── .github/workflows/ # Submission, audit, and sync automation
The contents of this repo are maintained by Skill Store's automated pipeline. Manual changes are limited to maintainers.
The marketplace catalog is MIT-licensed. Individual skills carry their own licenses — check each skill's LICENSE file.
name: content-amplifier
slug: content-amplifier
displayName: "Content Amplifier · 内容放量"
summary: "把跑赢的创作者内容用付费放大,并将 UGC 复用到付费、网站、邮件与自然渠道"
description: '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. 复用达人内容 / 内容放量.'
version: "19.0.0"
license: Apache-2.0
compatibility: "Claude Code and compatible agent-skill hosts"
homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills"
when_to_use: "Use when a brand has live, approved creator content 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/pause 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."
argument-hint: "[--mode paid|repurpose] <campaign or content set> [budget] [platforms/channels]"
metadata: {"author": "aaron-he-zhu", "version": "19.0.0", "discipline": "influencer", "phase": "activate", "geo-relevance": "low", "hermes": {"tags": ["marketing", "influencer", "activate"], "category": "influencer"}, "openclaw": {"emoji": "📣", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}Extract more value from live, approved creator content. 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 content that is already published and cleared; neither reviews whether the content is publishable — that gate is creator-content-auditor.
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 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 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 and net-new idea-to-multi-platform package drafting to social-creative-builder — this skill keeps repurposing of existing assets and ALL paid amplification, and the social discipline only flags boost-worthy organic winners to it.
| 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.
Shortest invocation:
Which influencer content should we amplify from [campaign]? # paid
How can we repurpose this influencer content across channels? # repurpose
Common scenarios:
--mode paid: Create a paid amplification plan for our influencer campaign with $5,000 across TikTok and Instagram
--mode repurpose: We have 3 great TikTok videos. Build a repurposing plan and a 30-day distribution calendar.
Output expectation — paid: every candidate scored, tiered, and given a spend that sums to budget, plus a scale/pause playbook. repurpose: every source asset rights-tagged, at least one mapped to 3+ formats across 2+ channels, plus a dated distribution plan.
memory/hot-cache.md when memory-management is active.memory/influencer/content-amplifier/YYYY-MM-DD-<topic>.md.memory/hot-cache.md (ask first).Emit the standard shape from skill-contract.md §Handoff Summary Format. State which mode ran. Label every metric Measured / User-provided / Estimated — never present a CPM, ROAS, view count, or rights date you were not given as Measured; if it is missing, ask for the export or mark it Estimated with the basis.
This family is Tier 1: both modes work with no live integrations. Ask the user for the mode's inputs and produce the full artifact from those. Never invent reach, engagement, CPM, ROAS, or rights numbers — if a value is missing, ask for the export or label it Estimated.
Where a connector could sharpen the output (all optional, opt-in Tier 2/3):
~~social platform analytics — pull organic reach, engagement rate, and view counts (both modes) instead of asking the user to paste them.~~ad platform (Meta Ads Manager, TikTok Ads Manager, Google Ads) — read live CPM/CTR/CPC/ROAS for the paid optimization playbook, and confirm Spark Ads / Partnership Ad authorization status.~~influencer database — verify creator audience demographics for lookalike targeting (paid); pull handles, platforms, and contract rights terms (repurpose).~~DAM / asset library — store and tag processed assets; enforce the naming convention (repurpose).~~CRM — supply retargeting/exclusion audiences (paid); reconcile creator records with usage-rights expirations (repurpose).See CONNECTORS.md for the verified free/keyless recipe per category. None are required; absent a connector, the user supplies the numbers.
Select the mode first (see Mode selector), then run that mode's steps. Each step has a fill-in template in references/templates.md — produce the populated artifact, do not skip the table.
Save the populated artifact and (with the user's OK) promote the chosen mix, per-creator spend tiers, winning audiences, and scale/pause thresholds.
[campaign]_[creator]_[platform]_[type]_[variation]_[date] naming convention, and metadata fields. Repurpose Step 6 structure.For slicing one source into many output atoms, apply the 7-tier extraction and near-duplicate flag in references/atom-extraction.md. Save the populated artifact and (with the user's OK) promote rights levels, expiration dates, the library naming convention, and top-performing source assets.
paid — User: "We have 5 influencer TikToks from our launch campaign. Which should we amplify with our $5,000 paid budget?"
| Creator | Views | ER | Hook | Amplify? | Budget |
|---------|-------|-----|------|----------|--------|
| @creator1 | 245K | 8.2% | 5/5 | Yes | $2,000 |
| @creator3 | 89K | 6.5% | 4/5 | Yes | $1,500 |
| @creator4 | 34K | 9.8% | 4/5 | Yes | $800 |
| @creator2 | 156K | 4.1% | 3/5 | Maybe | $500 |
| @creator5 | 67K | 2.3% | 2/5 | No | $0 |
Testing reserve $200. Get Spark Ads auth from top 3; run @creator1 as awareness,
@creator3 as traffic; scale winners after the 3-day learning phase.
repurpose — User: "We have 3 great TikTok videos. How should we repurpose them?" → 3 clips ranked; @creator1's 45s demo expands to 6 assets (Spark Ad, IG Reel, website embed, 3 stills, 15s Stories cut), backed by a 30-day calendar and asset checklist.
Full rankings, strategies, setups, and both worked examples: references/templates.md.
STAR-T1 FTC disclosure, STAR-T2 claim integrity) that creator-content-auditor enforces before this skill runs.After delivering findings, ask: "Save these results for future sessions?" If yes, write memory/influencer/content-amplifier/YYYY-MM-DD-<topic>.md with: one-line verdict/headline, top 3-5 actionable items, open loops or blockers, and source data references. Only the auditor-class gates may write memory without asking — this skill asks first, and hands veto-like risks (missing disclosure, unsubstantiated claims) to creator-content-auditor rather than judging them here.
Primary:
Alternates:
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.
评论 (0)
暂无评论,成为第一个评论者吧!