Great projects die
in silence.
Yours doesn't have to.
DevRel Coach reads your GitHub org the way a sceptical senior engineer would — the repos, the docs, every conversation about you — and hands you a plan: what to fix, what to write, where to show up. Do the work, hit verify, watch the score move.
No signup needed for the public report — sign in with GitHub to unlock the full plan.
Every verified task moves a real, published score.
The way developers find tools is breaking down
There's a moment every maintainer has experienced. Someone asks their AI assistant "what should I use for X?" — and the answer lists three projects. Yours isn't one of them. Not because it's worse. Because the model never properly learned what your project does, and the people who could have said so were never answered.
This is the visibility problem. And it's getting worse.
The front page is now an answer
Developers increasingly ask their assistant — in the editor, in chat — instead of searching. The assistant doesn't squint at your repo and think "hmm, the docs are rough but the project is solid." It reads what's there, processes it as fact, and recommends accordingly. If your README doesn't say what you are in one sentence, if your docs don't render without JavaScript, you simply don't appear. There is no page two to be on.
A great project with unreadable docs is invisible at exactly the moment a developer decides.
The fix is unglamorous and completely doable: a one-sentence README, llms.txt and AGENTS.md, examples that actually run. The Coach checks all of it, generates the files for your repos, and verifies when they're live.
Reddit threads are tomorrow's recommendations
When a developer asks "what should I use?", the answer was usually written months ago — in a Reddit thread, a Hacker News comment, a Stack Overflow answer. Those conversations are where developer trust actually lives. They're also what the models train on.
A mention you never saw still decides what gets recommended next year.
The Coach tracks every mention across five communities in one inbox, tells you which ones are worth showing up for, and turns recurring questions into the content you should have written already.
Here's what doing nothing looks like
- — A developer hits your quickstart, can't get to "it works" in five minutes, and leaves. They tell their team why.
- — Questions about your project pile up on Reddit and Stack Overflow, answered by people guessing. The guesses become the record.
- — AI assistants describe you wrongly — or not at all — and recommend the better-documented competitor instead.
- — Your DevRel work stays invisible internally, because "community vibes" don't survive a budget meeting.
The compound cost is enormous, but it's invisible until adoption stalls. None of it is fixed by ads — developers don't click banners; they ask peers and assistants. Visibility is earned with docs, answers, and examples. Compounding assets, not campaigns.
Measured. Coached. Verified.
No vague advice. Every recommendation comes from a measured gap, and every completed task is re-checked against the real repo. The loop is closed.
We measure
The Smoower Index scans your org like a sceptical senior dev: repos, docs, examples, issue hygiene, community signals, mentions.
You get a plan
Concrete tasks per pillar — each one citing the exact signal that triggered it, with ready-to-commit files where possible.
We verify
Ship it, hit verify, and the rescan confirms it against the live repo. Scores update. Your report writes itself.
Seven pillars. One place.
Tasks
A concrete, repo-specific checklist — licence, CI, README quality, examples. Ship the work, hit verify, and the rescan confirms it against the live repo.
Content
Blog, video, and talk ideas drawn from your real signals: recurring issues, mentions, releases, doc gaps. If there's no signal behind an idea, you never see it.
Reach & AI visibility
Be findable by developers — and by the assistants they ask instead. llms.txt, AGENTS.md, docs that machines can actually read.
Mentions
Every Reddit, Hacker News, Stack Overflow, Dev.to, and Lobsters thread about you, in one inbox. Nothing slips past unanswered.
Community
Issue responsiveness, contribution paths, and the health signals that decide whether someone's first PR is also their last.
Competitors
Pillar-by-pillar score gaps against the orgs you choose. Not a vague sense that they're ahead — the exact places where, and what to do about it.
Reports
Score deltas, work shipped, mentions earned — the summary that survives a budget meeting. Forward it to your boss.
Advice you can audit
Every suggestion must cite the signal it came from — a repo, a mention, an issue theme, a doc gap. If it can't point at the evidence, it gets dropped before you ever see it. No exceptions. No generated fluff, no "have you considered a newsletter?" — just the gap, the fix, and the proof it worked.
All features on every plan. Pay for depth.
Plans aren't live yet — limits will be on usage and data windows, never on which pillars you can see.
Get in touch if you want to join early
Early birds get the best food. Drop your details and we'll reach out as Coach plans open up.
"Your project should have to earn its visibility. Not once — continuously. The Coach shows you how, and proves when it worked."
That's what we're building with DevRel Coach. Find out what developers — and their assistants — see when they look at you.