creator-outreach
Skill417 starsChanged 3 months agoMITView on GitHub
Use when a specific creator has been selected and you need a concise, personal, permission-respecting first contact about a relevant collaboration. Trigger phrases include "write outreach to this creator", "contact these partners", "make a creator pitch", "how should I ask this creator?", and "follow up on this collaboration". Do not use this for mass cold outreach, automated DMs, undisclosed affiliate offers, or creator selection; use influencer-partnerships to assess fit and campaign-brief to establish the offer first.
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
- cross-platform-distributionSkill
- cross-platform-reformatterSkill
- cta-writerSkill
- dm-script-writerSkill
- going-viralSkill
- hashtag-keyword-researchSkill
- hook-miningSkill
- humanizerSkill
- influencer-partnershipsSkill
- 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
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 8
Write outreach that proves the operator has done the work: it is relevant to the creator, clear about the ask, and easy to decline.
- Distinctive: line 16
Use a specific, recent piece of work or audience need that the operator can accurately name.
- Distinctive: line 28
Never automate unsolicited replies, DMs, or follow-ups.
- Distinctive: line 29
Do not misrepresent the sender, relationship, compensation, product access, or urgency.
- Distinctive: line 30
Use only appropriate contact details supplied for business contact or already approved by the operator.
- Distinctive: line 31
Do not promise results, creative approval, or payment terms that are not authorised.
- Distinctive: line 45
Use influencer-partnerships to decide whether and how to approach a creator.
≈ “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
Creator Outreach
Write outreach that proves the operator has done the work: it is relevant to the creator, clear about the ask, and easy to decline.
1. Confirm permission and fit
Record the creator's supplied or public business contact route, the reason the collaboration is relevant, the approved offer, and the required disclosure or compensation terms. Do not contact a creator merely because they are in a large list. If the relationship is not mutually useful, stop before drafting.
2. Find one honest personalisation point
Use a specific, recent piece of work or audience need that the operator can accurately name. Explain the connection in one sentence without flattery theatre or invented familiarity. Never imply that the creator uses the product, knows the team, or endorsed anything.
3. Make the ask inspectable
State what the collaboration could involve, the creative latitude, compensation or consideration where approved, timeline, disclosure expectation, and the smallest next step. Link only to material the creator needs to evaluate the proposal. Make a no-pressure decline simple.
4. Follow up with restraint
Record the outreach date and one reasonable follow-up point. If there is no response, do not escalate through other personal channels, pressure the creator, or treat silence as consent. Update the partnership record with a factual outcome so future outreach does not repeat unwanted contact.
Hard rules
- Never automate unsolicited replies, DMs, or follow-ups.
- Do not misrepresent the sender, relationship, compensation, product access, or urgency.
- Use only appropriate contact details supplied for business contact or already approved by the operator.
- Do not promise results, creative approval, or payment terms that are not authorised.
- Include required sponsorship, gifted, affiliate, or material-connection disclosures in the later brief, not as a hidden condition.
Failure modes
| Failure | Do this instead |
| The message could be sent to anyone | Add one verifiable relevance point or do not send it. |
| The ask hides the commercial terms | State the available terms clearly or say they are still being scoped. |
| Follow-up becomes harassment | Set one follow-up and close the record after no response. |
| Outreach starts before partnership fit | Return to influencer-partnerships and evaluate the collaboration first. |
Where it sits
Use influencer-partnerships to decide whether and how to approach a creator. Use campaign-brief for the approved campaign facts and utm-campaign-plan for any attributable link. Use launch-retrospective to learn from completed collaborations, never from private creator data outside the agreed purpose.
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.