agentleFS
whawkinsivwhawkinsiv/claude-code-skills/skills/content/SKILL.md

content

Skill258 starsChanged 28 days agoMITView on GitHub

Use this skill when the founder wants to write and publish in their own voice to attract customers: 'content strategy,' 'build in public,' 'write a blog post,' 'founder essay,' 'LinkedIn post,' 'Twitter thread,' 'newsletter,' 'About page,' 'which platform should I post on,' or 'grow an audience.' Picks one platform, finds an angle worth publishing, and writes and edits the piece. Not for search-driven pages (use seo), for sales pages (use landing-page), or for cleaning up existing AI text (use humanize).

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use accounts, data and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MGrinSkill

    accounts

    Read custom Claude and Codex subscription telemetry, switch captured Claude/Codex accounts, or see which accounts mgrin has paused in the accounts plugin.

    Also in 3 projects that use this

  • launch52-aiSkill

    data

    Generate data layer code (Freezed DTOs, repository implementations, data sources) from feature specifications or API references. Creates the bridge between domain entities and external data sources. Use after /domain to implement the data layer.

    Also in 3 projects that use this

  • seikaikyoSkill

    brand

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

    Also in 3 projects that use this

  • 0xSeroSkill

    security

    Also in 4 projects that use this

  • NVIDIASkill

    github

    Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 10

    Distinctive

    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:

    Read ABOUT-ME.md first. If it does not exist and the piece must sound like the founder, suggest about-me.

    line 12
  2. Distinctive:

    Keep about 80% of the posts useful on their own and 20% about the product.

    line 29
  3. Distinctive:

    Before writing, state two things:

    line 33
  4. Distinctive:

    Why this piece should exist: when others already cover the topic: original data, first-person experience, a contrarian view backed by …

    line 35
  5. Distinctive:

    If you cannot state both, do not write the piece.

    line 37
  6. Distinctive:

    Draft fast, in the founder's voice: Do not edit while drafting.

    line 43
  7. Distinctive:

    End on the strongest line: No recap, no "in conclusion." Move the best line to the end and cut whatever came after it.

    line 59
  8. Distinctive:

    Keep a schedule the founder can hold for 3 months, such as three short posts a week, or one long piece.

    line 67
  9. Distinctive:

    Use real numbers and real stories only: Never invent a metric, a customer, or an experience.

    line 71
  10. Distinctive:

    Measure sign-ups and customers from content,: not likes. Ask new customers "How did you find us?"

    line 72

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “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

Content

For a solo founder, content is the marketing department. The goal is customers, not followers. Publish what only this founder can write, on one platform, for long enough to work.

Read ABOUT-ME.md first. If it does not exist and the piece must sound like the founder, suggest about-me.

Step 1: Pick one platform

Go where the customers already talk about the problem. Search the problem's keywords on each likely platform (LinkedIn, X, Reddit, YouTube, a niche forum, a newsletter). The one with the most active discussion wins.

One platform, done well, for 3 months before judging. A weak presence on five platforms loses to a strong presence on one.

Step 2: Choose what to write about

Building in public is the cheapest way for a solo founder to earn trust. Use these topics:

  • Progress: what shipped, and the real numbers.
  • Decisions: "A customer asked for X. I said no. Here's why."
  • Failures: what went wrong, and what changed. These get the most engagement.
  • How it was built: the approach, with specifics.
  • The problem itself: something useful to the reader even if the product did not exist.

Keep about 80% of the posts useful on their own and 20% about the product.

Step 3: Pass the angle gate

Before writing, state two things:

  1. The one takeaway, in one sentence.
  2. Why this piece should exist when others already cover the topic: original data, first-person experience, a contrarian view backed by reasons, or a specific audience nobody else writes for.

If you cannot state both, do not write the piece. It would be one more article that nobody needs.

Step 4: Write

  1. Write the opening line first: a specific moment, claim, or number. Not a definition, a question, or "Imagine if." Rewrite it until it is specific.
  2. Outline 3–5 beats in plain words, as what each part does.
  3. Draft fast, in the founder's voice. Do not edit while drafting.
FormatLengthShape
Social post50–300 wordsThe specific thing → why it matters → one takeaway
Build-in-public update200–500 wordsThe number or shipped thing → what was hard → what changed in the founder's view
Blog post800–1,500 wordsHook → the one claim → 2–4 beats, each with a real example → end on the strongest line
Founder essay1,500–3,000 wordsPersonal stake → the tension → working through it → where the founder has landed, open questions allowed
About page300–600 wordsThe problem the founder ran into → why existing options failed them → what they built → who it is for, by name
Newsletter intro100–250 wordsThe one thing on the founder's mind → a light pointer to what is below → one invitation

Step 5: Edit

Three edits catch most problems:

  1. Delete the throat-clearing first paragraph. The piece usually starts on what was the second paragraph.
  2. Replace every "this highlights / underscores / demonstrates" with the specific thing it points at.
  3. End on the strongest line. No recap, no "in conclusion." Move the best line to the end and cut whatever came after it.

Then run humanize on the draft.

Step 6: Publish and point

  • Link to a specific page that matches the post, not the homepage.
  • Adapt one good piece across formats. A blog post becomes a thread, a post, and a newsletter section. Rewrite each one for its platform.
  • Keep a schedule the founder can hold for 3 months, such as three short posts a week, or one long piece. Write in batches.

Rules

  • Use real numbers and real stories only. Never invent a metric, a customer, or an experience.
  • Measure sign-ups and customers from content, not likes. Ask new customers "How did you find us?"
  • Never post an AI draft the founder has not shaped with their own experience. Readers notice.
  • Skip "Excited to announce," vague teasers, and complaints about competitors.

Output

The platform choice and the reason for it, the takeaway and angle for each piece, and the finished pieces ready to post, each with its link.

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.