Name: google-merchant-center
Rating: 61.6 (1 reviews)
Author: membranedev

google-merchant-center

Google Merchant Center integration. Manage Accounts. Use when the user wants to interact with Google Merchant Center data.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/google-merchant-center/SKILL.md

Quality

Content

71%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 body is highly actionable with real, complete CLI commands and a clear connection workflow, but it opens with unnecessary conceptual padding and inlines a large actions table that belongs in a separate reference file. Step numbering and destructive-action validation have minor gaps.

Suggestions

Move the popular-actions table into a separate references file (e.g., references/actions.md) and link to it, keeping only a few representative examples inline.

Trim the opening overview paragraph and the Membrane-auth editorializing so the body assumes Claude's competence.

Fix the broken step numbering (add the missing '1a' / define 'Step 2') and add a brief validation/confirmation note before destructive actions like delete-product or delete-datafeed.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what Google Merchant Center is and the Membrane-auth platitude ('so you can focus on the integration logic rather than auth plumbing') restate concepts Claude already knows, so it is mostly efficient but includes unnecessary explanation that could be trimmed.	3 / 5
Actionability	Commands are fully executable and copy-paste ready across install, login, connection ensure, polling, action list/run, and proxy, with a complete flag table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow has explicit checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED then re-poll, inspect error fields), but the step numbering is broken ('1b' with no '1a', references an undefined 'Step 2') and destructive actions surfaced in the table lack validation guidance.	4 / 5
Progressive Disclosure	Section headers give the document structure, but the 20-row popular-actions table is bulk reference content inlined into SKILL.md with no separate reference files or signaled external pointers, matching the 'content that should be separate is inline' anchor.	3 / 5
	Total	15 / 20 Passed

Description

73%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 is distinct and includes an explicit 'Use when' trigger, but its capability list is thin ('Manage Accounts') and the trigger phrasing is generic. It is solid but could name more concrete actions and sharper trigger situations.

Suggestions

Replace the generic 'Manage Accounts' with several concrete capabilities (e.g., 'list and update products, manage datafeeds, create promotions, review product approval statuses').

Sharpen the 'Use when' clause with concrete trigger situations (e.g., 'Use when the user wants to list products, check product approval issues, manage datafeeds, or run promotions in Google Merchant Center').

Dimension	Reasoning	Score
Specificity	Names the domain ('Google Merchant Center integration') and one action ('Manage Accounts'), but that single action is generic and coverage is not comprehensive, matching the 1-2 concrete actions anchor rather than the minimal/generic anchor below.	3 / 5
Completeness	Both 'what' ('Google Merchant Center integration. Manage Accounts.') and 'when' ('Use when the user wants to interact with Google Merchant Center data.') are present, but the 'when' trigger is somewhat generic and could be more specific, fitting the both-present-but-could-be-sharper anchor.	4 / 5
Trigger Term Quality	'Google Merchant Center' is precisely the natural phrase a user would say and the 'Use when the user wants to interact with Google Merchant Center data' clause surfaces it well; a few common variations/synonyms are missing, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	'Google Merchant Center' is a uniquely named product niche with a distinct trigger phrase and minimal overlap risk with other skills, matching the clear-niche anchor.	5 / 5
	Total	16 / 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-merchant-center/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.