agentleFS
Infinite-Labs-AIInfinite-Labs-AI/infinite-skills/skills/partnerships/SKILL.md

partnerships

Skill43 starsChanged 4 months agoMITView on GitHub

Use when finding or planning partner, referral, affiliate, creator, community, co-marketing, integration, marketplace, newsletter, podcast, or earned distribution channels.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    Do not design full referral, affiliate, PR, or community programs inside this skill.

    line 33

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Partnerships

Find partner channels that can introduce the product to the right audience with borrowed trust.

Map The Ecosystem

Identify:

  • Customer’s existing tools and communities.
  • Adjacent products that benefit when the user succeeds.
  • Experts, creators, consultants, agencies, newsletters, podcasts, and communities.
  • Marketplaces and integration ecosystems.
  • Referral or affiliate candidates.
  • Credibility sources: analysts, directories, review sites, open source projects.

Prioritize partners with audience overlap and a reason to care beyond commission.

Choose Partner Plays

For each partner class, state:

  • Why their audience would trust them on this problem.
  • Why the partner benefits from introducing the product.
  • What asset would make the introduction useful.
  • What conversion path captures the borrowed attention.
  • What would make the relationship asymmetric or not worth doing.

Do not design full referral, affiliate, PR, or community programs inside this skill. Route to the right partner motion and define the first test.

Outreach Strategy

Make the ask specific and low-friction:

  • Why this partner.
  • Why now.
  • What their audience gets.
  • What asset you will create.
  • What you need from them.
  • How success will be measured.

Output

Partner map:
| Partner type | Examples | Audience overlap | Value exchange | Priority |

Trust-transfer hypotheses:
1. Partner class:
   Why audience trusts them:
   Why partner cares:
   Asset:
   Conversion path:
   First test:

Outreach note:
Subject:
Body:

Operating risks:
- [risk] -> [mitigation]

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.