agentleFS
tang-vutang-vu/social-posting-skills/.agents/skills/post-indiehackers/SKILL.md

post-indiehackers

Skill9 starsChanged 2 months agoMITView on GitHub

Adapt and publish campaign items on IndieHackers — transparent milestones for the founder/maker community

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify the group/post flow still matches expectations before trusting any older automation notes — the platform drifts.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

IndieHackers Adapter

Facts live in platforms/indiehackers.json — status is degraded: the community has cooled since acquisition and the product changes without notice. Draft export is the reliable path.

What IH rewards (culture)

  • Transparency with real numbers: revenue, users, timelines, churn.
  • "What worked / what didn't" breakdowns — the community trades tactics.
  • Maker-voiced honesty over startup-investor polish.

Drafting from the content graph

  • core-claim → milestone title with the real number in it.
  • proof → the metrics and details — this is where IH lives.
  • technical/context → how you got there; specifics beat story arcs.
  • cta → "ask me anything" — the community answers questions with care.
  • Posts are filed under topic groups: the draft names the target group and the user confirms fit.

Publishing

  • manual only — posting flow and bot detection shift without notice.
  • No public API.

Genuine engagement

  • Answer every question on your post; IH rewards presence.
  • Share numbers because they help others, not because they impress.

Pitfalls

  • Verify the group/post flow still matches expectations before trusting any older automation notes — the platform drifts.

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.