agentleFS
scrollmarkscrollmark/social-skills/skills/platform-fluency/SKILL.md

platform-fluency

Skill19 starsChanged 29 days agoMITView on GitHub

Use when you need to understand platform-specific conventions, algorithm behavior, content formats, or audience expectations for Instagram, TikTok, YouTube, X, or LinkedIn.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search + recommended (YouTube) — intent-driven.

    line 17
  2. Very specific:

    If the conversation involves a specific platform, load references/platforms/{platform}.md from this skill's own directory.

    line 33
  3. Distinctive:

    Every platform's audience can detect cross-posted content.

    line 37
  4. Distinctive:

    If the reference can't be loaded, work with the mental model above and be upfront about the limitation.

    line 50

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

Platform Fluency

This skill is a router. The deep platform knowledge lives in the reference files — this skill tells you when and how to use them.

Cross-Platform Mental Model

Platforms differ on three axes. Knowing where a platform sits on each one shapes every recommendation.

Discovery mechanism:

  • Content-graph (TikTok) — the algorithm shows content based on what it is, not who made it. Follower count barely matters.
  • Follower-graph (Instagram, LinkedIn) — your existing audience sees your content first. Reach beyond that depends on engagement signals.
  • Search + recommended (YouTube) — intent-driven. People find content through search, suggestions, and browse. Evergreen content has a long tail.
  • Conversation-graph (X) — content spreads through replies, quotes, and reposts. Real-time relevance matters most.

Content lifespan:

  • Ephemeral: Stories (24h), X posts (hours of relevance), TikTok (days to weeks)
  • Medium: Instagram Reels/feed (weeks), LinkedIn posts (days to a week)
  • Evergreen: YouTube long-form (months to years), YouTube Shorts (weeks)

Audience intent:

  • Passive scroll (TikTok, Instagram) — entertainment-seeking, low commitment per piece
  • Active search (YouTube, increasingly TikTok) — looking for something specific
  • Professional context (LinkedIn) — career-relevant, during work hours
  • Conversation (X) — wants to engage, react, discuss

When to Load References

If the conversation involves a specific platform, load references/platforms/{platform}.md from this skill's own directory. If comparing platforms or adapting content across them, load both.

Native vs. Cross-Posted

Every platform's audience can detect cross-posted content. Dead giveaways:

  • Wrong aspect ratio or resolution
  • Watermarks from other platforms (especially TikTok logo on Reels)
  • Caption style that belongs elsewhere (hashtag walls on LinkedIn, professional tone on TikTok)
  • Timing and pacing that feels off for the platform

Native content consistently outperforms cross-posted content. When in doubt, adapt.

Algorithm Guidance

Don't give specific algorithm advice without loading the relevant platform reference — algorithms change frequently. Provide the framework (what signals matter, how distribution works) rather than specific numbers. If the reference's last_updated date is more than 6 months old, note that algorithmic details may have shifted.

If the reference can't be loaded, work with the mental model above and be upfront about the limitation.

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.