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

distribution-plan

Skill43 starsChanged 4 months agoMITView on GitHub

Use when planning social, community, PR, founder-led content, newsletters, audience building, or recurring distribution between launches.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Create a repeatable plan for turning company activity into posts, newsletters, community updates, PR angles, and partner promotion.

    line 8
  2. Distinctive:

    If there is no source material, plan collection habits before a posting schedule.

    line 24

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

Distribution Plan

Create a repeatable plan for turning company activity into posts, newsletters, community updates, PR angles, and partner promotion.

Start With Source Material

Find what the team can repeatedly talk about:

  • Customer stories.
  • Product changes.
  • Founder opinions.
  • Data or benchmarks.
  • Behind-the-scenes decisions.
  • Competitive lessons.
  • Community questions.
  • Support patterns.
  • Partner or customer wins.

If there is no source material, plan collection habits before a posting schedule.

Choose Channels And Formats

Route source material by job:

  • Proof: customer result, product usage, revenue, benchmark, review.
  • Point of view: founder belief, market shift, mistake, refusal.
  • Education: workflow, teardown, checklist, answer to a repeated question.
  • Progress: ship note, changelog, behind-the-scenes decision.
  • Conversation: community question, comment thread, objection, trend.

Then choose surfaces by capacity and audience behavior. Do not schedule every channel. Pick the few the team can maintain.

Design The Cadence

Define recurring slots:

  • Weekly proof post.
  • Customer lesson.
  • Founder point of view.
  • Product progress.
  • Community answer.
  • Partner amplification.
  • Monthly narrative or report.

Each slot needs input source, owner, format, CTA, and reuse path.

Output

Distribution thesis:
[why this audience will keep paying attention]

Source routes:
| Source material | Route | Surface | Format | Owner | CTA |

This week:
1. [post/story]
2. [post/story]
3. [post/story]

Reuse map:
- [source] -> [formats]

Collection habits:
- [what to capture weekly]

Queue health:
- Starved source:
- Overused format:
- Channel at capacity:

Do not do:
- [channel or format to skip]

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.