Name: weglot
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

weglot

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

Quality

70%

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

Quality

Content

82%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 strong, executable integration guide with concrete commands, a clear operational sequence, and a genuine validation feedback loop for connection state. Its main weaknesses are minor over-explanation, slightly inconsistent step numbering, and an all-inline structure that forgoes progressive disclosure.

Suggestions

Fix the step numbering inconsistency: either label the connect step "Step 1"/"Step 2" explicitly or stop referencing an undefined "Step 2".

Trim the introductory "Weglot is a SaaS app..." paragraph and the "auth plumbing" aside so the body leads with action.

Consider moving the detailed clientAction field schema and the proxy flag table into a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands and a tight flag table, with only minor over-explanation such as the introductory "Weglot is a SaaS app..." sentence and "so you can focus on the integration logic rather than auth plumbing".	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands across the common cases (install, login, connection ensure, action list/run, request) plus a comprehensive flag table; placeholders like CONNECTION_ID are necessary, not gaps.	5 / 5
Workflow Clarity	A clear install → authenticate → connect → search → run sequence exists with an explicit feedback loop for connection readiness (poll BUILDING, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll), but step labels are loose ("Step 2" is referenced while the section is titled "1b").	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers in a single self-contained file with no bundle references, which is good structure; at ~140 lines some inline material (e.g. the proxy flag table, the detailed clientAction schema) could optionally live in a reference file, leaving minor organization gaps.	4 / 5
	Total	17 / 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 pairs a what-clause with an explicit Use-when trigger and is anchored to a distinctive product name, but its action list is generic SaaS boilerplate rather than Weglot-specific capabilities. Tightening the verbs to reflect translation workflows would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Weglot capabilities, e.g. "Manage translation projects, languages, and translated resources" instead of "Manage data, records, and automate workflows".

Add natural user trigger phrases such as "translate a website", "add languages", or "review Weglot translations" so the skill matches how users actually ask.

Keep the existing third-person voice and Use-when clause, but make the trigger clause specific to translation/multilingual intent rather than "interact with Weglot data".

Dimension	Reasoning	Score
Specificity	Names the Weglot domain but the listed actions — "Manage data, records, and automate workflows" — are generic verbs that apply to nearly any SaaS rather than concrete Weglot capabilities like translation projects or language management.	2 / 5
Completeness	Both "what" (Weglot integration; manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Weglot data") are present, but the trigger clause is generic rather than concrete phrases.	4 / 5
Trigger Term Quality	Includes the distinctive product keyword "Weglot" and the phrase "interact with Weglot data", but misses the natural translation-related terms a user would actually say (e.g. "translate my site", "Weglot translation", "add languages").	3 / 5
Distinctiveness Conflict Risk	The named product "Weglot" gives it a clear, mostly-distinct niche with minimal conflict risk, though the generic action verbs leave minor overlap with other data-integration skills.	4 / 5
	Total	13 / 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/weglot/SKILL.md
Commit: f484c82

Reviewed: 3 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.