Social
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
A skill your agent uses 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…
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill content-amplifier -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills content-amplifier --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/influencer/activate/content-amplifier .claude/skills/content-amplifier && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "content-amplifier" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/activate/content-amplifier into .claude/skills/content-amplifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-amplifier", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/activate/content-amplifierType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill content-amplifier -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills content-amplifier --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/influencer/activate/content-amplifier .agents/skills/content-amplifier && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-amplifier" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/activate/content-amplifier into .agents/skills/content-amplifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-amplifier", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill content-amplifier -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills content-amplifier --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/influencer/activate/content-amplifier .cursor/skills/content-amplifier && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-amplifier" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/activate/content-amplifier into .cursor/skills/content-amplifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-amplifier", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aaron-he-zhu/aaron-marketing-skills.git --path influencer/activate/content-amplifier--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill content-amplifier -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills content-amplifier --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/influencer/activate/content-amplifier .gemini/skills/content-amplifier && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-amplifier" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/activate/content-amplifier into .gemini/skills/content-amplifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-amplifier", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aaron-he-zhu/aaron-marketing-skills content-amplifierInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill content-amplifier -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/influencer/activate/content-amplifier .github/skills/content-amplifier && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-amplifier" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/activate/content-amplifier into .github/skills/content-amplifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-amplifier", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aaron-he-zhu/aaron-marketing-skills --skill content-amplifier -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aaron-he-zhu/aaron-marketing-skills content-amplifier --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/influencer/activate/content-amplifier .opencode/skills/content-amplifier && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-amplifier" agent skill from https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/influencer/activate/content-amplifier into .opencode/skills/content-amplifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-amplifier", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
content-amplifierA skill your agent uses 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…
Content Amplifier is an agent skill from aaron-he-zhu/aaron-marketing-skills. 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…
Its SKILL.md is about 6.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/atom-extraction.md` and `references/templates.md`). Compatibility notes: Claude Code and compatible agent-skill hosts
It sits in Marketing & SEO, covering Content repurposing, Influencer and creator marketing and Social media marketing. The repository describes itself as: 120 marketing skills as an AI marketing staff — plugin, portable skills, or an 8-bot team across 7 disciplines (narrative, SEO/GEO, social, email, paid, influencer, launch) on… The licence is Apache-2.0.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d5529cb. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Claude Code and compatible agent-skill hosts
From compatibility in the SKILL.md frontmatter.
Content Amplifier loads about 6.5k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 218 tokens; SKILL.md has 2,623 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from aaron-he-zhu/aaron-marketing-skills at commit d5529cb, republished under its Apache-2.0 licence (© aaron-he-zhu). 2,623 words, ~6,545 tokens.
.claude/skills/content-amplifier/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.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 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 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 frozen auditor-approved asset with current active paid rights should we amplify from [campaign]? # paid
How can we repurpose this frozen approved asset within its evidenced active destination scope? # repurposeCommon scenarios:
--mode paid: Create a $5,000 TikTok/Instagram plan from these frozen approved assets and supplied current active scoped-rights records
--mode repurpose: Build a 30-day plan from these 3 frozen approved videos and supplied current active rights records covering the requested destinationsOutput expectation — paid: every evidence-complete candidate scored, tiered, and given a spend that sums to budget, plus a scale/pause playbook. Any candidate missing organic-performance evidence or a Hook/Message/Quality/CTA observation remains NOT_SCORED/NEEDS_INPUT with no /25, 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.
creator_ref values plus transient creator locators, platform, content type, dated organic reach/engagement/views evidence, separate dated Hook/Message/Quality/CTA observations, amplification budget, campaign objective (awareness/traffic/conversions), target platforms, any prior performance data the user provides, and each candidate asset's current rights status/evidence plus existing placements when present.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/evidence, original performance metrics, target channels, and existing placements. For atomizing a source, the pasted transcript/caption/review text is transient evidence bound to that three-ref source identity; a raw handle or content URL never becomes source_ref.memory/hot-cache.md when memory-management is active.memory/influencer/content-amplifier/YYYY-MM-DD-<topic>.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-<UUIDv4> once for the lineage. Never persist a raw handle, creator name, profile/content URL, email, provider ID, or deterministic hash as identity. Keep only creator_ref, frozen asset/approval refs, opaque evidence/rights/contact/placement 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.memory/hot-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 proposal path with the exact status evidence. This skill does not append or accept that proposal.NOT_SCORED/NEEDS_INPUT with no total/rank/tier/spend; (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/pause rules is recorded, or those rules stay NEEDS_INPUT; (4) every selected asset has current active rights evidence covering the intended use.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.Emit the standard shape from skill-contract.md §Handoff Summary Format. State which mode ran. Label every metric Measured / User-provided / Calculated / Estimated / 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/NEEDS_INPUT. Organic performance and the Hook/Message/Quality/CTA observations are selection evidence, not forecast fields: if any is missing, do not substituteEstimated; set that asset toNOT_SCORED/NEEDS_INPUTand emit no/25, rank, tier, or spend. Use Estimated elsewhere only when the user supplied or approved the calculation inputs and assumptions, and show that basis.
This 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/engagement/views evidence or Hook/Message/Quality/CTA evidence is never Estimated; it makes that asset NOT_SCORED/NEEDS_INPUT. Other forecast fields may be Estimated only from supplied or explicitly approved inputs and assumptions; otherwise use Unknown/NEEDS_INPUT.
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); transiently resolve creator locators while retaining only creator_ref, platform, and contract-rights refs in saved repurpose artifacts.~~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.
creator_ref, platform/type, and dated organic reach/ER/views values with evidence refs. Do not create an organic-performance score from an absent, undated, or unevidenced metric. Paid Step 1 template.source_ref and observed_at. Only when all five are present may the asset receive /25, 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.NEEDS_INPUT and no hypothetical allocation. Paid Step 5 template.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/boost 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.Return 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.
status_observed_at, and status_evidence_ref. Repurpose Step 1 template.[campaign]_[creator_ref]_[platform]_[type]_[variation]_[date] naming convention, and metadata fields. Repurpose Step 6 structure.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.For slicing one source into many output atoms, apply the 7-tier extraction in references/atom-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/NEEDS_INPUT and do not auto-rank/drop/select them. Return the populated artifact inline; request one exact authorization for its WARM save and a separate authorization for any HOT promotion.
For 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.
NOT_SCORED/NEEDS_INPUT with no total/rank/tier/spend; (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/territory/format/use — 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.paid — User: "The dated organic export supplies views/ER 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."
Evidence basis: organic metrics, Hook observations, frozen approval refs, and rights status/scope are user-provided; Message, Quality, and CTA evidence is missing.
| Creator Ref | Organic | Hook | Message | Quality | CTA | Score State | Total / Rank / Spend |
|-------------|---------|------|---------|---------|-----|-------------|----------------------|
| [creator_ref per asset] | supplied | supplied | Unknown | Unknown | Unknown | `NOT_SCORED/NEEDS_INPUT` | none |
No `/25`, rank, tier, or allocation is emitted. Request dated Message/Quality/CTA observations with opaque evidence refs; never fill them with `Estimated` or force a partial total.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/evidence refs in the plan.
If 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/NEEDS_INPUT when organic metrics/evidence or any Hook/Message/Quality/CTA observation/evidence is missing.
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 inline, ask: "Save these results for future sessions?" If yes, obtain exact authorization for memory/influencer/content-amplifier/YYYY-MM-DD-<topic>.md and write the one-line verdict/headline, top 3-5 actionable items, open loops or blockers, and opaque source references. Saved identity is creator_ref only; remove raw handles, names, profile/content 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 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.
© aaron-he-zhu, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in influencer/activate/content-amplifier of aaron-he-zhu/aaron-marketing-skills.
Open the folder on GitHubat commit d5529cb
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in aaron-he-zhu/aaron-marketing-skills, which our catalogue first saw on October 7, 2026.
Content Amplifier next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Amplifier this skillaaron-he-zhu/aaron-marketing-skills | 2.9k | 1 repos | ~6.5k | Automated safety check: Pass | Apache-2.0 | |
| Socialcoreyhaines31/marketingskills | 54k | 4 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Suede VideoJasonColapietro/suede-creator-skills | 127 | — | ~4.1k | Automated safety check: Pass | MIT | |
| Getxapi ConnectLeoYeAI/openclaw-marketing-skills | 1k | 1 repos | ~715 | Automated safety check: Pass | Custom licence | |
| LinkedIn Ads Managementivangfalco/ads-skills | 279 | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Paid Ads Creativenowork-studio/notfair-plugin | 3.9k | — | ~248 | Automated safety check: Pass | MIT |
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
JasonColapietro/suede-creator-skills
Suede-owned marketing video planning and production discipline.
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
ivangfalco/ads-skills
Routes LinkedIn Ads work for B2B SaaS to the right playbook: campaign planning, performance analysis, account audits, creative, scaling and account-based campaigns.
nowork-studio/notfair-plugin
Create grounded paid-media creative concepts, copy angles, refresh hypotheses, and measurable test briefs across advertising platforms.
JasonColapietro/suede-creator-skills
Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes…
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix…
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"…
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "pick a bid strategy", "set a tCPA/tROAS target", or "plan the learning-phase entry"; produces a bid-strategy choice (tCPA / tROAS / max-conversions /…
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "QA my conversion tracking before launch", "check my UTMs / pixel / event firing", "set up a tracking pre-flight", or "set the dedup rule so Meta and…
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks "what did we pay this creator last time" or to "update the creator roster"; curates creator identity, rate, rights, exclusivity, compliance-event, and…
Categories
A skill your agent uses 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…. Content Amplifier is an agent skill from aaron-he-zhu/aaron-marketing-skills.
Content Amplifier fits situations like: the user asks to amplify influencer content with paid media; set up whitelisting; decide which posts to boost; repurpose influencer content.
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill content-amplifier -a claude-code`. Or copy the skill folder (influencer/activate/content-amplifier in aaron-he-zhu/aaron-marketing-skills) into .claude/skills/content-amplifier in your project. Claude Code loads it when a task matches its description.
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill content-amplifier -a codex`. Or copy the skill folder (influencer/activate/content-amplifier in aaron-he-zhu/aaron-marketing-skills) into .agents/skills/content-amplifier in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill content-amplifier -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-amplifier, .gemini/skills/content-amplifier, .github/skills/content-amplifier and .opencode/skills/content-amplifier in your project.
SKILL.md names no scripts, command-line tools or credentials: Content Amplifier is instructions for the agent only. Compatibility (from SKILL.md): Claude Code and compatible agent-skill hosts.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Content Amplifier is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.5k tokens (SKILL.md is roughly 26k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Content Amplifier: Social (coreyhaines31/marketingskills, 54k stars), Suede Video (JasonColapietro/suede-creator-skills, 127 stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars) and LinkedIn Ads Management (ivangfalco/ads-skills, 279 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
aaron-he-zhu (a GitHub user) maintains it in aaron-he-zhu/aaron-marketing-skills, which has 2,898 GitHub stars. The repository holds 119 skills in this directory. The repository was last updated on October 11, 2026.
Source: aaron-he-zhu/aaron-marketing-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.