web-content

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The skill is highly actionable with concrete, copy-paste-ready schema, code, and page templates, but it is a long monolithic document that mixes padding and time-sensitive stats with reference material and lacks an explicit validation feedback loop. Splitting reference material into bundle files and tightening prose would improve it.

Suggestions

Move the schema JSON templates, platform-specific optimization, and analytics sections into reference files (e.g. references/schema-templates.md, references/platform-optimization.md) and link to them from SKILL.md to break up the ~670-line monolith.

Trim marketing padding and time-sensitive statistics (e.g. "AI traffic grew 1,200%...", "Google's share dropped below 90%") that Claude does not need and that will date quickly.

Turn schema validation into an explicit feedback loop: validate markup → if errors, fix and re-validate → only then publish, instead of merely listing the validator URL.

Dimension	Reasoning	Score
Conciseness	The body is a ~670-line monolith with marketing-style padding ("SEO gets clicks. GEO gets citations.") and time-sensitive stats ("AI traffic grew 1,200%...") that Claude does not need, though much of it is genuinely useful concrete templates rather than pure fluff.	2 / 3
Actionability	It provides copy-paste-ready, executable artifacts: full schema.org JSON templates, a GA4 regex filter, JavaScript referral-tracking code, HTML TL;DR/stat boxes, and concrete per-page-type structure templates.	3 / 3
Workflow Clarity	Publishing is supported by explicit SEO/GEO checklists and a schema-validation step, but there is no validate→fix→revalidate feedback loop and the overall content-creation sequence is a loose collection of templates rather than a tightly sequenced workflow.	2 / 3
Progressive Disclosure	The body is well-organized into headed sections, but everything is inline in one ~670-line file with no bundle/reference files; content that should be split out (schema templates, platform specifics, analytics) is not separated or navigable.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 conveys a clear, distinctive niche and benefits from an explicit when-to-use trigger, but the description field itself is light on concrete actions and natural-language trigger variations. Tightening the action verbs and broadening trigger terms would raise specificity and trigger-term quality.

Suggestions

Replace the vague "optimization" with concrete actions in the description, e.g. "structure pages, generate schema markup, and optimize content for AI citations".

Add natural trigger terms users would actually say — "AI search", "LLM optimization", "content optimization", "get cited by ChatGPT/Perplexity" — alongside SEO/GEO.

Dimension	Reasoning	Score
Specificity	The description names its domain ("SEO and AI discovery (GEO)") and some mechanisms ("schema", "ChatGPT/Perplexity optimization"), but "optimization" is abstract and it does not enumerate multiple concrete actions like the score-3 anchor.	2 / 3
Completeness	The description states what the skill does, and the frontmatter's when-to-use field ("When creating web content that needs SEO and AI discoverability") provides equivalent explicit trigger guidance, satisfying both what and when.	3 / 3
Trigger Term Quality	It includes natural terms users would say ("SEO", "ChatGPT", "Perplexity"), but leans technical with "GEO" and "schema" and misses common variations such as "AI search", "LLM optimization", or "content optimization".	2 / 3
Distinctiveness Conflict Risk	The SEO-plus-GEO/AI-discovery niche with platform-specific triggers (ChatGPT/Perplexity) is a clear, distinct niche unlikely to conflict with unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

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

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 5 hours 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.