CtrlK
BlogDocsLog inGet started
Tessl Logo

google-cloud-api-gateway

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

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/google-cloud-api-gateway/SKILL.md
SKILL.md
Quality
Evals
Security

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 strongly actionable, well-structured CLI guide with good feedback loops in the connection workflow; its main weaknesses are a padded introductory paragraph and inconsistent step numbering.

Suggestions

Remove or trim the opening paragraph that defines what Google Cloud API Gateway is, since Claude already knows this.

Fix the step numbering so referenced "Step 2" exists and "1b" has a corresponding labeled step.

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

DimensionReasoningScore

Conciseness

The body is mostly command-focused and efficient, but the opening paragraph explaining what Google Cloud API Gateway is ("lets developers create, secure, and manage APIs...") restates a concept Claude already knows.

3 / 5

Actionability

It provides concrete, copy-paste-ready CLI commands for install, auth, connect, search, run, and proxy, with only minor gaps such as unreplaced CONNECTION_ID placeholders.

4 / 5

Workflow Clarity

The connect flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, though step numbering is inconsistent ("Step 2" is referenced but unlabeled, "1b" has no "1a").

4 / 5

Progressive Disclosure

Content is well organized into clearly headed sections with no nested references; everything is inline since no bundle files exist, which is appropriate for this length, though the proxy flags table could live in a reference file.

4 / 5

Total

15

/

20

Passed

Description

57%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 correctly uses third person and provides an explicit use-when trigger tied to a specific product, but its capability verbs are generic rather than concrete API Gateway operations.

Suggestions

Replace generic verbs with concrete API Gateway actions, e.g. "Create and manage gateways, configs, and API operations".

Add natural synonyms users might say, such as "APIs", "endpoints", or "GCP API Gateway".

Tighten the trigger clause to mention concrete scenarios like deploying or securing APIs.

DimensionReasoningScore

Specificity

The description names the domain ("Google Cloud API Gateway") but the actions "Manage data, records, and automate workflows" are generic rather than concrete API-gateway operations like creating gateways or deploying configs.

2 / 5

Completeness

Both a "what" (integration, manage data/records/workflows) and an explicit "when" ("Use when the user wants to interact with Google Cloud API Gateway data") are present, though the what could be more specific.

4 / 5

Trigger Term Quality

It includes the natural product name "Google Cloud API Gateway" and a usable trigger phrase, but lacks common synonyms or variations users might say.

3 / 5

Distinctiveness Conflict Risk

Naming a specific Google product gives it a clear niche with distinct triggers, though the generic action verbs create minor overlap risk with other data-management skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.