CtrlK
BlogDocsLog inGet started
Tessl Logo

google-search-console

When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.

68

Quality

82%

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

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 well-structured, action-oriented analysis skill that provides concrete report locations, benchmark tables, and clear investigation workflows without over-explaining basics. The main gaps are a full API call example and slightly more explicit validation checkpoints in its workflows.

Suggestions

Add one copy-paste-ready searchanalytics.query API call example (request body + pagination loop) to lift actionability from concrete guidance to fully executable.

Make validation checkpoints explicit in the Investigation and Low-CTR workflows (e.g., a labeled 'Verify' step confirming the metric shift before acting) to push workflow_clarity toward 5.

Tighten the 'Indexed vs Not indexed are complementary' and CTR-benchmark prose into tighter table/bullet form to remove the remaining minor verbosity.

DimensionReasoningScore

Conciseness

The body is dense with actionable tables and assumes Claude's competence (no padding explaining what GSC or CTR is), with only minor over-explanation that could be trimmed, fitting anchor 4 better than the leaner 5 or the noticeably verbose 3.

4 / 5

Actionability

Concrete report locations, a CTR-by-position benchmark table, a copy-paste regex, named API method (searchanalytics.query), and hard limits (50,000 rows) give mostly executable guidance with minor gaps such as no full API call example, matching anchor 4.

4 / 5

Workflow Clarity

Numbered Investigation and Low-CTR-Optimization workflows, decision checkpoints ("Quick check," "Decide"), and a Monthly Audit Checklist provide a clear sequence with most checkpoints present; this is a read/analysis skill so the destructive-cap does not apply, anchoring at 4 rather than 5 due to a few implicit checkpoints.

4 / 5

Progressive Disclosure

No bundle files exist; the body is well-organized into numbered report sections and clear headers (Scope, API, Checklist, Output Format, Related Skills) with one-level cross-skill references, fitting anchor 4 with minor splitting possible rather than the no-bundle anchor 5 which assumes under 50 lines.

4 / 5

Total

16

/

20

Passed

Description

90%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 with excellent trigger-term coverage, explicit use-when guidance, and clear boundary routing to sibling skills. The only weakness is that the "what" actions are somewhat high-level rather than an enumerated, comprehensive capability list.

DimensionReasoningScore

Specificity

Names the GSC domain plus a few concrete actions ("analyze Google Search Console data, use the GSC API, or interpret search performance") but the actions are high-level and not a comprehensive list, matching anchor 3 rather than 4.

3 / 5

Completeness

Explicitly answers both "what" (analyze/interpret GSC data, use the API) and "when" with a rich "Use when the user mentions..." clause listing concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural user terms including synonyms ("GSC," "Search Console"), report names ("indexing report," "Core Web Vitals," "Insights report"), metrics ("impressions," "CTR," "average position"), and the technical API name "searchanalytics.query," matching the anchor 5 example.

5 / 5

Distinctiveness Conflict Risk

Clearly scoped to Google Search Console with distinct triggers and explicit boundary routing to title-tag and meta-description for rewrite tasks, giving minimal conflict risk per anchor 5.

5 / 5

Total

18

/

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
kostja94/marketing-skills
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.