web-content

SEO and AI discovery (GEO) - schema, ChatGPT/Perplexity optimization

Quality

37%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/web-content/SKILL.md

Quality

Discovery

32%

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 identifies a relatively novel and specific domain (GEO/AI discovery optimization) but reads more like a topic label than a functional skill description. It lacks concrete actions, explicit trigger guidance, and a 'Use when...' clause, making it difficult for Claude to reliably select this skill at the right time.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about optimizing content for AI search engines, improving visibility in ChatGPT or Perplexity responses, or implementing structured data/schema markup.'

List specific concrete actions the skill performs, e.g., 'Generates JSON-LD structured data, optimizes content for AI citation and retrieval, audits pages for generative engine optimization (GEO), and improves discoverability in ChatGPT, Perplexity, and similar AI platforms.'

Expand trigger term coverage to include natural variations like 'structured data', 'JSON-LD', 'rich snippets', 'AI search optimization', 'generative engine optimization', and 'search engine optimization'.

Dimension	Reasoning	Score
Specificity	Names the domain (SEO and AI discovery/GEO) and mentions some specific areas like 'schema' and 'ChatGPT/Perplexity optimization', but doesn't list concrete actions (e.g., 'generate structured data markup', 'optimize content for AI citation').	2 / 3
Completeness	Provides a partial 'what' (SEO and AI discovery optimization involving schema) but completely lacks a 'when' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'SEO', 'schema', 'ChatGPT', 'Perplexity', and 'GEO', which users might naturally mention. However, it misses common variations like 'search engine optimization', 'structured data', 'AI search', 'rich snippets', 'JSON-LD', or 'generative engine optimization'.	2 / 3
Distinctiveness Conflict Risk	The combination of SEO with AI discovery platforms (ChatGPT/Perplexity) and GEO creates a somewhat distinct niche, but 'SEO' alone is broad and could overlap with general content writing or marketing skills. The mention of specific AI platforms helps but isn't enough for full distinctiveness.	2 / 3
	Total	7 / 12 Passed

Implementation

42%

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

The skill excels at actionability with concrete, copy-paste ready schema markup, HTML templates, and tracking code. However, it is severely bloated—easily 3-4x longer than necessary—with content that should be split across multiple referenced files. It also wastes tokens explaining concepts Claude already knows (SEO basics, E-E-A-T definitions, what AI search is) and includes time-sensitive statistics that will quickly become outdated.

Suggestions

Split into multiple files: move schema examples to SCHEMA.md, page templates to TEMPLATES.md, platform-specific optimization to PLATFORMS.md, and analytics tracking to ANALYTICS.md—reference each from a concise SKILL.md overview.

Remove explanatory content Claude already knows: the Philosophy section, E-E-A-T definitions, and explanations of what SEO/GEO are. Replace with just the actionable rules.

Remove time-sensitive statistics ('AI traffic grew 1,200%', 'Google's search share dropped below 90%') that will become outdated and waste tokens.

Add an explicit content creation workflow with validation checkpoints: e.g., draft → validate schema with schema.org validator → check against checklists → publish, with a feedback loop for schema validation failures.

Dimension	Reasoning	Score
Conciseness	At ~400+ lines, this skill is extremely verbose. It explains concepts Claude already knows (what SEO is, what E-E-A-T stands for, basic HTML structure), includes lengthy philosophy sections, and provides extensive template content that could be referenced in separate files. The statistics about AI traffic growth and Google's search share are unnecessary padding.	1 / 3
Actionability	The skill provides fully concrete, copy-paste ready examples throughout: complete JSON-LD schema markup, HTML templates, JavaScript tracking code, GA4 regex filters, and detailed page structure templates. Every section includes specific, executable guidance rather than vague descriptions.	3 / 3
Workflow Clarity	The content checklist at the end provides a clear sequence for publishing, and schema validation is mentioned. However, there's no explicit workflow for the overall content creation process—steps are presented as independent sections rather than a sequenced workflow with validation checkpoints between stages (e.g., validate schema before publishing).	2 / 3
Progressive Disclosure	This is a monolithic wall of content with everything inline. The page templates, schema examples, platform-specific optimization guides, and analytics code should all be in separate referenced files. The skill mentions loading 'base.md + ui-web.md' but doesn't offload any of its own massive content to sub-files, making it a single enormous document.	1 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (682 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: d4ddb03

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.