CtrlK
BlogDocsLog inGet started
Tessl Logo

google-cloud-translate

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

56

Quality

65%

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-translate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 Membrane CLI commands and a well-structured connection workflow including state-based checkpoints. It loses a little conciseness to introductory boilerplate and lacks an explicit validation/retry loop for destructive action runs.

Suggestions

Trim the introductory paragraph defining what Google Cloud Translate is, since Claude already knows this; lead with the integration mechanics.

Add an explicit validate-and-retry step (e.g. check the action run output/errors and re-run with corrected input) for destructive or batch action invocations.

Consider moving the full proxy flag reference table into a separate reference file so the overview stays leaner.

DimensionReasoningScore

Conciseness

The body is mostly efficient, using terse command examples and tables, but it carries some unnecessary explanation Claude already knows (a paragraph defining what Google Cloud Translate is and the line 'so you can focus on the integration logic rather than auth plumbing').

4 / 5

Actionability

It provides copy-paste-ready, fully executable CLI commands with flags, JSON examples, and a clear options table covering the common cases of connecting, searching, running, and proxying actions.

5 / 5

Workflow Clarity

The connection flow is sequenced with explicit state handling and polling checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), which is strong; however there is no explicit validate-and-retry feedback loop for batch or destructive action runs, leaving a minor validation gap.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no bundle files to reference; it is a self-contained overview that navigates well, with only minor inlining of material that could otherwise live separately.

4 / 5

Total

17

/

20

Passed

Description

50%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 names the right service but leans on generic Membrane-integration boilerplate ('Manage data, records, and automate workflows') instead of describing actual translation capabilities. Trigger guidance exists but is vague ('interact with Google Cloud Translate data') and lacks natural user phrasing.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete translate-specific actions such as 'Translate text between languages, detect source language, list supported languages'.

Sharpen the trigger clause to use natural user phrasing, e.g. 'Use when the user wants to translate text, detect a language, or work with Google Cloud Translate.'

Remove boilerplate ('records', 'automate workflows') that dilutes the niche and raises overlap risk with other integration skills.

DimensionReasoningScore

Specificity

The description names the domain ('Google Cloud Translate integration') but the concrete actions are generic boilerplate ('Manage data, records, and automate workflows') rather than translate-specific actions like translating text or detecting languages.

3 / 5

Completeness

There is a 'what' (Google Cloud Translate integration) and a 'Use when' clause ('Use when the user wants to interact with Google Cloud Translate data'), but the 'when' is weak and generic ('interact with data') rather than tied to concrete translation triggers, and the 'what' is diluted by boilerplate.

3 / 5

Trigger Term Quality

It includes 'translate' and 'Google Cloud Translate' which are relevant, but it omits natural user phrases and synonyms such as 'translation', 'translate text', 'languages', or 'localize' that a user would actually say.

3 / 5

Distinctiveness Conflict Risk

'Google Cloud Translate' names a clear niche, but the generic 'Manage data, records, and automate workflows' phrasing overlaps heavily with many other integration skills, so conflict risk remains moderate.

3 / 5

Total

12

/

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.