Name: google-search-console
Rating: 58.4 (1 reviews)
Author: membranedev

google-search-console

Google Search Console integration. Manage Accounts. Use when the user wants to interact with Google Search Console data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/google-search-console/SKILL.md

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.

The content is a strongly actionable, well-structured Membrane CLI guide with a clear connection workflow and explicit error-state handling. Its main weaknesses are an unnecessary introductory explanation of what Google Search Console is and the absence of validation guidance around destructive actions.

Suggestions

Trim or remove the opening paragraph explaining what Google Search Console is — Claude already knows this.

Add a brief validation/confirmation step before destructive actions like delete-site and delete-sitemap (e.g. confirm the site/sitemap with the user or a get-site check first).

Consider moving the full popular-actions table to a separate reference file and keeping only a few representative examples inline, to tighten the overview.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean command-and-table content, but the opening paragraph ("Google Search Console is a web service by Google which allows webmasters to check indexing status...") explains a concept Claude already knows, and the "Agent Types" line is loosely worded.	3 / 5
Actionability	Commands are fully executable and copy-paste ready ("membrane connection ensure", "membrane action run <actionId> --input '{...}'", the proxy flags table), and the popular-actions table covers the common cases concretely.	5 / 5
Workflow Clarity	The connection workflow is a clear sequence with explicit validation (poll until READY, handle CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but destructive actions (delete-site, delete-sitemap) are listed without any verification guidance.	4 / 5
Progressive Disclosure	The body is well-organized under clear section headers with no deep nested references, and there are no bundle files to navigate; the large inline actions table could arguably live in a reference file, which is the main organization gap.	4 / 5
	Total	16 / 20 Passed

Description

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

The description clearly identifies a distinct niche and provides an explicit use-when clause, but it under-specifies capabilities — only the generic "Manage Accounts" is named. Tightening the action list and adding a few synonyms would raise the score.

Suggestions

Replace the generic "Manage Accounts" with several concrete actions (e.g. inspect URLs, submit/list sitemaps, query search analytics, list/add/delete sites).

Add natural synonyms to broaden triggering (e.g. "Search Console", "GSC", "indexing status", "sitemaps").

Keep the explicit "Use when..." clause but make the trigger more specific (e.g. mentioning indexing, search performance, or sitemap management).

Dimension	Reasoning	Score
Specificity	The description names the domain ("Google Search Console integration") but the only named action is the generic "Manage Accounts", with no mention of sitemaps, URL inspection, or search analytics — actions are minimal and generic.	2 / 5
Completeness	It has both a "what" ("Google Search Console integration. Manage Accounts.") and an explicit "when" ("Use when the user wants to interact with Google Search Console data"), though the "what" is thin and the "when" is somewhat generic.	4 / 5
Trigger Term Quality	"Google Search Console" and "interact with Google Search Console data" give a relevant natural trigger, but common variations/synonyms (Search Console, GSC, indexing, sitemaps) are missing.	3 / 5
Distinctiveness Conflict Risk	"Google Search Console integration" carves out a clear, narrow niche with a distinct trigger phrase, creating minimal overlap risk with other skills.	5 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/google-search-console/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.