Name: google-address-validation
Rating: 53.6 (1 reviews)
Author: membranedev

google-address-validation

Google Address Validation integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Address Validation data.

Quality

60%

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-address-validation/SKILL.md

Quality

Content

67%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 a well-structured, actionable guide with concrete CLI commands and a clear connection lifecycle workflow including state-based checkpoints. It is somewhat verbose in its introductory framing, and the proxy/flag reference material could be offloaded to a reference file.

Suggestions

Trim the opening overview paragraph and the 'so you can focus on the integration logic rather than auth plumbing' padding; Claude knows what auth plumbing is.

Add an explicit post-run validation step (e.g. check the `output`/`error` field and retry on failure) to close the feedback loop for batch or repeated action runs.

Consider moving the proxy request flag table into a references file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with concrete CLI commands, but it pads with explanations Claude doesn't need, e.g. the opening 'Google Address Validation is a service that validates and standardizes postal addresses...' and 'so you can focus on the integration logic rather than auth plumbing'.	3 / 5
Actionability	It provides concrete, executable `membrane` commands throughout with `--json` flags and example invocations, with only minor gaps like the unfilled CONNECTION_ID placeholder.	4 / 5
Workflow Clarity	The install → auth → connection → poll-state → search-actions → run sequence is clear, with checkpoints for READY/BUILDING/CLIENT_ACTION_REQUIRED and error states; it lacks an explicit re-validation feedback loop after running an action.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no nested references, and no bundle files exist to split further; structure is good though some inline reference material (the proxy flag table) could live in a reference file.	4 / 5
	Total	15 / 20 Passed

Description

53%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 functional and includes an explicit 'Use when' trigger, but the capability list is generic boilerplate ('Manage data, records, and automate workflows') rather than concrete address-validation actions. Trigger terms are narrow, missing natural synonyms.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions like 'Validate postal addresses, standardize address components, and verify deliverability'.

Expand trigger terms to include natural phrasings users say, e.g. 'when the user wants to validate or verify an address, standardize postal addresses, or check address deliverability'.

Drop the generic data-management phrasing to reduce overlap with other integration skills and sharpen the skill's niche.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Google Address Validation integration') but its only stated actions are generic ('Manage data, records, and automate workflows'), with no concrete address-specific capabilities.	2 / 5
Completeness	It states both what it does ('Google Address Validation integration') and when to use it ('Use when the user wants to interact with Google Address Validation data'), with the 'when' explicit though somewhat broad.	4 / 5
Trigger Term Quality	It surfaces the natural keyword 'Google Address Validation' but lacks synonyms, related phrasings (e.g. 'validate address', 'verify postal address'), or file-format cues that users would actually say.	3 / 5
Distinctiveness Conflict Risk	The named Google Address Validation niche narrows it, but the generic 'Manage data, records, and automate workflows' phrasing could overlap with other data-integration skills.	3 / 5
	Total	12 / 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-address-validation/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.