CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-seo

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable reference with strong progressive disclosure to three real bundle files and a clear audit→optimize→monitor workflow. Its main weakness is redundancy: Google's official stance and AI-bot blocking guidance are each repeated across multiple sections and could be consolidated to save tokens.

Suggestions

Consolidate the recurring Google stance into one canonical section and reference it rather than restating it in 'Machine-Readable Files', 'Schema Markup', 'What NOT to Do', and 'Common Mistakes'.

Merge the overlapping AI-bot blocking guidance (Step 4, What NOT to Do #5, Common Mistakes) into a single robots.txt treatment to remove triplicated content.

Dedupe the pricing.md and keyword-stuffing points that appear in both 'What NOT to Do' and 'Common Mistakes', keeping one authoritative location.

DimensionReasoningScore

Conciseness

Mostly efficient, information-dense reference material (tables, stats, checklists), but the same guidance is restated across several sections — Google's stance and AI-bot blocking each recur in 3+ places — so it could be meaningfully tightened.

3 / 5

Actionability

Provides concrete, copy-paste-ready artifacts (the /pricing.md markdown template, schema-type table, named AI bot user-agents, pass/fail audit checklists), with only minor stretches of principle-level advice such as "write with demonstrated expertise."

4 / 5

Workflow Clarity

A clear sequence runs from gathering context through the 4-step AI Visibility Audit (with pass/fail and bot-access checkpoints) into the Three Pillars and monitoring, though the audit lacks an explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Overview content stays inline while detail is pushed to three real one-level-deep references (platform-ranking-factors.md, content-patterns.md, content-types.md), each clearly signaled with contextual markdown links; navigation is easy.

5 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong, third-person statement that crisply defines the skill's purpose, packs in comprehensive natural trigger terms and synonyms, and explicitly distinguishes it from neighboring SEO skills. It cleanly satisfies both the what and when requirements with concrete, citable phrasing.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — "optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers" — comparable to the anchor listing several specific actions with minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (optimize/get cited/appear in AI answers) and when ("Also use when the user mentions…", "Use this whenever someone wants their content to be cited or surfaced") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and acronyms ("AI SEO," "AEO," "GEO," "LLMO," "answer engine optimization") plus user phrasings like "how do I show up in AI answers" and "optimize for ChatGPT."

5 / 5

Distinctiveness Conflict Risk

Clear niche (AI search citation/visibility) with explicit disambiguation from adjacent skills — "For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema" — minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
joshmanders/dotfiles
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.