Name: google-postmaster-tools
Rating: 60 (1 reviews)
Author: membranedev

google-postmaster-tools

Google Postmaster Tools integration. Manage Users, Domains. Use when the user wants to interact with Google Postmaster Tools data.

Quality

70%

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-postmaster-tools/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 body is highly actionable with executable commands and a well-structured connection state-machine, but carries a little product-explanation padding and a couple of placeholder guidance lines that could be tightened.

Suggestions

Cut the intro paragraph explaining what Postmaster Tools is and who uses it — Claude can infer this — and remove the empty "When to use which actions" line.

Either replace "When to use which actions: Use action names and parameters as needed." with concrete guidance mapping intents (e.g. reputation checks, traffic stats) to specific actions, or delete it.

Consider moving the full proxy flag reference table into a separate reference file and keeping only a one-line pointer, to slim the overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-based guidance, but the product-purpose intro ("used by email senders, marketers... This helps ensure their emails reach Gmail inboxes") and filler like "When to use which actions: Use action names and parameters as needed." could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure ...", "membrane action run ... --input '{...}'") with full flag tables and JSON examples covering the common cases.	5 / 5
Workflow Clarity	A clear install → authenticate → connect → poll-for-ready → search → run sequence exists with explicit state polling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but "When to use which actions: Use action names and parameters as needed." leaves a minor guidance gap.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no broken or nested references, all self-contained in SKILL.md; at ~140 lines it exceeds the simple-skill threshold, so it earns good-but-not-perfect structure rather than a 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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 its niche and includes both a 'what' and a 'when', but its trigger phrasing is circular and its action list is generic and incomplete relative to the body.

Suggestions

Replace the circular trigger with concrete natural phrases, e.g. 'Use when the user wants to check email deliverability, spam rate, or sender reputation in Gmail Postmaster Tools.'

Expand "Manage Users, Domains" to name the actual capabilities (e.g. retrieve traffic stats, list/inspect registered domains) so the action list matches what the body offers.

Add common synonyms/file terms (deliverability, email reputation, spam rate, Gmail inbox) so the trigger matches how users actually phrase the request.

Dimension	Reasoning	Score
Specificity	"Manage Users, Domains." names the domain plus 1-2 concrete actions, but the verb "Manage" is generic and omits the traffic-stats capabilities the body actually covers, so it is not comprehensive.	3 / 5
Completeness	It has both a 'what' ("Manage Users, Domains") and a 'when' ("Use when the user wants to interact with Google Postmaster Tools data"), but the 'when' is generic rather than a concrete trigger phrase, so it stops short of a 5.	4 / 5
Trigger Term Quality	The only triggers are the product name ("Google Postmaster Tools") and the circular phrase "interact with Google Postmaster Tools data"; natural synonyms like deliverability, email reputation, spam rate, or Gmail inbox are missing.	3 / 5
Distinctiveness Conflict Risk	It names a specific Google product ("Google Postmaster Tools") with a clear niche and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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-postmaster-tools/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.