CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. 复用达人内容 / 内容放量.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-validated two-mode workflow with excellent progressive disclosure into a verified reference bundle. The one real weakness is redundancy: the rights/never-estimate policy is repeated across seven sections, inflating token cost without adding guidance.

Suggestions

State the evidence-gating rule (never estimate missing organic/Hook/Message/Quality/CTA evidence → NOT_SCORED/NEEDS_INPUT) once in Decision Gates or the Skill Contract, and have other sections reference it instead of restating it — the Output expectation, Data Sources, paid Step 2, Handoff Summary, and Example each repeat it nearly verbatim.

Consolidate the rights-status blocking rule (expired/revoked/disputed/unknown fails closed) into a single rights-verification section; it currently appears in the Scope guard, both Done-when lists, paid Step 7, repurpose Step 7, and both Decision Gates.

Trim cross-skill boundary prose (the momentum-planner/social-calendar-builder/social-creative-builder split is explained twice, in the Scope guard and again by reference in Reference Materials) to a single handoff note.

DimensionReasoningScore

Conciseness

The core never-estimate / rights-gating policy ("Missing … Hook/Message/Quality/CTA evidence is never Estimated; it makes that asset NOT_SCORED/NEEDS_INPUT") is restated nearly verbatim in the Output expectation, Skill Contract, Data Sources, paid Step 2, Decision Gates, the Example, and the Handoff Summary. The body assumes Claude's competence and explains no known concepts, but the repeated policy restatements across seven sections are more than the minor trimming of the 4 anchor — it genuinely needs consolidation into one stated rule.

3 / 5

Actionability

Both modes get numbered step sequences each bound to a named fill-in template, a concrete selection scheme (five 1–5 observations gating a /25 score), an exact library naming convention ("[campaign]_[creator_ref]_[platform]_[type]_[variation]_[date]"), explicit machine-readable statuses, and a worked example table covering the most common failure case. This is fully executable guidance for an instruction-only skill.

5 / 5

Workflow Clarity

Mode selection has keyword routing with a conflict rule ("run repurpose first to produce the assets, then hand to paid — do not silently merge"), steps are clearly sequenced, and validation is pervasive: evidence-completeness gating before any score/spend, "Done when" checklists per mode, Stop-and-ask / Continue-silently decision gates, rights verification before activation, and termination/visited-set rules.

5 / 5

Progressive Disclosure

The body is an overview that delegates each step's detail to verified one-level-deep references — references/templates.md (646 lines, headings match every anchor link cited in the body) and references/atom-extraction.md — plus clearly signaled family references (skill-contract.md, state-model.md, CONNECTORS.md, per-platform specs). Structure and navigation are easy to follow.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: explicit trigger phrases, a concrete per-mode inventory of outputs, and explicit disambiguation against adjacent skills. The only nitpick is density — it packs a lot into one field — but every clause is informative rather than padded.

DimensionReasoningScore

Specificity

The description enumerates concrete deliverables per mode — "a content-selection scorecard, a paid amplification strategy (whitelisting/boosting/dark posts), audience targeting, and a budget+optimization plan" plus "a rights-tracked content inventory, a 1-video-to-10+-asset repurposing map, per-format transformation specs, and a 30-day distribution plan" — comprehensive coverage of concrete actions with no real gaps.

5 / 5

Completeness

It opens with an explicit "Use when the user asks to…" clause with concrete trigger phrases and separately states what the skill produces for both modes, clearly and explicitly answering both what and when.

5 / 5

Trigger Term Quality

Six quoted natural user phrases ("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", "build a UGC asset library") plus bilingual terms give comprehensive coverage of how users would actually phrase the request; no natural synonym is meaningfully missing.

5 / 5

Distinctiveness Conflict Risk

Beyond a clear niche, it lists explicit negative boundaries naming the skills to use instead ("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…"), minimizing wrong-skill triggering.

5 / 5

Total

20

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing, 31 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

influencer/activate/content-amplifier/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.