CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-web-performance

Audits, fixes, and optimizes modern web applications for search engine optimization (SEO) and Core Web Vitals performance. Use when implementing meta tags, Open Graph, structured data (JSON-LD), XML sitemaps, robots.txt, asset delivery optimization (images, fonts, critical CSS, code splitting, compression), Lighthouse audits, or diagnosing and resolving LCP, INP, and CLS bottlenecks.

69

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced playbook with executable commands and templates throughout and a proper verification section, backed by a real one-level-deep reference for deep CWV diagnostics. Its main cost is length: sections re-teaching semantics/accessibility basics and bulky inline templates make it heavier than an ideal overview.

Suggestions

Trim Step 5 (semantic HTML) and Step 8 (touch targets) down to SEO-specific guidance only — Claude already knows heading hierarchy, landmark tags, alt-text rules, and 48px tap-target minimums.

Compress the meta-tag example by showing the primary tags once and noting 'duplicate title/description as og:title/og:description and twitter:*' instead of repeating identical strings inline; move the full sitemap XML pair and nginx config into a reference file.

Add an explicit feedback loop to the Verification section, e.g. 'If Lighthouse performance < 90 or LCP > 2.5s, revisit steps 6–9 and re-run the audit' to close the remediation cycle.

DimensionReasoningScore

Conciseness

The body is mostly efficient, code-dense templates, but several sections explain concepts Claude already knows: the Step 5 semantic HTML checklist (single <h1>, sequential headings, landmark tags, alt-text rules), Step 8 touch-target sizing, and the generic intro paragraph. The OG/Twitter block also repeats identical title/description strings inline. It fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 2, since the padding is limited to a few sections amid largely actionable content.

3 / 5

Actionability

Nearly everything is executable and copy-paste ready: Lighthouse CLI invocations with flags, curl header checks, complete nginx compression/caching config, full meta-tag and JSON-LD templates, responsive image markup, and a verification Node script that parses the audit report. This matches the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The nine steps are clearly sequenced (baseline audit → crawling config → metadata → structured data → semantics → media → rendering path → internal links → CWV remediation) and a dedicated Verification section provides concrete checkpoints. It falls short of level 5 because there is no explicit feedback loop (e.g., 'if performance < 90, revisit steps 6–9 and re-run Lighthouse') connecting verification results back to remediation.

4 / 5

Progressive Disclosure

The single bundle reference (references/core-web-vitals.md, verified to exist) is well signaled and exactly one level deep: 'For comprehensive diagnostic scripts, attribution hooks, and step-by-step remediation patterns, refer to [Core Web Vitals Reference](references/core-web-vitals.md)'. However, the 490-line body inlines large templates (full sitemap XML pairs, nginx blocks, complete OG/Twitter duplication) that partially belong in reference files, so it fits 'most content appropriately placed; minor organization gaps' rather than the cleanly split level-5 anchor.

4 / 5

Total

16

/

20

Passed

Description

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

A strong description: third-person, concise, with an explicit 'Use when' clause covering the full range of triggers from crawling config to Core Web Vitals remediation. The only weakness is a handful of missing natural synonyms users might say, such as 'page speed' or 'search ranking'.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions ('Audits, fixes, and optimizes', 'implementing meta tags, Open Graph, structured data (JSON-LD), XML sitemaps, robots.txt, asset delivery optimization... Lighthouse audits, or diagnosing and resolving LCP, INP, and CLS bottlenecks') with comprehensive coverage of the skill's domain. It matches the anchor for multiple specific concrete actions; the level-4 'minor gaps' anchor is a worse fit since the enumeration is extensive.

5 / 5

Completeness

It explicitly answers both questions in third person: the 'what' ('Audits, fixes, and optimizes modern web applications for search engine optimization (SEO) and Core Web Vitals performance') and the 'when' ('Use when implementing... or diagnosing and resolving LCP, INP, and CLS bottlenecks') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Keyword coverage is strong and natural — 'SEO', 'Core Web Vitals', 'meta tags', 'robots.txt', 'XML sitemaps', 'JSON-LD', 'Lighthouse', 'LCP, INP, and CLS' — including both acronyms and full forms. A few common user phrasings are missing ('page speed', 'site speed', 'search ranking', 'rich results'), so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The technical-SEO / Core Web Vitals niche is clear and the triggers (JSON-LD, sitemaps, robots.txt, Lighthouse, LCP/INP/CLS) are specific enough that it would rarely fire for an unrelated skill. This matches the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

administrakt0r/pro-skills-repo-administraktor

Path

skills/seo-performance-skills/seo-web-performance/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.