build-in-public
Skill8 starsChanged 3 months agoApache-2.0View on GitHub
Turns the user's recent GitHub activity into build-in-public posts through Stanley; use when the user wants to post about something they shipped, a specific PR or commit, or their recent coding work.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- nicolas-diez/personal-ostheir own version, first seen Nov 8, 2026
- iamcipherdev/cipher-linkedin-kittheir own version, first seen Nov 8, 2026
- alinaqi/claude-bootstraptheir own version, first seen Oct 8, 2026
- samber/developer-relations-skillstheir own version, first seen Sep 27, 2026
- davidvictor/build-in-publictheir own version, first seen Jun 29, 2026
- alinaqi/maggytheir own version, first seen Jun 12, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- alinaqi/maggy★ 711same name
- alinaqi/claude-bootstrap★ 708same name
- nicolas-diez/personal-os★ 4same name
- samber/developer-relations-skills★ 2same name
- davidvictor/build-in-public★ 1same name
- iamcipherdev/cipher-linkedin-kit★ 0same name
- Myra-Agents/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- site/llms.txtllms.txt
- repurposeSkill
- stanley-reviewSkill
- stanley-startSkill
- stanley-week-planSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
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
- Distinctive: line 12
Never publish live, delete posts, send DMs, or email a list through Stanley without the user's explicit approval in this conversation.
- Distinctive: line 17
Ask the user which repo (or all connected repos) and what lookback window, 1 to 30 days.
- Distinctive: line 21
Ask which platforms, then have Stanley draft: a single post for a small fix, a thread for a bigger ship.
- Very specific: line 24
If the user wants this on a schedule, point them to recipes/08-rituals.md instead of creating a ritual unasked.
“Common” is measured: kept by at least 6 in 10 of the 7 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.
Files
Build in public
Drive message_stanley to run this flow with the user. Stanley keeps conversation state across calls, so write to him in plain English and pass drafts back with their platform wrappers (<tweet>, <linkedin_post>, and so on) intact.
Hard rules:
- Never publish live, delete posts, send DMs, or email a list through Stanley without the user's explicit approval in this conversation. Scheduling drafts is allowed, since it can be undone.
- If you don't know what's connected, first send Stanley the audit prompt: list every connected platform and integration, flag anything expired or broken, and show the configured posting slots. GitHub must be on the list; if it isn't, stop and point the user at recipes/01-first-connection.md.
Steps:
- Ask the user which repo (or all connected repos) and what lookback window, 1 to 30 days. If they name a specific PR or commit instead, jump to step 4 with that target.
- Send Stanley the repo and window and ask for a shortlist of story-worthy changes: shipped features, gnarly bugs, decisions with tradeoffs. Tell him to skip dependency bumps and formatting churn.
- Show the user the shortlist as Stanley sent it and ask which item becomes a post. Draft nothing they haven't picked.
- Have Stanley read the actual diff for the picked item and pull one concrete, quotable detail. A draft that leans on the PR title alone goes back.
- Ask which platforms, then have Stanley draft: a single post for a small fix, a thread for a bigger ship. Show the user the draft, collect edits, and pass them back with the wrapper intact.
- Offer to schedule into the next open slot or leave it as a draft. Publish live only if the user says so in this conversation.
If the user wants this on a schedule, point them to recipes/08-rituals.md instead of creating a ritual unasked.
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
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.

