跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

ai-seo

Use when optimizing a site or brand to show up in AI answers, LLM citations, AI search, product recommendations, and category answers.

Infinite-Labs-AI · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Infinite-Labs-AI/infinite-skills --skill ai-seo

技能说明


name: ai-seo description: "Use when optimizing a site or brand to show up in AI answers, LLM citations, AI search, product recommendations, and category answers."

AI SEO

Make the company, product, category, use cases, and proof easy for AI answer engines to understand and cite.

Audit The Entity

Inspect what the web can verify:

  • Official site pages that explain the product and category.
  • Founder, team, or company pages.
  • Docs, pricing, comparisons, case studies, changelog, integrations.
  • Third-party mentions, directories, reviews, podcasts, GitHub, app stores, communities.
  • Structured data and clean metadata.

If live research is needed, use current sources and prefer primary pages.

Diagnose Answerability

Ask:

  • Can an AI system identify what this is in one sentence?
  • Is the category explicit?
  • Are use cases and target customers named?
  • Are claims supported by public proof?
  • Are comparisons stated cleanly without legal or factual overreach?
  • Are there third-party corroboration points?
  • Can important pages be crawled without app login or script-only rendering?

Improve The Evidence

Inventory public evidence by claim:

  • Claim the company wants answer engines to repeat.
  • Official source that supports it.
  • Third-party corroboration.
  • Query or buying question it helps answer.
  • Evidence strength.
  • Missing proof or crawl problem.

Then recommend assets that make weak claims easier to verify: canonical explainer, use case page, public example, customer story, fair comparison, documentation, review surface, or reputable third-party mention.

Guardrails

  • Do not recommend fake reviews, synthetic citations, or spam directories.
  • Do not overstate unsupported claims.
  • Treat answer engines as retrieval and synthesis systems, not magic keyword boxes.
  • Prefer durable public evidence over prompt-hack phrasing.

Output

AI answer presence read:
[one paragraph]

Entity clarity:
- Category:
- Audience:
- Use cases:
- Proof:
- Third-party corroboration:

Gaps:
1. [gap] -> [why it matters]

Evidence table:
| Claim | Official source | Third-party source | Query supported | Strength | Gap |

Assets to create:
| Asset | Query/job it supports | Proof required | Priority |

Schema and crawl fixes:
- [fix]

30-day presence plan:
1. [action]
2. [action]
3. [action]