CtrlK
BlogDocsLog inGet started
Tessl Logo

crowdin

Crowdin integration. Manage data, records, and automate workflows. Use when the user wants to interact with Crowdin 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

71%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 actionable and well-sequenced with concrete CLI commands and connection-state handling, but it carries minor verbosity and inlines reference material that would benefit from separate files.

Suggestions

Trim the introductory 'what is Crowdin' paragraph and filler lines like 'Use action names and parameters as needed'.

Resolve the membrane vs npx invocation inconsistency and remove the duplicated action-list example.

Move the entity overview and proxy-flag table into separate reference files linked from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete CLI commands, but the opening paragraph explaining what Crowdin is and filler like 'Use action names and parameters as needed' are over-explanation that could be trimmed.

4 / 5

Actionability

It provides concrete, copy-paste-ready membrane commands with flags for login, connection, action listing, running, and proxying; minor gaps come from the duplicated action-list command and inconsistent membrane vs npx invocation.

4 / 5

Workflow Clarity

There is a clear install-auth-connect-search-run sequence with polling checkpoints and state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED), though the 'skip to Step 2' reference points to an unlabeled section, leaving a minor gap.

4 / 5

Progressive Disclosure

The content is sectioned but everything is inlined in one ~150-line file with no bundle references; the entity overview and proxy-flag table are content that could live in separate reference files.

3 / 5

Total

15

/

20

Passed

Description

53%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 names the target platform and includes a 'Use when' clause, but its action language is generic and it omits the natural localization/translation trigger terms users would actually say.

Suggestions

Replace generic verbs with concrete Crowdin capabilities, e.g. 'Manage projects, strings, translations, tasks, and glossaries'.

Add natural trigger terms users say: 'Use when the user wants to localize or translate content, manage translations, or work with Crowdin projects, strings, or tasks'.

Make the 'when' clause more specific than 'interact with Crowdin data' by naming concrete scenarios.

DimensionReasoningScore

Specificity

It names the domain (Crowdin) but the actions "Manage data, records, and automate workflows" are minimal and generic rather than concrete capabilities like translating strings or managing tasks.

2 / 5

Completeness

Both a 'what' (Crowdin integration managing data, records, workflows) and a 'when' ("Use when the user wants to interact with Crowdin data") are present, though the 'when' clause is generic and could be more specific.

4 / 5

Trigger Term Quality

Only "Crowdin" and "Crowdin data" serve as keywords; it misses the natural terms users would actually say such as localization, translation, or translators.

2 / 5

Distinctiveness Conflict Risk

It names a specific platform (Crowdin) giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 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.