Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.
npx skills add https://github.com/cbrock84/headcount --skill ai-search-optimization
Classical SEO optimizes to be *clicked*. This optimizes to be *quoted* — often with no click at all.
That changes what a good page looks like.
must make sense alone, with its subject named rather than pronominalized.
passage retrieved will be the context.
neither retrievable nor quotable.
Anonymous undated content is weakly weighted.
styling disappears.
retrieved and usually neglected.
Assistants assemble an answer about you from whatever is available, weighted toward third-party and
structured sources. Where those are thin or stale, the answer will be wrong.
Audit periodically: ask several assistants what your company does, who it is for, what it costs, and
how it compares. Note the errors and trace them to a source. The fix is almost always publishing or
correcting the source, not the assistant.
Click-through will fall on informational queries even as influence rises. Track citation and mention
frequency, and downstream branded search and direct traffic, rather than judging this program on
organic sessions — that metric will say you are losing while you are winning.
Take cbrock84/ai-search-optimization from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.