CtrlK
BlogDocsLog inGet started
Tessl Logo

translatecom

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/translatecom/SKILL.md
SKILL.md
Quality
Evals
Security

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 a highly actionable, well-structured CLI integration guide with executable commands and a clear state-driven connection workflow, losing points mainly to trimmable explanatory prose and the absence of any reference split for a >50-line skill.

Suggestions

Trim padded prose such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" to tighten token efficiency.

Make step numbering explicit and consistent (label "Step 1: Connect", "Step 2: Discover actions") so the "skip to Step 2" references are unambiguous.

Consider moving the proxy flag table and detailed clientAction field breakdown into a reference file to improve progressive disclosure for this longer skill.

DimensionReasoningScore

Conciseness

Mostly efficient concrete commands, but several sentences are padded ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") and the opening platform description could be trimmed.

3 / 5

Actionability

Provides copy-paste-ready commands across install, login, headless login, connection ensure/wait, action list/run, and a full proxy flag table, covering the common cases fully and executably.

5 / 5

Workflow Clarity

Clear sequence from install through connect-to-run with a state-based polling feedback loop and error recovery (CONFIGURATION_ERROR → check error), though step numbering is slightly loose ("skip to Step 2" without explicit Step labels).

4 / 5

Progressive Disclosure

No bundle files exist; the skill is self-contained with well-organized logical section headers and good structure, though at over 50 lines some detail (clientAction breakdown, proxy flag table) could be split into references.

4 / 5

Total

16

/

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 includes an explicit "Use when" trigger and binds to a distinct named platform, but its capability list is generic ("manage data, records, automate workflows") rather than naming concrete Translate.com actions, which limits specificity and trigger-term richness.

Suggestions

Replace generic verbs with concrete Translate.com capabilities, e.g. "Translate documents and websites, retrieve translation records, and manage translation memory."

Add natural trigger terms users would say, such as "translation", "translate", "languages", or "localized content", alongside "Translate.com".

Tighten the "when" clause to mention concrete objects, e.g. "Use when the user wants to translate text, documents, or websites via Translate.com."

DimensionReasoningScore

Specificity

Names the domain ("Translate.com integration") but the actions ("Manage data, records, and automate workflows") are minimal and generic rather than concrete, matching the anchor for naming the domain with minimal/generic actions.

2 / 5

Completeness

Provides both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Translate.com data"), but the what is generic, keeping it just below the fully concrete anchor.

4 / 5

Trigger Term Quality

Includes the specific natural term "Translate.com" and "data", but misses common variations users would say such as "translation", "translate", or "languages", so coverage has gaps rather than being comprehensive.

3 / 5

Distinctiveness Conflict Risk

Bound to a specific named platform giving it a clear niche with minimal conflict risk, though the generic action verbs create minor overlap with other integration 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.