agentsclimarketplace

Build in public engine

Skill lexthirteen-ai/founder-survival-kit/skills/build-in-public-engine

Claude skills for the hard parts of building, now that ai made the building easy

Install
npx -y skills add lexthirteen-ai/founder-survival-kit --skill build-in-public-engine

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turns the work a founder is already doing into honest, specific build-in-public content, so showing the work becomes how the audience and trust get built. Takes what you shipped, learned, or struggled with this week and drafts a small set of posts in your voice, without hype, ready to adapt per platform. Use when someone wants to build in public but does not know what to post, has work worth sharing but no time to write it up, or wants a repeatable weekly content habit from real work. Turns work into proof, it does not manufacture a brand.

SKILL.md

3.4 KB, as published. Nobody here has run it

Build In Public Engine

The audience and trust that make you hard to copy do not appear on their own. They get built by showing the work, honestly and specifically, week after week. This skill turns what you are already doing into that content, so growth is a byproduct of building rather than a separate chore.

When to use

  • You want to build in public but freeze on what to post.
  • You did real work this week that is worth sharing, and no time to write it up.
  • You want a repeatable weekly habit that turns building into an audience.

Process

  1. Harvest the week. Pull the raw material from what actually happened: what you shipped, what broke and how you fixed it, a decision you made and why, something you learned, a number that moved. Real specifics, not opinions about the industry.
  2. Pick the honest angles. Choose two or three moments worth a post. The best build-in-public content is specific and a little vulnerable: the bug that humbled you, the thing you got wrong, the small win with the real number. Skip the vague lessons.
  3. Draft in your voice, no hype. Write each as a short post that leads with the concrete moment, not a generic takeaway. If a line could sit on any homepage, rewrite it. If you have a voice guide, apply it; if not, sound like you explaining it to a smart friend.
  4. Adapt per platform. Shape each for where it goes: a longer reflective version for a professional feed, a tighter casual version for a fast feed, a hook plus thread where that fits. Same moment, right format, not copy-paste.
  5. Always leave a door open. End on a genuine question or an invitation to follow the build, so posts start conversations instead of broadcasting. That is where the audience actually forms.
  6. Make it weekly. Run this every week from real work. Consistency from honest material beats a viral one-off, and it compounds into the moat.

Output

  • Two or three drafted posts from this week's real work, in your voice, no hype.
  • Per-platform versions where useful.
  • Each ending on a question or a soft invitation.
  • A one-line note on the weekly cadence to keep.

Guardrails

  • Honest and specific, not performative. Share the real thing, including what went wrong. Manufactured founder-hero posts read as fake and erode the trust you are trying to build.
  • From real work only. This turns actual building into content. It does not invent milestones or dramatize nothing.
  • Value over promotion. Most posts should give something useful. Asks are rare and earned.
  • Your voice, no hype. No jargon, no inflated claims, no homepage language. Specifics beat ambition.

Related

This is how first-ten-users grows an audience and how the audience-and-trust moat in moat-finder actually gets built. Its raw angles can come from founder-pain-miner.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.