site-architecture

Technical SEO - robots.txt, sitemap, meta tags, Core Web Vitals

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/site-architecture/SKILL.md

Quality

Content

50%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 content is a thorough, mostly-executable technical-SEO reference with good sectioning and concrete templates, but it is significantly verbose, repeats material across sections, and offers no sequenced workflow with validation checkpoints or external file references.

Suggestions

Move large reusable blocks (the full AI-bot robots.txt rules, the meta-tag reference, the Core Web Vitals tables) into reference files and link to them one level deep to reduce repetition and token cost.

Add explicit validate/test checkpoints for destructive or batch operations, e.g. 'Test robots.txt with Google's tester before deploying' and 'Verify 301 redirects with curl before enabling'.

Trim explanations of concepts Claude already knows (Core Web Vitals definitions, basic URL casing rules) and de-duplicate the repeated robots.txt configurations.

Dimension	Reasoning	Score
Conciseness	At ~930 lines the body repeats substantial blocks (robots.txt configurations appear multiple times), restates well-known concepts like Core Web Vitals thresholds and basic URL hygiene, and inlines large reference tables/checklists that assume Claude's competence, fitting 'noticeably verbose; several unnecessary explanations or padded sections' more than the efficient score-3 anchor.	2 / 5
Actionability	It provides mostly executable, copy-paste-ready Next.js (robots.ts, sitemap.ts, metadata), HTML meta tags, and XML sitemap templates covering common cases, with only minor gaps (some examples rely on undefined helpers like getBlogPosts and use placeholder domains), matching the 'mostly executable; minor gaps' anchor.	4 / 5
Workflow Clarity	Content is organized by topic with a final checklist, but it is a reference catalog rather than a sequenced workflow; risky operations like 301 redirects and robots.txt Disallow rules lack explicit validate/test checkpoints, so it fits 'steps listed but validation gaps; checkpoints missing or implicit' and the destructive/batch cap of 3.	3 / 5
Progressive Disclosure	There are no bundle files (references/scripts/assets absent) and the entire body is inlined in SKILL.md with heavy section repetition; while section headers provide some structure, large blocks that could live in separate files are inlined, fitting 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	12 / 20 Passed

Description

58%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 concise, third-person, and names concrete sub-domains, but it omits any explicit 'Use when...' trigger guidance within the description field and lacks synonyms/file extensions that users would naturally say.

Suggestions

Add a 'Use when...' clause to the description, e.g. 'Use when setting up or auditing technical SEO, robots.txt, sitemaps, or meta tags.'

Include natural trigger synonyms and file extensions users say, such as 'SEO', 'Open Graph', 'sitemap.xml', and 'structured data'.

Consider folding the existing 'when-to-use' guidance into the description so the trigger context travels with the description field.

Dimension	Reasoning	Score
Specificity	The phrase 'robots.txt, sitemap, meta tags, Core Web Vitals' lists several concrete sub-areas of the domain with only minor gaps (e.g., structured data, canonical URLs not surfaced), matching the 'several specific actions; minor gaps' anchor rather than the fully comprehensive score-5 anchor.	4 / 5
Completeness	It clearly answers 'what' (technical SEO covering those four areas) but provides no 'Use when...' trigger clause inside the description — the when-guidance lives in a separate 'when-to-use' frontmatter field — so per the rubric a missing explicit trigger caps completeness at 3 rather than 4.	3 / 5
Trigger Term Quality	'robots.txt', 'sitemap', 'meta tags', and 'Core Web Vitals' are natural terms users say, but the set lacks common synonyms and file extensions (e.g., 'SEO', 'Open Graph', '.xml', 'sitemap.xml'), so coverage is relevant but incomplete.	3 / 5
Distinctiveness Conflict Risk	'Technical SEO' with concrete artifacts (robots.txt, sitemap, Core Web Vitals) carves a mostly distinct niche with only minor overlap risk against a generic 'SEO' or 'content' skill, fitting the 'mostly distinct; minor overlap' anchor.	4 / 5
	Total	14 / 20 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 (930 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
Path: skills/site-architecture/SKILL.md
Commit: abc600e

Reviewed: 7 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.