influencer-partnerships
Skill417 starsChanged 3 months agoMITView on GitHub
Use when you need to decide whether a creator partnership is appropriate and prepare a truthful, mutually useful collaboration brief. Trigger phrases include "should we work with this creator?", "evaluate these influencers", "make a creator partnership brief", "how do we structure this collaboration?", and "what should a partner post?". Do not use this to buy followers, conceal sponsorship, automate outreach, or invent a creator's audience fit; use creator-outreach for personalised contact and campaign-brief for the underlying campaign.
In this repository54 other files it gives its agents.
- ab-hook-testerSkill
- agent-reachSkill
- ai-brainSkill
- analytics-readoutSkill
- audience-personasSkill
- best-time-schedulerSkill
- bio-profile-optimizerSkill
- b-roll-shot-listSkill
- campaign-briefSkill
- caption-and-hashtagsSkill
- carousel-builderSkill
- collab-outreachSkill
- comment-miningSkill
- comment-responderSkill
- community-engagement-planSkill
- competitor-positioningSkill
- competitor-teardownSkill
- content-auditSkill
- content-calendarSkill
- content-factorySkill
- content-pillar-builderSkill
- content-repurposerSkill
- content-researchSkill
- cover-thumbnail-briefSkill
- creator-outreachSkill
- cross-platform-distributionSkill
- cross-platform-reformatterSkill
- cta-writerSkill
- dm-script-writerSkill
- going-viralSkill
- hashtag-keyword-researchSkill
- hook-miningSkill
- humanizerSkill
- launch-retrospectiveSkill
- linkedin-thought-leadershipSkill
- on-screen-text-writerSkill
- paid-social-briefSkill
- positioning-auditSkill
- profile-conversion-auditSkill
- reel-analyzerSkill
- reel-builderSkill
- reel-scripterSkill
- series-plannerSkill
- social-analytics-reportSkill
- social-listeningSkill
- social-proof-miningSkill
- story-sequencerSkill
- trend-spotterSkill
- ugc-creator-briefSkill
- utm-campaign-planSkill
- viral-carouselSkill
- viral-hook-writerSkill
- viralitySkill
- x-thread-strategySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Start with the campaign objective, audience situation, approved offer, proof, budget or compensation constraints, timing, and the role a …
- Distinctive: line 28
Never conceal paid, gifted, affiliate, or other material relationships.
- Distinctive: line 29
Do not claim audience demographics, reach, or conversion without supplied evidence.
- Distinctive: line 30
Do not require a creator to make unsupported product or performance claims.
- Distinctive: line 32
Never pressure creators or their audiences into unsolicited contact or deceptive engagement.
- Distinctive: line 45
Use campaign-brief before this skill.
≈ “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 Partnerships
Evaluate and structure creator collaborations around real audience fit, transparent terms, and claims both sides can defend.
1. Define the partnership job
Start with the campaign objective, audience situation, approved offer, proof, budget or compensation constraints, timing, and the role a creator could credibly play. A creator is not automatically a distribution channel; state what their audience gains from the collaboration.
2. Assess fit from supplied evidence
Review only evidence provided or publicly verified by the operator: recent work, audience conversation quality, topic relevance, format strength, brand conflicts, and disclosure norms. Separate observable fit from assumptions. If audience data is unavailable, record that as an uncertainty rather than inventing a reach forecast.
3. Build a creator-respecting brief
Share the non-negotiable facts, claim boundaries, required disclosures, deliverables, timing, rights, review process, compensation terms, and a clear creative latitude zone. Explain the audience problem to solve, not a script to recite. Identify what the creator must not imply.
4. Agree on measurement and learning
Define what success means, the approved tracking method, the reporting window, and who owns follow-up. Review work against the agreed brief, not taste alone. Capture learning about fit, message, and format for future partnerships without ranking creators by a single vanity metric.
Hard rules
- Never conceal paid, gifted, affiliate, or other material relationships; follow applicable disclosure requirements.
- Do not claim audience demographics, reach, or conversion without supplied evidence.
- Do not require a creator to make unsupported product or performance claims.
- Respect creator terms, usage rights, exclusivity, and consent before reusing material.
- Never pressure creators or their audiences into unsolicited contact or deceptive engagement.
Failure modes
| Failure | Do this instead |
| Selection is based only on follower count | Evaluate topical fit, audience conversation, format, and evidence quality. |
| The brief removes the creator's voice | State truth boundaries and desired outcome, then leave creative room. |
| A partnership is treated as a guaranteed sales channel | Define a test and learning goal, not an invented return. |
| Disclosure is an afterthought | Put required disclosure and approval expectations in the brief from the start. |
Where it sits
Use campaign-brief before this skill. Use creator-outreach to contact a selected creator with a relevant, personalised note. Use social-proof-mining for approved proof and utm-campaign-plan for attributable links. Use launch-retrospective to decide what to repeat.
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.

