本文へ移動
cccskills
無料GitHub で公開

ai-search-optimization

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.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md3.3 KB
  • references/sources.md1.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

What gets cited

  • Self-contained passages. A retrieved chunk arrives without the surrounding page. Each section must make sense alone, with its subject named rather than pronominalized.
  • Direct answers near the question. Bury the answer under three paragraphs of context and the passage retrieved will be the context.
  • Specific, checkable facts — numbers, dates, named methods, stated conditions. Vague claims are neither retrievable nor quotable.
  • Attributable expertise. Named authors, stated credentials, dated content, and cited sources. Anonymous undated content is weakly weighted.
  • Structure that survives extraction — real headings, real lists, real tables. Layout implied by styling disappears.

Practical moves

  • Answer the question in the first sentence under each heading, then elaborate.
  • Write headings as the questions people actually ask.
  • Define your own terms on your own pages, so the model's definition traces to you.
  • Keep facts consistent across your site. Contradictions get resolved against you.
  • Maintain the boring canonical pages — pricing, comparisons, specifications, FAQ. These are heavily retrieved and usually neglected.

Being represented accurately

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.

Measuring

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.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Optimize for one assistant's current behavior. Retrieval and citation rules change without notice and without a changelog.
  • Assume being crawlable means being citable. Models cite sources that answer a question cleanly, not sources that merely exist.
  • Leave an inaccurate representation uncorrected because it is not on your site. The claim propagates whether or not you own the page it came from.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0322026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0322026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0322026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0322026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0322026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0322026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する