Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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. 竞品达人合作追踪/竞品营销分析
.claude/skills/aaron-he-zhu-competitor-tracker/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-03 | ✗→✓ | ▲ Improved | 35% | 0% |
| case-01 | ✗→✓ | ▲ Improved | 49% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 55% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 86% | 0% |
| case-14 | ✗→✓ | ▲ Improved | 127% | 0% |
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.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-03 | fail→pass | 34,842 | 33,912 | -3% | 1 | 1 | 0% | 5,709 | 7,732 | +35% | 0 | 0 | — |
case-01 | fail→pass | 26,631 | 27,697 | +4% | 1 | 1 | 0% | 4,259 | 6,348 | +49% | 0 | 0 | — |
case-02 | fail→fail | 29,970 | 35,410 | +18% | 1 | 1 | 0% | 4,936 | 6,573 | +33% | 0 | 0 | — |
case-04 | fail→fail | 13,875 | 17,791 | +28% | 1 | 1 | 0% | 2,505 | 4,124 | +65% | 0 | 0 | — |
case-05 | fail→fail | 16,441 | 31,599 | +92% | 1 | 1 | 0% | 3,021 | 6,483 | +115% | 0 | 0 | — |
case-06 | fail→fail | 4,231 | 7,718 | +82% | 1 | 1 | 0% | 655 | 3,060 | +367% | 0 | 0 | — |
case-07 | fail→pass | 7,268 | 2,658 | -63% | 1 | 1 | 0% | 1,431 | 2,223 | +55% | 0 | 0 | — |
case-08 | fail→fail | 15,464 | 6,636 | -57% | 1 | 1 | 0% | 3,127 | 2,767 | -12% | 0 | 0 | — |
case-09 | pass→pass | 13,743 | 8,840 | -36% | 1 | 1 | 0% | 2,079 | 3,198 | +54% | 0 | 0 | — |
case-10 | fail→pass | 9,306 | 5,909 | -37% | 1 | 1 | 0% | 1,568 | 2,918 | +86% | 0 | 0 | — |
case-11 | pass→fail | 5,443 | 2,090 | -62% | 1 | 1 | 0% | 825 | 2,131 | +158% | 0 | 0 | — |
case-12 | pass→pass | 13,083 | 4,863 | -63% | 1 | 1 | 0% | 2,276 | 2,682 | +18% | 0 | 0 | — |
case-13 | fail→fail | 10,079 | 4,626 | -54% | 1 | 1 | 0% | 1,697 | 2,633 | +55% | 0 | 0 | — |
case-14 | fail→pass | 6,458 | 2,805 | -57% | 1 | 1 | 0% | 946 | 2,145 | +127% | 0 | 0 | — |
case-15 | fail→fail | 11,780 | 3,799 | -68% | 1 | 1 | 0% | 2,010 | 2,342 | +17% | 0 | 0 | — |
case-16 | fail→fail | 8,391 | 2,364 | -72% | 1 | 1 | 0% | 1,441 | 2,242 | +56% | 0 | 0 | — |
case-17 | fail→pass | 11,119 | 4,381 | -61% | 1 | 1 | 0% | 1,788 | 2,505 | +40% | 0 | 0 | — |
case-18 | pass→pass | 10,410 | 5,358 | -49% | 1 | 1 | 0% | 1,724 | 2,623 | +52% | 0 | 0 | — |
case-19 | pass→pass | 15,833 | 13,296 | -16% | 1 | 1 | 0% | 2,511 | 3,869 | +54% | 0 | 0 | — |
case-20 | fail→pass | 11,537 | 2,141 | -81% | 1 | 1 | 0% | 2,036 | 2,087 | +3% | 0 | 0 | — |
case-21 | pass→pass | 7,709 | 3,872 | -50% | 1 | 1 | 0% | 1,241 | 2,345 | +89% | 0 | 0 | — |
case-22 | fail→pass | 2,442 | 3,081 | +26% | 1 | 1 | 0% | 312 | 2,260 | +624% | 0 | 0 | — |
case-23 | fail→pass | 8,043 | 3,524 | -56% | 1 | 1 | 0% | 1,231 | 2,296 | +87% | 0 | 0 | — |
case-24 | fail→pass | 9,389 | 2,215 | -76% | 1 | 1 | 0% | 1,469 | 2,112 | +44% | 0 | 0 | — |
case-25 | fail→pass | 11,339 | 3,976 | -65% | 1 | 1 | 0% | 1,745 | 2,314 | +33% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 25 cases were attempted. The headline lift of +40 percentage points is the difference between those two pass rates over the 25 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
The publisher has shipped newer versions since this run, so these numbers describe v1, not the version currently listed.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.