site-architecture
Technical SEO - robots.txt, sitemap, meta tags, Core Web Vitals
43
44%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/site-architecture/SKILL.mdQuality
Discovery
47%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 effectively lists relevant technical SEO topics with good keyword coverage, but it reads more like a tag list than a functional description. It lacks concrete action verbs describing what the skill does and entirely omits guidance on when Claude should select this skill over others.
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 diagnoses Core Web Vitals issues.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about technical SEO, search engine crawling, indexing issues, page speed optimization, or site structure for search engines.'
Consider specifying boundaries to reduce overlap, e.g., distinguishing this from content SEO, general web performance, or web development skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Technical SEO) and lists specific areas (robots.txt, sitemap, meta tags, Core Web Vitals), but these are topics/nouns rather than concrete actions. It doesn't describe what it actually does with these things (e.g., 'generate robots.txt files', 'audit meta tags', 'analyze Core Web Vitals scores'). | 2 / 3 |
Completeness | There is no 'Use when...' clause or equivalent explicit trigger guidance, and the 'what' is only partially addressed (topics listed but no actions). Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also weak (no verbs/actions), 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 'SEO' are all terms users would naturally use when seeking help in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | The 'Technical SEO' label combined with specific subtopics like robots.txt and Core Web Vitals provides some distinctiveness, but it could overlap with broader SEO skills, web development skills, or performance optimization skills without clearer boundaries. | 2 / 3 |
Total | 8 / 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 across multiple areas, but it suffers severely from being a monolithic document that tries to cover too many topics in one file. Much of the content (URL best practices, meta tag character limits, image dimensions, security headers) is general knowledge Claude already possesses, making the skill far more verbose than necessary. The lack of progressive disclosure and workflow sequencing makes it more of a reference dump than an actionable skill.
Suggestions
Split into focused sub-files (e.g., ROBOTS.md, SITEMAP.md, META-TAGS.md, CORE-WEB-VITALS.md) and make SKILL.md a concise overview with links to each topic.
Remove content Claude already knows: URL best practices, meta tag character limits, image dimension tables, security header explanations, and general SEO concepts like 'content is king'.
Add a clear implementation workflow with sequenced steps and validation checkpoints, e.g., '1. Set up robots.txt → 2. Validate with Google tester → 3. Generate sitemap → 4. Submit to Search Console → 5. Verify indexing'.
Remove the philosophy section and reduce the AI crawler table to just the bot names, since Claude can look up user-agent strings.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~600+ lines, containing extensive template code that Claude could generate on its own. Much of this is reference material (meta tag lengths, image sizes, URL best practices, security headers) that Claude already knows. The philosophy section and explanatory text add unnecessary padding. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples across multiple frameworks (Next.js TypeScript, raw HTML, XML, robots.txt). Code is complete and specific with real configuration values, not pseudocode. | 3 / 3 |
Workflow Clarity | The skill provides checklists and covers many topics but lacks clear sequencing for implementation. There are no validation checkpoints or feedback loops (e.g., 'validate robots.txt with Google's tester before deploying' is mentioned in a checklist but not integrated into a workflow). The content reads more like a reference manual than a guided process. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of content with no references to external files despite covering 12+ distinct topics (robots.txt, sitemaps, meta tags, URLs, canonicals, security headers, Core Web Vitals, internal linking, AI crawlers, structured data, verification). This should be split into focused sub-files with the SKILL.md serving as an overview. No bundle files are provided to offload content. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%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 (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 | 9 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
7e5f7a2
- 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.