CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

Quality

86%

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

80%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 dense, highly actionable command reference: every command is executable with exact flags, defaults, and error-recovery actions, and detail is correctly pushed to a complete, well-signaled set of reference files. The main gaps are missing validation checkpoints before batch operations (capped by the rubric) and dated time-sensitive notes scattered outside the Technical Notes section.

Suggestions

Add an explicit validation step before batch operations: for index-batch/inspect-batch, verify the URL file (one URL per line, count against the 200/2,000 limits) and confirm the submission scope with the user before executing.

Consolidate time-sensitive dated information (2026 GSC AI-surfaces notes, GA4 AI Assistants channel launch dates) into a dedicated 'Data caveats by date' or deprecated-changes section alongside the existing Technical Notes, so stale dates are easier to audit.

Break the GSC 'Which flag' guidance into a short bulleted rule list (--property vs --domain vs neither) to replace the current dense run-on paragraph.

DimensionReasoningScore

Conciseness

The body is an efficient command reference with essentially no explanation of concepts Claude already knows — each command gets one script line, defaults, and quota. It is not a 5 because several time-sensitive dated items sit outside the deprecation-style Technical Notes section (the 2026 AI-surfaces blockquotes, the GA4 'AI Assistants' ~2026-05-13 note) and a few passages like the GSC 'Which flag' paragraph are dense run-ons that could be tightened.

4 / 5

Actionability

Every command ships a copy-paste executable invocation with exact flags (e.g. '"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run gsc_query.py --domain <audited-domain> --json'), stated defaults, quotas, a concrete error-scenario/action table, and a fully specified 3-step report workflow. This matches the anchor for fully executable, copy-paste-ready commands covering the common cases.

5 / 5

Workflow Clarity

Sequencing is generally clear — credentials are checked up front with a concrete command, the detected tier is communicated before running, and the error table maps failures to recovery actions. However, the batch operations (inspect-batch at 2,000/day and index-batch submitting up to 200 URLs to Google's Indexing API) have no pre-execution validation or verification steps — no file-content check, URL-count check, or confirm-before-submit loop — which the rubric explicitly caps at 3 for batch/destructive workflows.

3 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview: a quick-reference command table up top, per-family sections, and per-command '**Reference:**' labels pointing to one-level-deep files. All 12 referenced files in references/ and all 3 templates in assets/templates/ exist on disk, and the reference files contain no nested references, matching the anchor for a clear overview with well-signaled one-level-deep references.

5 / 5

Total

17

/

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 that names each Google API with its concrete data outputs and pairs them with an explicit, well-chosen 'Use when' trigger list including abbreviations (GSC, CrUX, CWV). The only weaknesses are a few missing natural trigger variations and slight overlap risk with sibling SEO skills in the same plugin.

DimensionReasoningScore

Specificity

The description enumerates concrete capabilities per API — 'Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic' — and what each returns ('real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends'). This matches the anchor for multiple specific concrete actions with comprehensive coverage; score 4 would require minor coverage gaps that are not present.

5 / 5

Completeness

It explicitly answers both questions: what it does (the API and data list) and when to use it via a concrete trigger clause ('Use when user says "search console", "GSC", ...'). This mirrors the anchor-5 example structure of listing actions followed by explicit 'Use when' trigger phrases; a missing or weak trigger clause would cap it at 3, which does not apply.

5 / 5

Trigger Term Quality

Triggers include natural terms and synonyms users would say: "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data". Coverage is good but a few natural variations are missing — e.g., 'Core Web Vitals' spelled out (only the CWV abbreviation appears) and 'organic traffic' — so it falls between the good (4) and comprehensive (5) anchors, closer to 4.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — Google's own field-data APIs — with specific triggers unlikely to fire for unrelated skills. However, the skill family includes closely related SEO skills (the body references seo-performance and seo-technical, which also handle CWV/Lighthouse data), leaving minor overlap risk with those siblings, which fits the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict anchor at 5.

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

Path

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