Name: tolgee
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

tolgee

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

Quality

59%

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

Quality

Content

61%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 content is highly actionable with concrete, copy-paste Membrane CLI commands and a well-structured connection state machine, but it carries some promotional filler and redundant action-list sections, shows generic rather than Tolgee-specific examples, and omits verification checkpoints for destructive data operations.

Suggestions

Trim the opening Tolgee marketing paragraph to one functional sentence and merge the redundant 'Searching for actions' and 'Popular actions' sections.

Add 1-2 Tolgee-specific action examples (e.g. listing keys or fetching translations) so the executable guidance reflects the actual domain.

Add a verification checkpoint after running actions, e.g. re-query the affected project/keys to confirm destructive or batch changes succeeded.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening Tolgee intro paragraph ('Tolgee is an open-source platform for localization...') and its marketing line ('It's used by companies and developers looking to streamline...') explain/promote the app rather than instruct, and the 'Searching for actions' and 'Popular actions' sections redundantly restate the action-list command.	3 / 5
Actionability	It provides copy-paste ready commands for install, login, connection ensure/get, action list/run, and proxy requests plus a flags table, but the examples are generic Membrane CLI patterns rather than Tolgee-specific actions, leaving a minor gap in concrete domain examples.	4 / 5
Workflow Clarity	The connection setup is well sequenced with a state machine and feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but running actions on translation data is potentially destructive/batch and lacks post-action verification steps, so the destructive-operations cap holds it at 3.	3 / 5
Progressive Disclosure	The body is organized into clear, well-labeled sections with no nested or broken references (and no bundle files exist to reference), but it is a monolithic ~157-line document where the detailed connection state machine and proxy flags could be split out, plus minor redundancy between action sections.	4 / 5
	Total	14 / 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 successfully pairs a 'what' with an explicit 'Use when' trigger and anchors on the distinctive Tolgee name, but its action language is generic boilerplate rather than concrete localization operations and it omits the natural trigger vocabulary (translations, localization, i18n).

Suggestions

Replace generic actions with concrete Tolgee operations, e.g. 'Manage Tolgee projects, languages, keys, and translations'.

Add natural trigger terms users would say, such as 'translations', 'localization', or 'i18n', to the 'Use when' clause.

Make the 'when' more specific, e.g. 'Use when the user wants to manage translations or localization data in Tolgee'.

Dimension	Reasoning	Score
Specificity	The description names the Tolgee domain but its actions are generic ('Manage data, records, and automate workflows') rather than concrete Tolgee operations like managing translations, keys, or languages; this matches the 'names domain but actions are minimal or generic' anchor and falls short of listing 1-2 concrete actions.	2 / 5
Completeness	Both a 'what' ('Tolgee integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Tolgee data.') are present, matching the anchor for having both with the 'when' able to be more specific; it is not a 5 because the trigger phrases lack concrete specificity.	4 / 5
Trigger Term Quality	It includes the core natural keyword 'Tolgee' and 'Tolgee data' in the trigger, but misses the common vocabulary users would actually say such as 'translations', 'localization', or 'i18n', so it has relevant keywords with missing synonyms rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	The named 'Tolgee' app gives it a clear, mostly-distinct niche with minimal conflict risk, though the generic 'manage data, records, automate workflows' boilerplate overlaps with sibling Membrane integration skills, keeping it just below a 5.	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/tolgee/SKILL.md
Commit: f484c82

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