Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →alinaqi/build-in-public-best-practices
Build in public isn't marketing. It's letting people watch you work. The best posts feel like you're narrating your thought process to a friend who's also a senior engineer. No hype sludge. No "I'm excited to announce." Just: here's what I built, here's why it matters, here's what I learned.
Passed 16 of 24 test cases with the skill, and 13 of 24 without it.
and 5 more in the full report
5 fixed11 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
An automated event 'on_review_passed' occurred with 3/3 unanimous approvals for a new custom memory allocator implementation. Specify which platform to target.
| Checked | Without skill | With skill |
|---|---|---|
| Targets X only for publishing this architectural update | Missed | Passed |
The instructions your model reads when the skill loads.
Build in public isn't marketing. It's letting people watch you work. The best posts feel like you're narrating your thought process to a friend who's also a senior engineer. No hype sludge. No "I'm excited to announce." Just: here's what I built, here's why it matters, here's what I learned.
Share:
Never share:
Audience: Engineers, CTOs, founders who build. They scroll between meetings looking for something that makes them think.
Format:
Tone: Confident, teaches something. You're the senior engineer explaining your approach to a peer. No jargon without explanation. If you used a technique others might not know, explain it briefly.
When to post: Tuesday-Thursday, 8-10 AM in target timezone. Avoid weekends and Monday mornings (everyone's catching up).
test cases passed, vs 13 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.