agentleFS
Sign inStart free
aryaminusaryaminus/socials-assistant/skills/media-kit/SKILL.md

media-kit

Skill0 starsChanged 3 months agoMITView on GitHub

Generates or refreshes a creator's media kit (one-page brand deck) from live verified vault analytics. Use when the user asks for a media kit, press kit, brand deck, rate sheet backup, or wants updated numbers before pitching brands.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. augchan42/inkstone★ 5same 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 repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call socials-mcp:profile_get — name, niche positioning, past_collaborations feed the header and case-study sections (ask the user to fill …

    line 13
  2. Very specific:

    Call socials-mcp:media_kit_data — followers, 30-day views, avg engagement, top videos, audience highlights per platform.

    line 14
  3. Very specific:

    If data is thin (no 30-day views, missing platforms), prompt the user to run socials-mcp:snapshot and (TikTok) …

    line 15
  4. Distinctive:

    Every metric carries its window ("last 30 days").

    line 26

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

media-kit — verified numbers, auto-refreshed

The media kit is the creator's business card. Generate it from the vault so every number is real and current. Never estimate; never use stale screenshots.

Steps

  1. Call socials-mcp:profile_get — name, niche positioning, past_collaborations feed the header and case-study sections (ask the user to fill gaps; never invent brand names).
  2. Call socials-mcp:media_kit_data — followers, 30-day views, avg engagement, top videos, audience highlights per platform.
  3. If data is thin (no 30-day views, missing platforms), prompt the user to run socials-mcp:snapshot and (TikTok) socials-mcp:import_tiktok_csv first.
  4. Generate media-kit.md from the template in assets/media-kit-template.md.
  5. Fill "Past collaborations" from socials-mcp:outreach_log_list plus anything the user recalls — ask, don't invent.
  6. Export options: leave as markdown, render to PDF, or publish as a live link (GitHub page / Notion) — a live link is preferred for cold emails.

Refresh cadence

Re-run after every weekly snapshot. Numbers older than ~10 days in a media kit are how creators get lowballed.

Rules

  • Every metric carries its window ("last 30 days").
  • Omit platforms with meaningless data rather than showing zeros.
  • Audience section: top 3 facts maximum — brands skim.

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.

Check your setup, free