CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-google

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

76%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-structured reference body: exact executable commands throughout, clearly signaled one-level-deep references that all exist, and useful defaults, quotas, and error recovery. The main gaps are the missing pre-submit validation for the batch Indexing/Inspection operations (capping workflow clarity) and dated changelog-style blockquotes plus a duplicated rate-limits table that inflate the SKILL.md token budget.

Suggestions

Add a validation step before batch write operations: before '/seo google index-batch <file>', verify the URL list with the user (count, format check, one URL per line) and check remaining quota, since 200-URL submissions are hard to undo and quota-capped at 200/day.

Move the dated 2026 product-change blockquotes (AI surfaces in GSC, GA4 AI Assistants channel, platform properties) into their corresponding files under references/ and keep one-line pointers in SKILL.md — they are reference detail, not command-time guidance.

Replace the inline Rate Limits table with a pointer to references/rate-limits-quotas.md (already cited by '/seo google quotas'), keeping only the per-command quota notes where they are used.

DimensionReasoningScore

Conciseness

The body is dense and reference-style — command tables, exact script invocations, defaults, and quotas — with no explanation of concepts Claude already knows. Minor over-length remains: the long dated blockquotes (AI surfaces in GSC, GA4 AI Assistants channel) and the inline rate-limits table could be trimmed or moved to the existing reference files. Not 5: those sections keep tokens in SKILL.md that references/ already exists to hold; not 3: the padding is minor, not 'some unnecessary explanation' throughout.

4 / 5

Actionability

Every command ships a copy-paste-ready invocation (e.g. '"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run gsc_query.py --property <property> --json'), alongside the config-file schema, per-command defaults, quota numbers, and an error-handling table mapping scenarios to actions. This fully covers the common cases the skill exposes.

5 / 5

Workflow Clarity

The prerequisite flow (credential check -> read references/auth-setup.md) and the numbered report workflow (collect -> save JSON -> generate) are clearly sequenced, with an error-handling table for recovery. However, batch operations — 'index-batch' submits up to 200 URLs and 'inspect-batch' reads a file of URLs — have no pre-submit validation or verification steps (e.g. confirm the URL list or check quota before batch submit), which the rubric says caps workflow clarity at 3.

3 / 5

Progressive Disclosure

A quick-reference command table up top and per-command sections each clearly signaling their reference ('**Reference:** references/search-console-api.md'); all 12 referenced files and all 3 assets/templates files exist and are one level deep. Not 5: the inline rate-limits table duplicates references/rate-limits-quotas.md, and the dated 2026 product-change blockquotes are content that belongs in those reference files rather than the overview.

4 / 5

Total

16

/

20

Passed

Description

88%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: comprehensive, specific, third-person, with an explicit 'Use when' trigger list containing natural phrasings and abbreviations. The only weaknesses are a few missing natural trigger variations and minor overlap risk with sibling SEO/analytics skills on generic terms like 'GA4 organic' and 'field data'.

DimensionReasoningScore

Specificity

The description enumerates concrete capabilities with sub-features — 'Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic' — plus the concrete data delivered (Core Web Vitals, indexation status, search performance, organic traffic trends) in third person, giving comprehensive rather than minor-gap coverage.

5 / 5

Completeness

Explicitly answers both: what ('Google SEO APIs: ... Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends') and when ('Use when user says "search console", "GSC", ...') with concrete trigger phrases — a direct match to the 5 anchor.

5 / 5

Trigger Term Quality

Trigger list ('search console', 'GSC', 'PageSpeed', 'CrUX', 'field data', 'indexing API', 'GA4 organic', 'URL inspection', 'real CWV data') covers natural phrasings and abbreviations well, but omits common variations for commands the skill itself supports, e.g. 'Core Web Vitals' spelled out, 'keyword volume', 'YouTube SEO'. Not 3: coverage is good with only a few natural terms missing, not missing whole synonym groups.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Google's own first-party field data) with distinct triggers like 'GSC', 'CrUX', 'PageSpeed', but 'GA4 organic' and 'field data' are terms sibling SEO/analytics skills (which the body says overlap with this one) would also match, leaving minor overlap risk. Not 5: the description does not disambiguate against those closely related skills.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
AgriciDaniel/claude-seo
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.