Query Google Search Console for SEO data - search queries, top pages, CTR opportunities, URL inspection, and sitemaps. Use when analyzing search performance, finding optimization opportunities, or checking indexing status.
89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that follows best practices. It uses third person voice, lists specific capabilities, includes natural trigger terms that SEO practitioners would use, and explicitly states both what the skill does and when to use it. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'search queries, top pages, CTR opportunities, URL inspection, and sitemaps' - these are distinct, actionable capabilities within the SEO domain. | 3 / 3 |
Completeness | Clearly answers both what ('Query Google Search Console for SEO data - search queries, top pages, CTR opportunities, URL inspection, and sitemaps') AND when ('Use when analyzing search performance, finding optimization opportunities, or checking indexing status'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'SEO data', 'search queries', 'CTR', 'indexing status', 'search performance', 'optimization opportunities', 'Google Search Console', 'sitemaps' - good coverage of terms SEO practitioners use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Google Search Console with distinct triggers like 'GSC', 'CTR opportunities', 'URL inspection', 'indexing status' - unlikely to conflict with general analytics or other SEO tools. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill with excellent conciseness and copy-paste ready commands. The main weaknesses are the lack of error handling/validation guidance for API operations and missed opportunities for progressive disclosure to detailed documentation or troubleshooting guides.
Suggestions
Add a troubleshooting section or validation steps for common failures (e.g., authentication errors, property access issues, rate limits)
Include example output snippets so Claude knows what successful responses look like
Consider linking to a separate TROUBLESHOOTING.md or REFERENCE.md for detailed API error codes and edge cases
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information. No explanations of what GSC is or how OAuth works - assumes Claude's competence. Every section serves a clear purpose. | 3 / 3 |
Actionability | All commands are fully executable with copy-paste ready bash commands. Includes specific flags, paths, and example values. The commands are complete and immediately usable. | 3 / 3 |
Workflow Clarity | Commands are clearly listed but there's no validation or error handling guidance. For operations like URL inspection or sitemap checks, there's no feedback loop for handling failures or verifying results. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file. The 'SEO Use Cases' section could link to detailed guides, and there's no reference to where the underlying Python script documentation lives. | 2 / 3 |
Total | 10 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Table of Contents
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.