apify-influencer-brand-collabs
Skill293 starsChanged 8 days agoApache-2.0View on GitHub
Discover Instagram brand–creator partnerships by chaining Apify Actors. Use when the user asks who collabs with a brand, which brands a creator has done paid posts for, wants to audit an influencer's branded-content history, or wants to scope a brand's sponsorship roster.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- calven-ai/marketing-as-codetheir own version, first seen Oct 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- calven-ai/marketing-as-code★ 10same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- apify-ads-intelligenceSkill
- apify-ai-search-visibility-trackerSkill
- apify-app-store-intelligenceSkill
- apify-ashby-jobs-scraperSkill
- apify-blocked-scrape-triageSkill
- apify-booking-host-leadsSkill
- apify-buying-signal-detectionSkill
- apify-company-data-apiSkill
- apify-creator-emailsSkill
- apify-easy-competitive-intelligenceSkill
- apify-ecommerceSkill
- apify-google-maps-leadsSkill
- apify-instagram-niche-mapperSkill
- apify-job-boardsSkill
- apify-jobs-dataSkill
- apify-lead-scoring-enrichmentSkill
- apify-link-prospecting-outreachSkill
- apify-local-business-leads-osmSkill
- apify-marketing-agency-databaseSkill
- apify-orchestrator-actor-developmentSkill
- apify-osint-threat-intelSkill
- apify-plan-travelSkill
- apify-product-data-setupSkill
- apify-reddit-scraperSkill
- apify-verified-email-finderSkill
- apify-x402-agentic-walletSkill
- apify-yandex-image-search-apiSkill
- apify-yandex-search-apiSkill
- _templateSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 57
Call each via mcp__claude_ai_Apify__call-actor.
- Distinctive: line 116
Run the two scrapers in parallel — they're independent.
- Distinctive: line 127
Only enrich the side the user actually cares about.
- Distinctive: line 177
If the user just needs a partner list, skip both toggles.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Influencer–Brand Collaborations
Surface Instagram branded-content partnerships by chaining four Apify Actors against Meta's Ad
Library. Distilled from the production influencer-brand-collabs mini-tool.
When to use
- "Who has Nike paid to promote them this quarter?"
- "What brands does @bellahadid do sponsored posts for?"
- Auditing an account's branded-content history
- Building a competitor's influencer roster
Don't use for: organic mentions or tags (use a hashtag/mentions scraper), TikTok or YouTube collabs (different platforms), generic competitor ads (query Meta Ad Library directly).
Inputs to gather
- Instagram handle or URL —
@adidasorhttps://www.instagram.com/adidas/ - Lookback window — days; default 90
- Enrichment toggles (each adds cost + time):
- Content insights — likes, comments, views per collab
- Profile enrichment — followers, bio, verified status of the other side
Direction (brand vs creator) is detected empirically. Do not ask.
The pipeline
| # | Actor | Purpose | Required |
| 1 | apify/instagram-profile-scraper | Resolve the target's Facebook fbid | ✓ |
| 2 | apify/brand-collaboration-scraper | Pull branded-content posts from Meta's Ad Library | ✓ |
| 3 | apify/instagram-post-scraper + apify/instagram-reel-scraper | Engagement metrics | optional |
| 4 | apify/instagram-profile-scraper (again) | Enrich the result-side partners | optional |
Call each via mcp__claude_ai_Apify__call-actor. Use mcp__claude_ai_Apify__fetch-actor-details
first if you've never run one of these and want the exact input schema.
Step 1 — Resolve the target
// actor: apify/instagram-profile-scraper
{ "usernames": ["adidas"] }Grab fbid from the first item. No fbid → can't query Ad Library → stop and tell the user.
Most common cause: private account.
Step 2 — Build the Meta Ad Library URL
https://www.facebook.com/ads/library/branded_content/?id={fbid}&query={username}&target=instagram&start_date={YYYY-MM-DD}&end_date={YYYY-MM-DD}Date range = the lookback window (default 90 days, ending today).
Step 3 — Fetch collaborations
// actor: apify/brand-collaboration-scraper
{ "startUrls": ["<ad library url>"], "resultsLimit": 10 }Schema is fixed: every item has creator (always the influencer side) and brandPartners[0]
(always the brand side). Do not try to infer direction from these fields.
Step 4 — Detect direction empirically
Count how often the target username appears on each side of the results:
- target appears more on
creatorside → target is the influencer; results are the brands - target appears more on
brandPartnersside → target is the brand; results are the creators
⚠️ Do not use
isBusinessAccountto infer this. It's unreliable — e.g.@fifaworldcupis a business account but appears as the creator of its own branded content.
Step 5 — (optional) Content metrics
Split collab URLs by type:
/reel/...→ reel scraper/p/...or/tv/...→ post scraper
// actor: apify/instagram-post-scraper
{ "username": ["<post urls>"], "resultsLimit": 1, "dataDetailLevel": "basicData" }
// actor: apify/instagram-reel-scraper
{ "username": ["<reel urls>"], "resultsLimit": 1 }Match back to collabs via shortcode in the URL: /(p|reel|tv)/([A-Za-z0-9_-]+).
Engagement formula: likesCount + commentsCount + (videoViewCount ?? videoPlayCount ?? 0).
Run the two scrapers in parallel — they're independent.
Step 6 — (optional) Enrich the result side
Collect unique usernames from the side that is not the target. Then:
// actor: apify/instagram-profile-scraper
{ "usernames": [<unique result-side usernames>] }Only enrich the side the user actually cares about. The input handle is already known.
What to present
After aggregation, surface:
- Headline counts: total collabs, unique partners, total engagement (if metrics enriched)
- Top 5 collabs by engagement — only meaningful when content insights were toggled on
- Content-type mix: Post vs Reel; Reels usually dominate engagement
- Weekly timeline across the date range — spikes reveal campaign launches
- Per-partner card (when profiles enriched): handle, full name, followers, verified, category, collabs in this run, avg engagement
For who-questions, the partner list alone is enough. Metrics only matter for which-was-best-questions.
URL parsing
Strip Instagram's _u/ and _n/ deep-link prefixes before extracting the handle:
/instagram\.com\/(?:_u\/|_n\/)?([A-Za-z0-9_.]+)/iThese slugs are not usernames — skip them:
explore, reels, stories, direct, accounts, about, p, reel, tv, tags,
locations, _u, _n.
Pitfalls
- Target is private → profile scraper returns no
fbid. Bail early with a clear message. - No results → try in order: widen the date range, double-check the handle (strip
_u/), confirm the account actually runs branded content. Meta only indexes ads they've classified as branded content. - Engagement is all zeros → user skipped content enrichment. Offer to re-run with it on.
- Direction looks wrong in the output → re-check the empirical count. Don't trust
isBusinessAccount. - Brand collabs with no metrics are still answer-shaped for who questions — don't gate the whole flow on enrichment.
Cost & time
Full 4-actor run: ~3–5 minutes, a few cents of Apify compute. Order of magnitude:
| Enrichment | Actors run | Approx time |
| None | 2 | 1–2 min |
| + Content | 3–4 | 2–4 min |
| + Profiles | +1 | +30–60 s |
If the user just needs a partner list, skip both toggles.
Reference implementation
Production route this skill was distilled from:
mini-tools-main/src/app/api/tools/influencer-brand-collabs/route.ts — full transformation logic,
error handling, and slimmed display shapes for each scraper's output.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

