CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

site-architecture

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

52

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/site-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

This is a strong, concrete reference of executable templates and tables with good section organization, but it is a monolithic topic catalog rather than a progressive-disclosure skill or a sequenced workflow. Consolidating duplicated templates and splitting domain-specific detail into referenced files would materially reduce token cost. Adding an ordered setup/audit sequence with validation checkpoints would strengthen workflow clarity.

Suggestions

Deduplicate the overlapping content: merge the two robots.txt templates into one, state canonical-URL guidance once, and collapse the final Checklist and Quick Reference sections, which largely repeat each other.

Split domain detail into one-level-deep reference files (e.g. references/ai-bots.md, references/nextjs.md, references/core-web-vitals.md) and keep SKILL.md as a concise overview with clearly signaled links — the ~900-line monolith is the main token-efficiency problem.

Add an ordered implementation or audit workflow with explicit validation steps (e.g. 1. robots.txt -> 2. sitemap -> 3. meta tags -> 4. validate with Rich Results Test and Search Console) instead of the current topic-by-topic catalog.

DimensionReasoningScore

Conciseness

The body is template-driven rather than explanatory (no padding about what robots.txt or SEO is), but it duplicates itself noticeably: two overlapping full robots.txt templates, canonical guidance repeated in 'Essential Meta Tags' and 'Canonical URLs', meta tags shown in both raw HTML and Next.js form, and a final Checklist that largely restates the Quick Reference — fitting 'could be tightened' more than 'minor instances of over-explanation'.

3 / 5

Actionability

Mostly executable, copy-paste-ready guidance: complete robots.txt and XML sitemap templates, working Next.js robots.ts/sitemap.ts/metadata/redirects/headers code, and a full Breadcrumbs component. Minor gaps keep it below 5: getBlogPosts()/getPost() are undefined placeholders and the 'Search Console Setup' block wraps a numbered list in a bash fence rather than runnable commands.

4 / 5

Workflow Clarity

The content is organized by topic rather than as a sequenced process; 'Verification & Submission' offers rough steps and the closing checklist supplies checkpoints, but there is no ordered workflow with explicit validation gates between steps, matching 'sequence present but checkpoints missing or implicit'. Not capped lower since this is configuration generation, not a destructive or batch operation.

3 / 5

Progressive Disclosure

Roughly 900 lines are inlined in SKILL.md with no references/, scripts/, or assets/ bundle at all; content that clearly belongs in separate files (the AI-bot robots reference, Next.js recipes, Core Web Vitals detail) is all inline. Well-labeled ## sections and a final Quick Reference keep it above anchor 2's 'minimal structure', but it is far past the under-50-lines case that would allow a high score without external files.

3 / 5

Total

13

/

20

Passed

Description

61%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 compact and names a clear, concrete technical domain, but it is a noun list rather than a statement of actions and lacks any 'use when' trigger guidance within the description field itself. Keyword coverage is good, with a few obvious synonyms missing. Appending a trigger clause and one or two action verbs would lift the two capped dimensions.

Suggestions

Add an explicit trigger clause to the description, e.g. 'Use when setting up or auditing robots.txt, sitemaps, meta tags, or Core Web Vitals' — the missing 'use when' guidance currently caps completeness at 3 even though a when-to-use field exists in the frontmatter.

State concrete actions rather than only nouns, e.g. 'Configures robots.txt and sitemaps, generates meta tags and structured data, optimizes Core Web Vitals' to move specificity from topic-listing to action-listing.

Include common synonyms users would say ('SEO', 'search engine visibility', 'Open Graph', 'structured data') to broaden trigger-term coverage toward anchor 5.

DimensionReasoningScore

Specificity

Names the domain ('Technical SEO') and four concrete artifacts ('robots.txt, sitemap, meta tags, Core Web Vitals'), but contains no action verbs, so it lists topics rather than the specific actions anchors 4-5 require; the nouns are too concrete for anchor 2's 'minimal or generic'.

3 / 5

Completeness

The description field clearly answers 'what' (the four technical-SEO topic areas) but has no 'Use when...' clause or equivalent trigger guidance, which the rubric explicitly caps at 3; the frontmatter's separate 'when-to-use' field is outside the evaluated description text.

3 / 5

Trigger Term Quality

'robots.txt', 'sitemap', 'meta tags', 'Core Web Vitals', and 'technical SEO' are all natural phrases users would say, matching 'good keyword coverage; a few natural terms missing' — synonyms like 'search engine', 'Open Graph', or 'structured data' are absent, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The specific artifacts (robots.txt, sitemap, Core Web Vitals) carve a mostly distinct technical-SEO niche with only minor overlap risk against a broader SEO or general web-development skill, fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict profile of anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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/maggy

Path

skills/site-architecture/SKILL.md

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.