Developers spend their careers making things rank and then ship repositories with a two-line README and no topics. The audience they're not optimizing for is no longer just human.

Say "SEO" to a developer and they picture content marketing — blog posts, keyword reports, the stuff that happens to other people. Say "repo SEO" and they'll assume it's a metaphor. It isn't. GitHub is a search engine with an index, a query language, ranking signals, and a results page. And as of this year, it has something better: it is becoming the retrieval layer that AI coding assistants read when they decide which library to use.

One skill in the agent-skill directory I run takes this seriously. agentic-seo-skill by Bhanunamikaze scores 7.8 overall — mid-table, not top-tier — but it contains 16 sub-skills, 89 scripts, and one of those sub-skills runs a full SEO audit of a GitHub repository : README structure, topics, the social preview card.…