agentleFS
Sign inStart free
jpeslar1jpeslar1/john-peslar-ai-skills/founder-content-engine/SKILL.md

founder-content-engine

Skill12 starsChanged 4 months agoMITView on GitHub

Turn founder expertise, notes, transcripts, calls, case studies, product work, or messy ideas into repeatable LinkedIn posts, newsletters, YouTube topics, and distribution systems. Use when building a founder brand, creating content pillars, repurposing long-form material, planning weekly content, writing founder-led posts, or turning business lessons into useful content. Trigger on "founder content", "LinkedIn posts", "newsletter", "YouTube ideas", "content engine", "repurpose this", "thought leadership", or "build my personal brand".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Use this skill to turn founder insight into content that builds trust, attracts buyers, and creates reusable distribution assets.

    line 12
  2. Very specific:

    Read references/content-system.md when creating a full content calendar or repurposing plan.

    line 14
  3. Distinctive:

    Write in a specific voice with concrete examples.

    line 36
  4. Distinctive:

    Add a soft CTA only when it fits.

    line 37
  5. Distinctive:

    Do not write generic thought leadership.

    line 71
  6. Distinctive:

    Prefer specific stories, numbers, and observations.

    line 72
  7. Distinctive:

    Use the founder's actual work as the content source.

    line 73
  8. Distinctive:

    Treat distribution as a system, not random posting.

    line 75

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

Founder Content Engine

Use this skill to turn founder insight into content that builds trust, attracts buyers, and creates reusable distribution assets.

Read references/content-system.md when creating a full content calendar or repurposing plan.

Core Principle

Founder content works when it teaches from earned insight. It should show what the founder sees, what they tried, what failed, what changed, and what the reader can do now.

Content Pillars

Use 3 to 5 pillars:

  • Proof - Case studies, screenshots, before-and-after, numbers, lessons.
  • Point of view - Beliefs, contrarian takes, market shifts, category POV.
  • Tactics - Templates, prompts, workflows, checklists, teardown steps.
  • Founder story - Mistakes, decisions, constraints, lessons, operating cadence.
  • Offer education - Problem awareness, mechanism, objections, buying criteria.

Workflow

  1. Extract raw material: notes, calls, product work, customer wins, failures, or research.
  2. Identify the lesson.
  3. Choose the content angle.
  4. Match the format to the point: post, thread, newsletter, video, carousel, or lead magnet.
  5. Write in a specific voice with concrete examples.
  6. Add a soft CTA only when it fits.
  7. Repurpose across channels.

Output Format

**Content Pillars**
1. ...
2. ...
3. ...

**This Week's Content**
| Day | Format | Topic | CTA |
|---|---|---|---|

**Posts**
1. [draft]
2. [draft]
3. [draft]

**Newsletter**
[outline]

**YouTube Ideas**
1. ...
2. ...
3. ...

**Repurposing Plan**
[how each asset becomes 3-5 more assets]

Rules

  • Do not write generic thought leadership.
  • Prefer specific stories, numbers, and observations.
  • Use the founder's actual work as the content source.
  • Make content useful even when there is no CTA.
  • Treat distribution as a system, not random posting.

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