site-architecture

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

Quality

48%

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/site-architecture/SKILL.md

Quality

Discovery

54%

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 benefits from strong, specific trigger terms that clearly identify the technical SEO domain, making it distinctive. However, it reads more like a topic list than a skill description—it lacks concrete action verbs describing what the skill does and entirely omits a 'Use when...' clause to guide skill selection.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Generates and validates robots.txt files, creates XML sitemaps, audits meta tags, and analyzes Core Web Vitals performance.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about technical SEO, crawlability, indexing issues, robots.txt configuration, sitemap generation, meta tag optimization, or page speed / Core Web Vitals.'

Use third-person active voice to describe capabilities rather than listing topics as a comma-separated fragment.

Dimension	Reasoning	Score
Specificity	Names the domain (Technical SEO) and lists specific topics (robots.txt, sitemap, meta tags, Core Web Vitals), but these are nouns/topics rather than concrete actions. It doesn't describe what it does with these things (e.g., 'generates robots.txt files', 'audits meta tags', 'analyzes Core Web Vitals').	2 / 3
Completeness	Answers 'what' only at a topic level (not action level) and 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 strong natural keywords that users would actually say: 'robots.txt', 'sitemap', 'meta tags', 'Core Web Vitals', and 'Technical SEO'. These are all terms a user would naturally use when seeking help with these topics.	3 / 3
Distinctiveness Conflict Risk	Technical SEO is a clear niche, and the specific trigger terms (robots.txt, sitemap, meta tags, Core Web Vitals) are highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	9 / 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.

This skill is a comprehensive technical SEO reference with excellent, executable code examples, particularly for Next.js implementations. However, it is far too verbose for a skill file — it reads more like a complete tutorial or documentation page than a concise skill. The massive inline content (600+ lines) wastes context window tokens on information Claude largely already knows, and the lack of file decomposition makes it a monolithic reference rather than a well-structured skill.

Suggestions

Split into multiple files: keep SKILL.md as a concise overview (~50-80 lines) with links to separate files like ROBOTS_TXT.md, SITEMAP.md, META_TAGS.md, CORE_WEB_VITALS.md, and STRUCTURED_DATA.md.

Remove explanatory content Claude already knows (URL best practices, what canonical URLs are, basic meta tag purposes) and keep only the specific templates and code examples.

Add an explicit implementation workflow with validation steps: e.g., '1. Set up robots.txt → 2. Validate with Google robots.txt tester → 3. Generate sitemap → 4. Validate XML → 5. Submit to Search Console → 6. Verify indexing'.

Trim reference tables (meta tag lengths, image sizes, AI crawler lists) to only include non-obvious or project-specific values, or move them to a separate REFERENCE.md file.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines. Includes extensive boilerplate templates, explanations of basic concepts (what robots.txt is, what Open Graph is, URL best practices), and reference tables that Claude already knows. Much of this is standard web development knowledge that doesn't need to be spelled out in full.	1 / 3
Actionability	Highly actionable with fully executable code examples throughout — complete Next.js TypeScript implementations for robots.ts, sitemap.ts, metadata, breadcrumbs, redirects, and security headers. All code is copy-paste ready with realistic configurations.	3 / 3
Workflow Clarity	The checklist at the end provides a good summary of what needs to be done, and sections are logically ordered. However, there's no explicit sequenced workflow with validation checkpoints — no 'do this first, then verify, then proceed' pattern. For a skill involving site configuration that could break crawling, validation steps (e.g., test robots.txt, validate sitemap XML, check structured data with Rich Results Test) are mentioned but not integrated into a step-by-step workflow.	2 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files. Everything is inline — robots.txt templates, sitemap examples, meta tag references, Core Web Vitals, internal linking, structured data, security headers. This should be split across multiple files (e.g., META_TAGS.md, CORE_WEB_VITALS.md, STRUCTURED_DATA.md) with the SKILL.md serving as an overview with links.	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 (931 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.