We’ve all been there - you’re sick of Claude forgetting what it did last session, so you built a sweet new tool to solve the problem, and now you’re ready to publish. You chuckle to yourself while writing the Reddit post: “I can’t believe nobody has thought of this yet. I am a genius, and the world needs this.” Sure, a cynic might point out that fifteen people shipped this same thing last month. But you wouldn’t know - you didn’t look, because why would you need to? Best to preempt the haters and explain why yours is different anyway. The problem is that manually searching for competition is wasteful inefficiency that your one-man org simply can’t afford . That’s where cba-searching comes in. Have Claude install the skill, run it in your repo, and do the hard work for you: it searches GitHub for similar projects, maps feature overlap, reads past the README spin to see what each thing really is, grades the incumbents on execution (stars, releases, tests, maintained-or-graveyard — because ideas don’t win, execution does), and hands you a blunt go/no-go verdict. The skill has been tested exactly once, on itself, so I’m 100% confident that it is production-ready and original. See it in action: “I found 7 similar repositories, of which 1 shares 4+ of your 8 features and 0 fully cover your application.” “r14dd/patent (360★, tested, CI, shipped today) already does prior-art-for-code-ideas across 11 registries — your core pitch, its literal tagline. Your only real edge is grading incumbents on execution, which patent doesn’t do yet; everything else is a Claude-skill repackage with zero tests and zero stars. Build the execution-scoring angle or don’t build at all — the search box you’re selling would’ve told you patent existed in 30 seconds.” https://github.com/scodge-24/cba-searching submitted by /u/scodgey
Originally posted by u/scodgey on r/ClaudeCode