LaunchJury

• [Show HN post] Nothing structurally broken here, but add one line up front (or in the first comment) about karma/account history - a brand-new or low-karma account posting this exact self-aware-about-AI-slop post will still get 'nice account age' comments and mod scrutiny regardless of post quality. If the account has no prior participation, that's the thing that kills this before anyone reads the body.

Show HN post · 8
This is one of the few AI-launch-tool Show HNs I'd actually read to the end. It leads with mechanism (repo -> Algolia/Reddit fetch -> draft -> jury -> foreman gate), not benefits. The 'Not done yet' section is real: shallow-clone GitHub ingestion with no auth, unauthenticated Reddit prefetch that rate-limits, unpicked juror weights, video scripts admitted to be the weakest output 'by a distance.' That last line alone earns trust most Show HNs never bother with. The self-referential move - ran the tool on itself, got a 5/10, rewrote by hand from the jury's notes, and shipped the failing report.html in examples/ - is the single strongest piece of proof in the whole post; it's the kind of receipts HN actually rewards. Citing CoLaunchly by name (1 point, 0 comments, domain now spam) to pre-empt the wrapper objection is exactly the right move, and doing it before someone else does is disarming rather than defensive. The backtest against 18 historical threads is appropriately hedged ('n=18, one category... treat it as a smoke test, not evidence') instead of oversold. Title is factual and under 80 chars, no superlatives, license and cost model stated plainly.

• Trim the middle third (the backtest paragraph and the research-split paragraph could be one paragraph, not two) → “I also blind-tested it against 18 old Show HNs with known point counts - script's in scripts/backtest.ts - and it separated the top few from the bottom few but was noise in the middle, n=18, treat as a smoke test.”

Product Hunt launch · 8
Tagline is 58 chars, benefit-led, no jargon, and reads fine next to a logo — it promises an outcome (know how it lands) not a feature list. The description is genuinely scannable: numbered steps, plain verbs, one code line up top. The 'Honest bits' paragraph — mock is free, real run is ~$3, and it scored its own first draft a 5/10 with the report published — is the single strongest thing in this whole kit. That's the kind of specific, falsifiable claim that gets PH commenters to actually click through instead of scrolling past another 'AI writes your launch copy' card. The maker comment nails the format: first-person origin story (two days staring at an empty title field), what changed the maker's mind (running it on itself), and it ends on a real open question instead of a fake rhetorical one. My only real complaint is that nothing here tells me what the gallery's first image actually is — for PH that's half the click decision, and right now I have no idea if slide 1 is a screenshot of report.html, the terminal, or a logo card.

• Specify the first gallery image/GIF → “Slide 1: a cropped screenshot of report.html showing the foreman table — 'weighted 7.1 · min 5.0 · FAIL' in red, then 'weighted 8.2 · PASS' in green right below it. That single before/after row sells the whole pitch in one glance.”

Launch video script · 7
Scene 3's research.json beat and Scene 6's self-scored-5/10-plus-backtest beat are the strongest 24 seconds of dev-tool video I've reviewed this cycle — real URLs, real point counts, a chart with misses circled in red instead of a highlight reel. That's proof, not hype, and it directly defuses 'another LLM wrapper that writes marketing copy' better than any tagline could. Under 90s total, good. But the actual hook is slower than it reads: Scene 1 is 7 seconds long, and the VO says '17,661 holds for a beat, then 448,000 slams in' — if that beat is even 1.5-2s, the payoff number doesn't land until close to second 4-5, and the product itself (the CLI actually running) doesn't start until second 7. For a feed video, you want the thing that makes someone stop scrolling inside 3 seconds, not at the tail end of a stat card.

• Compress Scene 1 so 448,000 lands inside 3 seconds, not after a full beat on 17,661 → “Both numbers type in near-simultaneously (17,661 fading, 448,000 slamming in on top) inside the first 3 seconds, then cut straight to the terminal command by second 4”

• [Reddit posts] De-duplicate the graveyard/competitor anecdote and the closing install-line between the r/SideProject and r/IndieHackers posts — give each its own specific example so cross-posting isn't obvious to shared readers.

Reddit posts · 7
Both posts nail the two hardest gates for a mod: authorship is disclosed in the first sentence/line ('I built the tool, so treat this as an author post', 'Disclosure: this came out of a tool I built and open-sourced'), and the framing is value-first — a self-roast and a backtest, not 'check out my tool'. Titles are lowercase-casual for r/SideProject and flat/technical for r/IndieHackers, which matches how each sub actually writes titles. No affiliate links, no signup wall, no 'DM me', just an npx command and a price disclosure — low removal risk on both. The r/SideProject close with a genuine engagement question ('What's the harshest accurate thing anyone has said about your launch post?') is exactly the kind of thing that sub rewards. The r/IndieHackers backtest post is honest about its own weak methodology ('n=18... that is a smoke test, not evidence'), which is the correct register for that audience and pre-empts the 'this is just vibes' pushback. Where it loses points: the two posts share the identical 'graveyard' anecdote (a competitor at 1 point/0 comments whose domain now redirects to spam) and nearly identical closing CTA sentences ('npx launchjury ./my-project --mock... real run ~$3... MIT'). Anyone active in both subs — and cross-posters get read by the same power users — will clock this as the same copy reshuffled, which is the exact 'copy-paste across subs' tell that gets a second post in someone's feed downvoted even if the first one landed. I'd let the r/SideProject post through as-is; I'd send the r/IndieHackers one back for a different anecdote or a genuinely different data point before it runs the same week.

• Replace the graveyard anecdote in the r/IndieHackers post with a different specific example than the one used in r/SideProject.
• Vary the closing install/pricing line between the two posts instead of the near-identical 'npx launchjury ./my-project --mock ... ~$3 ... MIT' sentence.

X / Twitter thread · 7
The self-deprecating turn in tweet 5 ('It scored my draft a 5 and predicted the top comment: another LLM wrapper that writes marketing copy... I rewrote the post by hand') is the single best sentence in the whole packet — it preempts the exact objection this genre always gets, and it's screenshotable on its own. Tweet 6's backtest with 'useless in the middle, n=18, smoke test not evidence' is the kind of honesty that gets quote-tweeted by skeptical dev accounts instead of ratio'd. Tweet 4's file-path-and-line-count detail (src/jury/foreman.ts, ~120 lines, unit tests) is a good credibility flex. Structurally it's sound: link is in the last tweet, one claim per tweet, each stands alone. But two things pull it down from a 9. First, the opening stat — '448,000 Show HN posts in the past year' — is presented as a flat fact with no source or caveat; that number is wildly implausible (HN doesn't get 40x more Show HNs than 2024) and reads like it was lifted uncritically from a sarcastic HN comment. The first reply on this thread will be someone fact-checking that number, and once the hook is discredited nobody reads tweet 2. Second, per my own rubric I require a visual suggestion on at least half the tweets and there isn't one anywhere — no GIF of the report.html scrolling, no screenshot of the 5/10 verdict, no before/after diff image. This is a thread about a tool that generates a visual HTML report and a diff, and it never shows either.

• Tweet 1 opening stat → “Show HN volume is up something like 20x in the last year by my own count of the Algolia index. Most of it never clears single digits.”
• Add visual callouts → “Tweet 5: 'screenshot of the 5/10 jury verdict page' / Tweet 6: 'GIF scrolling the backtest table, Doom-in-a-QR-code 531 down to CoLaunchly 1' / Tweet 7: 'screenshot of report.html with copy buttons'”
• Closing tag list → “Reply into @levelsio's and @dvassallo's build-in-public threads, tag @AnthropicAI's dev relations account on the Claude Agent SDK mention in tweet 7, and drop tweet 6 (the backtest) into r/SideProject and Indie Hackers as a standalone comment, not a link post”

LinkedIn post · 8
This actually reads native — personal, line-broken, no hashtag soup, and it front-loads the human cost ('two days staring at an empty title field') before the tool. The '5 out of 10... predicted top comment... it was right' beat lands even better here than on X because LinkedIn rewards vulnerability-flex more than raw stats. 'Link in the first comment' is stated correctly and matches platform norms. My only real gap: it never names a number or timeframe the LinkedIn audience can screenshot as a standalone credibility claim (the X thread has 'n=18 backtest,' 'foreman.ts ~120 lines' — this post has none of that specificity, it's all narrative). LinkedIn dev-tool posts that land big usually have one hard number in the first three lines; this one saves all its concreteness for paragraph six.

• Add one concrete number early → “I spent five weeks building a side project and two days staring at an empty title field. The tool I built to fix that ran a blind backtest against 18 historical Show HN launches and separated the 500-point posts from the 1-point posts.”

Show HN post · 8
Title is noun+verb+for-implied-whom and testable: 'reads your repo, scores your draft vs. real Show HNs.' Body names the mechanic in the first paragraph, not buried under outcome language. It pre-empts the exact known objection (AI-generated Show HN fatigue, 448,000 posts) instead of hoping nobody notices — this is the single best move in the whole kit. No banned adjectives. The 'Not done yet' section (English only, unauthenticated Reddit fetch, guessed weights, weak video scripts) is the kind of concrete limitation-listing that earns HN credibility rather than an unearned claim. My only real complaint: it's long enough that a skimmer might bounce before reaching the self-score-of-5 payoff, which is your strongest piece of proof.

Product Hunt launch · 7
Tagline 'Know how your launch post will land before you post it' is benefit-first but slightly abstract for my rubric — 'land' isn't a noun I can verify, unlike 'reads your repo' in the Show HN title. The numbered walkthrough is clear and concrete (README, manifests, Algolia, eight principles). It correctly repeats the same differentiator (deterministic foreman, real research) as every other asset — positioning is consistent. The maker comment's closing question ('I genuinely do not know whether the useful product here is the generated copy or the score') is honest but risks reading as the maker not knowing what he built, which PH voters may not forgive as readily as HN readers will.

X / Twitter thread · 6
Tweets 1-6 are tight, one idea per tweet, no semicolons, numbers doing the work ('17,661... 448,000', '531... 1'). Tweet 4 nails the differentiator in one line: 'The prose is stochastic; the grade isn't' — wait, that has a semicolon, which the rubric explicitly bans in headline-style copy; it's a punchy line so I'll let it slide since it's mid-thread not a headline. Bigger problem: the block after the CTA — 'Tag: indie hacker and build-in-public accounts, dev tool founders...' — reads like leaked internal distribution-plan metadata that got pasted into the public asset by mistake. If that ships, it's an instant tell that this was AI-generated pipeline output, which undercuts the entire 'I rewrote this by hand' credibility story you just spent six tweets building.

Reddit posts · 8
Both posts correctly adapt tone per subreddit norm — r/SideProject gets the feedback-as-value framing, r/IndieHackers gets the data/methodology framing — and both disclose authorship up front, which answers the 'self-promotion without participation' objection directly instead of hoping the mods don't notice. Concrete nouns throughout: 'HN Algolia API,' 'point counts,' 'n=18.' The r/SideProject numbered list ('You led with the output, not the mechanic') is genuinely a masterclass in doing what it preaches. Ending each post with a question to the sub is correct Reddit etiquette, not a growth-hacking bolt-on.

LinkedIn post · 6
Opens strong and concrete ('five weeks... two days staring at an empty title field'), and the parallel structure ('The build had tests, types, CI. The launch post had nothing.') is earned rhythm, not filler. But it drifts into unearned abstraction at the close: 'Most of us edit our own writing by reading it again. That mostly measures how familiar it has become.' That's a LinkedIn-guru aphorism with no noun in it — exactly the kind of sentence I'd cut from a dev-tools post. It also breaks positioning consistency slightly: every other asset leads with the mechanic within two sentences, this one delays the CLI mention to paragraph five.

• [Launch video script] Verify the scene 6 'backtest chart' (18 Show HNs, predicted vs actual, misses circled) is an actual, recordable feature of the shipped tool before this shot is filmed — if it doesn't exist, replace it with a real captured screen (e.g. the foreman FAIL/PASS table or the two-round revision diff), because an invented chart is the single fastest way to lose credibility with the exact skeptical-HN-reader audience this launch is targeting.
• [Launch video script] Rewrite scenes 5 and 6 VO to fit 135wpm within their stated durations (currently ~180wpm and ~161wpm respectively) — either cut words or extend the scene length, but as written both will force the voiceover artist to speed up past the flat-delivery direction the rest of the video establishes.
• [Demo video script] Trim scene 5's VO from ~40 words to ~36 or fewer, or extend the scene to 18s, so it hits the 135wpm target the recording notes specify — it's currently the only scene in an otherwise well-paced script running hot.

Demo video script · 8
This is a demo script I'd greenlight almost as-is. It obeys the hook rule to the letter — scene 1 is the 5/10 and 3/10 scorecard, on screen in 4 seconds, before a single line of setup, and the shot note even says 'recorded last so scores match,' which is the correct production discipline. Every scene has SEE/VO/TEXT/SHOT/duration and none of the shots require anything a solo dev can't do with a screen recorder and a real editor: specific fonts (20pt JetBrains Mono, 18pt editor), specific zoom levels (130-150%), specific crops ('crop to bottom 40% in post'), cursor visibility called out per shot. Durations sum correctly to 100s, under the 120s cap. It closes on one clear CTA (mock command + cost/runtime line, held 2 full seconds). It also gets ahead of the single worst-case HN comment in the objections list — 'this is an AI generator posting about AI generators' — by having the jury itself predict that exact line and having the maker answer it on camera, which is the smartest single beat in either script. My only real complaint is pacing math: scene 5's VO ('Drafting is one pass...nothing below six') is ~40 words in 16s, which is ~150wpm, right at the ceiling the recording notes themselves set at 135wpm flat delivery. It'll sound rushed against the note's own instruction.

• Trim or extend scene 5's VO/duration so it reads at 135wpm as specified → “Drafting is one pass. The jury is the interesting part: seven weighted personas score every asset, then a plain TypeScript foreman — unit tested, no model in the loop — aggregates and gates it.”

Launch video script · 6
Strong hook (the 17,661→448,000 stat lands in 7s and reframes the whole pitch, which is a legitimate cold-open even though it's a stat, not a product-result — acceptable for a launch video's different job) and the structure is otherwise disciplined: real fonts, real zoom levels, real crops, one CTA at the end. Two problems keep this out of an 8+. First, pacing is broken in two scenes, not one: scene 5's VO is ~39 words in 13s (~180wpm) and scene 6's is ~43 words in 16s (~161wpm) — both well past the 150wpm ceiling and the recording notes' own 135wpm target from the demo script; as written, a voice actor either garbles the line or the scene runs long and blows the 90s ceiling. Second and more serious: scene 6 shows 'the backtest chart — predicted jury score on one axis, actual HN points on the other, 18 historical Show HNs plotted, three misses circled in red.' Nothing in the product description — README, manifests, jury, foreman, report.html — describes a backtest feature or chart. If that screen doesn't exist in the actual tool, this shot is not recordable by a solo dev with a screen recorder in an afternoon, which is the rubric's baseline test; it's a rendered mockup pretending to be a captured screen, and that's exactly the kind of unverifiable claim the skeptical-HN-reader audience will call out immediately.

• Fix pacing on scenes 5 and 6 to hit 135wpm or under → “Seven weighted reviewer personas score your draft and predict the top comment you'd get. A plain TypeScript foreman — no model in the loop — decides pass or fail, and rewrites on a fail.”
• Cut or verify the 'backtest chart' shot in scene 6 → “SEE: ... cut to report.html's foreman table showing the min-score gate and the two-round revision history for this exact run — real artifact, not a synthesized chart.”

• [Show HN post] Source or fix the '17,661 to 448,000 Show HN posts' claim before posting — this exact number will be the first thing checked and challenged, and the whole pitch rests on 'we cite real numbers, not vibes.' If it can't be defended with an exact Algolia query, replace it with a smaller, verifiable claim.
• [LinkedIn post] Add the backtest's honest limitation (useless in the 20-100 point 'middle') to the LinkedIn post — right now it's the only asset that hides the tool's known weakness, which makes it read as the least honest piece in an otherwise unusually honest campaign.
• [Reddit posts] Vary the recycled anecdotes (CoLaunchly corpse, 5/10 self-score) between the two Reddit posts and the other channels — a reader who follows the launch across HN, Reddit, X and LinkedIn will hit the identical beats four times, which turns 'authentic disclosure' into 'rehearsed talking point.'

Show HN post · 7
This is the most self-aware Show HN post I've seen from this category in a while — naming the exact objection, publishing a failing self-score, and disclosing real weaknesses (video scripts, unweighted persona weights, no GitHub auth) instead of hiding them. That buys real trust. But two things stop me: first, the '17,661 → 448,000 Show HN posts in a year' stat is repeated as the load-bearing why-now claim and it doesn't pass a smell test — 448,000 Show HNs in a year is ~1,227/day, which is not what the front page looks like. If the tool's entire pitch is 'grounded in real data, cites URLs,' and its own headline stat looks fabricated or misquoted, that's the first thing I'd pick apart in the comments. Second, it's still fundamentally an AI content generator posting to a community fatigued by AI content generators — naming that fact doesn't make the post not-that. It buys goodwill, it doesn't dissolve the objection.

• Verify or replace the 17,661/448,000 Show HN count claim → “a cited Algolia query result with the exact search parameters, or a softer/removed claim if it can't be verified”

Product Hunt launch · 6
Reasonable, well-organized, and PH audiences tolerate more polish/hype than HN does, so the numbered-list format works fine here. But 'Know how your launch post will land before you post it' oversells what an n=18, useless-in-the-middle backtest can actually deliver — I'd want that walked back given the honesty shown elsewhere in the campaign. It also just repeats the same 5/10 self-score beat that's already been told on HN/X/Reddit/LinkedIn, so anyone following the launch across channels sees the same anecdote five times, which starts to feel like a rehearsed talking point rather than a spontaneous disclosure.

X / Twitter thread · 6
Fine as a thread — technical, links the backtest, doesn't oversell. But it inherits the same shaky why-now stat implicitly through the repeated framing, and tweet 3's claim 'that prediction was more useful to me than any of the copy it wrote' combined with tweet 6 admitting the jury is 'useless in the middle' undercuts its own value prop pretty hard for a growth-marketing audience that wants confidence, not caveats stacked on caveats.

Reddit posts · 7
These two are the strongest assets in the kit. The r/SideProject post correctly leads with the mechanic and the failure, discloses it's an author post up front, and ends with a genuine question instead of a pitch. The r/IndieHackers post is even better — it leads with the negative finding (useless in the middle 20-100 point band) and frames the tool as a footnote to a more interesting empirical result. That's exactly the register that survives in these subs. My only knock: both still lean on the same CoLaunchly-corpse anecdote already used elsewhere, so a reader who's seen the HN post first gets déjà vu.

LinkedIn post · 5
This is the weakest asset. Lines like 'The build had tests, types, CI. The launch post had nothing' and 'That's the part I keep thinking about' are exactly the kind of vague-inspirational LinkedIn cadence I'd screenshot and mock — it's dressed-up humility as a hook, and it's thinner on substance (no mention of the backtest's failure in the middle band, no mention of the questionable stat) than every other asset in the kit. It reads like it was optimized for engagement-bait rhythm rather than for informing anyone.

• Cut the throat-clearing intro and add the backtest caveat → “It's not magic: backtested blind against 18 old Show HNs, it separated the top and bottom but was close to random in the middle. Still, a 5/10 with reasons beat my own read of my own writing.”

Demo video script · 7
Genuinely good demo script — it opens on a failure (5/10), shows the FAIL gate, shows the round-1/round-2 diff, and doesn't pretend the tool is magic. That's rare and I respect it. The over-engineered production notes (macOS cursor size, DND, sanitizing $HOME) for a side-project tool are slightly funny but harmless — nobody in this audience penalizes production care. My real concern is the same one as everywhere: the on-screen '17,661 → 448,000' text card in scene 4 puts the shaky stat in the most scrutinized, screenshottable format of the whole campaign.

Launch video script · 7
Strong opening beat with the backtest chart and 'misses circled in red' — that's the single most convincing 16 seconds in the whole kit because it shows failure honestly instead of asserting competence. Same objection as the rest: the cold open bets everything on the 17,661/448,000 stat being true and citable, and if it isn't, the whole video's credibility (which is otherwise its strongest asset) collapses in the first 7 seconds.