site-architecture
Technical SEO - robots.txt, sitemap, meta tags, Core Web Vitals
45
48%
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
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 and would help Claude match user requests accurately. However, it reads as a topic list rather than a skill description—it lacks concrete action verbs describing what the skill does and entirely omits a 'Use when...' clause, significantly hurting completeness.
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, crawlability, indexing, robots.txt configuration, sitemap generation, meta tag optimization, or page speed / Core Web Vitals improvements.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Technical SEO) and lists specific artifacts (robots.txt, sitemap, meta tags, Core Web Vitals), but doesn't describe concrete actions—it's a list of topics rather than verbs like 'generate', 'audit', or 'optimize'. | 2 / 3 |
Completeness | Answers 'what' only partially (lists topics but not actions) and completely lacks a 'when' clause or any explicit trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would actually say: 'robots.txt', 'sitemap', 'meta tags', 'Core Web Vitals', and 'SEO' are all terms users commonly use when seeking help with technical SEO tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Technical SEO is a clear niche, and the specific artifacts listed (robots.txt, sitemap, meta tags, Core Web Vitals) make it highly distinguishable from other skills like content SEO, general web development, or analytics. | 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 across robots.txt, sitemaps, meta tags, and Next.js implementations. However, it is far too long and monolithic for a SKILL.md — it reads more like a documentation site than a concise skill file. It would benefit enormously from being split into a brief overview with references to topic-specific files, and from adding a clear implementation workflow with validation steps.
Suggestions
Reduce the SKILL.md to a concise overview (~50-80 lines) with a quick-start section and clear references to separate files like ROBOTS.md, SITEMAP.md, META-TAGS.md, CORE-WEB-VITALS.md for detailed templates and code.
Remove explanatory content Claude already knows (e.g., what robots.txt does, what Open Graph is, URL best practices like 'use hyphens not underscores').
Add a clear sequential workflow with validation checkpoints, e.g., '1. Set up robots.txt → 2. Verify with Google robots.txt tester → 3. Generate sitemap → 4. Submit to Search Console and verify indexing → 5. Add meta tags → 6. Validate with Rich Results Test'.
Cut the philosophy section and redundant checklists (there are two overlapping checklists at the end) to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines. Includes extensive explanations Claude already knows (what robots.txt is, what Open Graph is, basic HTML meta tags, URL best practices). Much of this is reference material that could be drastically condensed or split into separate files. The philosophy section and explanatory framing add no actionable value. | 1 / 3 |
Actionability | Highly actionable with complete, executable code examples throughout — Next.js TypeScript implementations for robots.ts, sitemap.ts, metadata, breadcrumbs, redirects, and security headers are all copy-paste ready. HTML templates and configuration files are concrete and specific. | 3 / 3 |
Workflow Clarity | The checklist at the end provides a good summary of what to do, and the content is organized by topic. However, there's no clear sequencing of steps (e.g., 'do robots.txt first, then sitemap, then meta tags'), no validation checkpoints between steps, and no feedback loops for verifying that configurations are correct before proceeding. | 2 / 3 |
Progressive Disclosure | Monolithic wall of content with no references to external files despite being well over 500 lines. Topics like AI crawler handling, structured data, security headers, and Core Web Vitals could each be separate reference files. No bundle files exist to offload this content, and the skill makes no attempt to split or reference supplementary materials. | 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
65efb33
- 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.