Name: google-cloud
Rating: 56.8 (1 reviews)
Author: membranedev

google-cloud

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

Quality

65%

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-cloud/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.

A well-structured, actionable integration guide built around concrete Membrane CLI commands and a clearly sequenced connection workflow with state-checking feedback loops. Its main weaknesses are an unnecessary opening paragraph explaining what Google Cloud is and the absence of result-verification guidance for potentially destructive action runs.

Suggestions

Remove or drastically shorten the opening paragraph defining what Google Cloud is — Claude already knows this and it is pure token overhead.

Add an explicit verification/retry step after 'membrane action run' and 'membrane request', since proxy calls and action runs can mutate or delete cloud resources.

Make the 'Popular actions' section actually list representative popular actions (with example command + output) instead of restating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and tables, but opens by explaining that 'Google Cloud is a suite of cloud computing services...infrastructure, platform, and software as a service' — a concept Claude already knows — and includes soft padding like 'so you can focus on the integration logic rather than auth plumbing.'	3 / 5
Actionability	Concrete, copy-paste-ready commands throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure', 'membrane action run') plus a full proxy-flag table, with only minor gaps such as the 'Popular actions' section restating discovery rather than showing a real run with output.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit checkpoints — ensure → check state (READY/BUILDING/CLIENT_ACTION_REQUIRED) → poll --wait → re-poll after the user acts — giving a genuine feedback loop, though the 'Running actions'/'Proxy requests' sections lack any explicit verification of destructive results.	4 / 5
Progressive Disclosure	No bundle files exist, so everything is inline, but the body is well-organized into Overview, Working with Google Cloud, and Best practices sections with clear subsections and no nested references; the inline resource tree and clientAction docs are the only minor organization bloat.	4 / 5
	Total	15 / 20 Passed

Description

62%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 answers both what it does and when to use it with a distinct Google Cloud niche, but the listed capabilities are generic ('manage data, records, automate workflows') and the trigger vocabulary is thin beyond 'Google Cloud'. More concrete service-level actions and synonyms would lift it from good to excellent.

Suggestions

Replace generic verbs with concrete Google Cloud actions, e.g. 'deploy Cloud Functions, manage Storage buckets, query Cloud SQL, run Cloud Build'.

Add common synonyms and service names users say naturally — GCP, BigQuery, Cloud Storage, GCS — to broaden trigger coverage.

Tighten the 'when' clause with specific triggers, e.g. 'Use when the user wants to deploy, query, or manage Google Cloud (GCP) resources.'

Dimension	Reasoning	Score
Specificity	It names the domain ('Google Cloud') and several actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete service-level operations like deploying Cloud Functions or managing storage buckets.	3 / 5
Completeness	Both parts are present — 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Google Cloud data') — but the 'when' clause is generic and could name more concrete triggers.	4 / 5
Trigger Term Quality	The natural keyword 'Google Cloud' is present, but common variations and service-specific terms users actually say (GCP, BigQuery, Cloud Storage, GCS) are missing, leaving only one relevant trigger term.	3 / 5
Distinctiveness Conflict Risk	'Google Cloud integration' carves out a clear niche distinct from other cloud skills, with only minor overlap risk against closely related skills such as Google Workspace or generic cloud-integration skills.	4 / 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-cloud/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.