Name: memsource
Rating: 58.4 (1 reviews)
Author: membranedev

memsource

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

Quality

67%

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

Quality

Content

68%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 a tight, actionable CLI guide with good section structure and executable commands. Its main weaknesses are a broken step numbering scheme ('Step 2' / '1b') and absent verification checkpoints after action execution.

Suggestions

Fix the workflow numbering: define and label 'Step 2' explicitly (or renumber '1b' / 'Searching for actions' as a coherent sequence) so 'skip to Step 2' resolves.

Add a verification/check step after running actions or proxy requests (e.g., inspect the `output` field and confirm expected state) to raise workflow clarity.

Trim the marketing-style intro and 'so you can focus on the integration logic' padding to push conciseness toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient copy-paste CLI commands with little concept over-explanation; minor padding like the marketing-style intro ('It's used by translation agencies...') and 'so you can focus on the integration logic' keeps it just below a 5.	4 / 5
Actionability	Concrete executable commands cover install, login, connection setup, action search/run, and proxying with a clear flag table; minor gaps (undefined placeholders like 'Step 2' and generic 'QUERY' intent) keep it from a 5.	4 / 5
Workflow Clarity	The connection flow has polling feedback loops and state checks, but 'skip to Step 2' references a Step 2 that is never labeled, numbering jumps ('1b'), and there is no verification step after running actions; the broken sequence and missing checkpoints fit the 3 anchor.	3 / 5
Progressive Disclosure	The single self-contained file is well-organized with clear section headers and no nested references; with no bundle files to split out, structure is good but not a 5 because some bulk (e.g., the proxy flag table, action reference) could live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

66%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 names a distinct service, giving it strong distinctiveness. It is held back by generic action language and thin keyword coverage that limit specificity and trigger-term quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Memsource capabilities such as projects, jobs, translation memories, and term bases.

Add natural trigger variations users would actually say, e.g. 'Use when the user wants to manage Memsource projects, jobs, translation memories, or term bases.'

Keep the explicit 'Use when...' clause but pair it with more specific nouns so completeness can reach the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain ('Memsource integration') and a couple actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; not a 4 because coverage is neither specific nor comprehensive.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Memsource data') are present; not a 5 because the 'what' is generic and lacks concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural keyword 'Memsource' appears and the trigger phrase references 'interact with Memsource data', but it lacks common variations, synonyms, or related phrasings users might say; not a 4 because keyword coverage is thin.	3 / 5
Distinctiveness Conflict Risk	Naming the specific service 'Memsource' gives it a clear niche with minimal conflict risk against other skills; the generic action verbs do not meaningfully raise overlap risk.	5 / 5
	Total	15 / 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/memsource/SKILL.md
Commit: f484c82

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