Use when the user asks to "track competitor influencer marketing", "see who my rivals partner with", or "benchmark my influencer program"; produces a competitor partnership roster, campaign and content-strategy breakdown, performance estimates, and a gap/opportunity list. Not for finding your own new creators — use influencer-discovery. 竞品达人合作追踪/竞品营销分析
68
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Monitor and analyze competitors' influencer marketing: who they partner with, what campaigns they run, how they structure collaborations, and what results they appear to achieve.
Shortest invocation:
Monitor [competitor name]'s influencer marketing activitiesCompare a set of rivals and surface gaps:
Compare influencer strategies across [competitor 1], [competitor 2], and [competitor 3], then show me which influencers they're missing in [category]creator_ref.memory/influencer/competitor-tracker/YYYY-MM-DD-<topic>.md only with exact WARM-save authorization.memory/hot-cache.md. Each competitor-partner or exclusivity update for a rostered creator requires another exact authorization for an operation: propose request through registry-events.py to memory/events/creators.ndjson; only creator-registry can reconcile it into canonical state.NEEDS_INPUT with a collection plan.Emit the standard shape from skill-contract.md §Handoff Summary Format.
Tier 1 can produce the tracking schema and exact collection/query plan. Named partners, campaigns, current activity, content patterns, and performance facts require dated user records, public-post evidence, or live connector results. Without them, return NEEDS_INPUT; do not reconstruct a roster or strategy from general knowledge. Estimates require an explicit formula and input refs and are never partnership facts.
Where a tool could speed things up, use ~~ connector placeholders:
~~influencer database — pull a competitor's known partner roster and tier mix.~~social platform analytics — estimate reach, engagement rate, and post cadence per creator.~~CRM — cross-check whether a former competitor partner has already touched your pipeline.Keyless news read on rivals: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/gdelt.py" '"<competitor>"' --days 30 lists index results with source URLs/dates. Label the retrieval Measured for the index query only; an article result does not verify a creator partnership or exclusivity until the underlying dated source explicitly supports it. See scripts/connectors/README.md.
Rival-partner channel watch (free key / keyless): python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/youtube.py" channel <partner-handle> reads a competitor partner's real subscriber/view counts (free YOUTUBE_API_KEY), and every YouTube channel also has a keyless RSS feed — https://www.youtube.com/feeds/videos.xml?channel_id=UC… piped into rss_monitor.py — for tracking partner posting cadence and spotting a burst of sponsored content without any API at all.
Label every estimate as an estimate. See CONNECTORS.md for the keyless/free recipe per category.
Each step has a fill-in template in references/templates.md.
creator_ref in all durable output; never infer exclusivity. (template)TBD/NEEDS_INPUT. (template)User: "Track the influencer marketing activities of Glossier, Fenty Beauty, and Rare Beauty"
Output: NEEDS_INPUT. The names alone do not evidence current partners or strategies. Return exact public-post/news/provider queries and required source/date/window fields; do not name partners, characterize strategy, estimate performance, or rank opportunities until dated evidence arrives. Full invocation patterns live in references/templates.md.
~~ connector category.Termination note: keep a visited-set of skills invoked this session. If the next skill has already run this session, stop and report the chain complete instead of re-invoking. Max chain depth is 3 hops.
888dd38
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.