If you maintain anything on GitHub, you have probably gotten one of these issues:
"We added your project Claude HowTo Templates to CodeGuilds, a community registry for the Claude Code ecosystem... If you'd like to claim ownership of the listing and manage it yourself, you can sign in with GitHub at codeguilds.dev."
Or the cousin version:
"I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools... your page is live. If any of this misrepresents the project, reply here and a human fixes it."
Same mechanic twice, independently: a directory adds your repo without asking, files a GitHub issue to tell you, and invites you to create an account to "claim" or "correct" the listing you never requested. It reads as a gift. It is an inbound account-creation funnel wearing a gift's clothes.
This is graveyard item #2 in my research, refuted 2 out of 3 independent checks. It is worth a full post instead of a line item because the mechanism is sound-sounding enough that I'd have shipped it myself before checking.
Why it looks like it should work
Every ingredient is right there. Free distribution to a maintainer who already has a relevant audience. A low-friction ask, just sign in with the account you already have. Flattery, your project was good enough to get noticed. On paper this is a cold-outbound tactic with the cold part removed, because you're not asking for anything, you're informing them of something nice that already happened.
Where it breaks
The thing that doesn't survive scrutiny is the premise that an unsolicited addition reads as a gift to the recipient. It reads as a directory needing your repo more than you need the directory. You did not evaluate CodeGuilds or StackMap and choose to list there. Someone chose you, as inventory. The GitHub issue is the tell: it is simultaneously a notification, an advertisement for the directory itself, and a conversion funnel, and a maintainer who has seen one knows it is a conversion funnel the second time.
Compare this to the pattern that did survive: posting in an adjacent project's Discussions, framed as genuinely complementary. The difference is consent to the interaction. A reply to a thread someone else started is participation. An issue you did not ask for, about a listing you did not ask for, is not.
The diagnostic question
Before you ship any variant of "we noticed you, come claim this," ask: did the recipient do anything to invite this contact?
If the honest answer is no, the warmth you're borrowing (community, curation, a knowledge graph) is doing the work that actual permission should be doing. That gap is where this tactic dies, not in the execution, which in both sourced cases was polite and well-written.
What to do instead
If you're building a directory, the pattern that did survive refutation is the opposite shape: let people opt in, and if you want outbound, make it a reply to something they already said in public, not a notification about something you already did to them.
I run every growth tactic I can find through adversarial re-checking before it goes anywhere near a recommendation. Eleven of twenty died this way. The full list, with a source URL on every claim, is an MIT Claude Code plugin at why-isnt-it-selling.
Top comments (0)