CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-seo

Optimize content for AI search and LLM citations across AI Overviews, ChatGPT, Perplexity, Claude, Gemini, and similar systems. Use when improving AI visibility, answer engine optimization, or citation readiness.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills-claude/skills/ai-seo/SKILL.md

The canonical home for this skill is ai-seo in popey/claude-code-skills

SKILL.md
Quality
Evals
Security

Quality

Content

35%Scale 1-3

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

This skill is comprehensive in coverage but severely over-engineered for a SKILL.md file. It reads more like a complete marketing guide or whitepaper than a concise skill instruction set, with extensive tables of statistics, tool comparisons, and strategic advice that Claude could largely infer or that should be in reference files. The content would benefit enormously from aggressive trimming to focus on the unique, non-obvious optimization patterns while moving reference material to bundle files.

Suggestions

Cut the content by 60-70%: Remove explanations of what AI platforms are, what schema markup does, what E-E-A-T means, and other concepts Claude already knows. Focus only on the specific, non-obvious optimization patterns and actionable checklists.

Move the detailed tables (platform ranking factors, monitoring tools, content type optimization guides, GEO research data) into referenced bundle files and keep only a brief summary in the main SKILL.md.

Add a validation/feedback loop after optimization: e.g., 'After implementing changes, re-run the AI visibility audit in 30 days. Compare citation rates before/after. If no improvement, check [specific failure modes].'

Replace the strategic advice sections (Common Mistakes, How AI Search Works) with a compact checklist format that assumes Claude understands the underlying concepts and just needs the specific rules to follow.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~400+ lines, with extensive explanations of concepts Claude already knows (how AI search works, what schema markup is, what E-E-A-T means). Large tables of statistics, tool comparisons, and platform descriptions pad the content significantly. Much of this is general knowledge that doesn't need to be spelled out — e.g., explaining what Wikipedia, Reddit, and YouTube are, or describing what each AI platform does.

1 / 3

Actionability

The skill provides structured checklists, audit tables, and specific optimization methods with percentage boosts, which is somewhat actionable. However, there are no executable code examples, no concrete command-line instructions, and much of the guidance remains at the strategic/advisory level rather than providing copy-paste-ready implementations. The audit steps are templates to fill in rather than executable procedures.

2 / 3

Workflow Clarity

There is a clear multi-step audit process (Steps 1-4) and a three-pillar optimization framework, which provides reasonable sequencing. However, there are no validation checkpoints or feedback loops — after optimizing content, there's no explicit 'verify your changes improved AI visibility' step before proceeding. The monitoring section is separate rather than integrated as a validation checkpoint in the workflow.

2 / 3

Progressive Disclosure

The skill references two external files (references/platform-ranking-factors.md and references/content-patterns.md) and related skills, which is good progressive disclosure design. However, no bundle files were provided, so these references are unverifiable. More importantly, the main SKILL.md contains enormous amounts of inline content (platform tables, optimization methods, content type guides, monitoring tools) that should be split into reference files rather than kept in the main body.

2 / 3

Total

7

/

12

Passed

Description

89%Scale 1-3

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

This is a solid skill description that clearly defines its niche in AI search optimization and LLM citation readiness. It excels at trigger term coverage and completeness with an explicit 'Use when' clause. The main weakness is that the core capabilities could be more specific—listing concrete actions beyond 'optimize content' would strengthen it.

Suggestions

Add specific concrete actions to improve specificity, e.g., 'Restructure content for featured snippets, add structured data markup, rewrite for direct citation extraction, and audit pages for AI crawlability.'

DimensionReasoningScore

Specificity

Names the domain (AI search/LLM citation optimization) and lists specific platforms (AI Overviews, ChatGPT, Perplexity, Claude, Gemini), but the core action 'optimize content' is somewhat vague—it doesn't specify concrete actions like 'restructure headings, add schema markup, rewrite for snippet extraction.'

2 / 3

Completeness

Clearly answers both 'what' (optimize content for AI search and LLM citations across named platforms) and 'when' (explicit 'Use when' clause covering AI visibility, answer engine optimization, and citation readiness).

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'AI search', 'AI visibility', 'answer engine optimization', 'citation readiness', plus specific platform names like 'ChatGPT', 'Perplexity', 'Claude', 'Gemini', and 'AI Overviews'. Good coverage of how users would naturally phrase these requests.

3 / 3

Distinctiveness Conflict Risk

This is a clearly distinct niche—AI search optimization and LLM citation readiness is specific enough that it's unlikely to conflict with general SEO skills, content writing skills, or other marketing-related skills. The named platforms and specialized terminology like 'answer engine optimization' create a clear boundary.

3 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation — 10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
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.