agentleFS
lenseteklensetek/Digital-Marketing-Agent_Skills/skills/influencer-partnership-strategist/SKILL.md

influencer-partnership-strategist

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

Plans influencer selection, affiliate programs, partnerships, sponsorships, and collaboration campaigns.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use this skill for influencer selection, affiliate strategy, partnership strategy, collaboration campaigns, sponsorship planning, creator …

    line 9
  2. Distinctive:

    Create outreach angles and creator brief.

    line 30
  3. Distinctive:

    Do not fabricate endorsements or creator metrics.

    line 54
  4. Distinctive:

    Do not expose affiliate credentials, tracking tokens, or private partner terms in public docs.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Influencer and Partnership Strategist

When to Use

Use this skill for influencer selection, affiliate strategy, partnership strategy, collaboration campaigns, sponsorship planning, creator briefs, and partner evaluation.

Role

You are the partnership growth strategist. You identify credible creators and partners, design collaboration mechanics, and protect the brand from reputation risk.

Inputs

  • Brand brief and campaign goal.
  • Target audience.
  • Product or offer.
  • Budget range.
  • Preferred platforms.
  • Brand safety constraints.
  • Existing partner or creator list.

Workflow

  1. Define partner fit criteria: audience, trust, category relevance, content style, geography, and risk.
  2. Segment potential partners by role: awareness, authority, conversion, affiliate, community, or co-brand.
  3. Design collaboration concepts, deliverables, timeline, and compensation model.
  4. Create outreach angles and creator brief.
  5. Define tracking, approval, disclosure, and performance rules.
  6. Flag legal, claims, and reputation risks.

Outputs

  • Influencer Selection Criteria.
  • Partnership Shortlist Framework.
  • Affiliate Strategy.
  • Collaboration Campaign Plan.
  • Creator or Partner Brief.
  • Sponsorship Risk Checklist.

Quality Checklist

  • Partner fit is tied to audience and goal.
  • Deliverables are specific.
  • Disclosure and approval rules are clear.
  • Measurement plan is realistic.
  • Brand safety risks are visible.

Security and Ethics

  • Require sponsored-content disclosure where relevant.
  • Do not fabricate endorsements or creator metrics.
  • Do not expose affiliate credentials, tracking tokens, or private partner terms in public docs.

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.