Name: metasfresh
Rating: 64 (1 reviews)
Author: membranedev

metasfresh

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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/metasfresh/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 highly actionable with copy-paste CLI commands and a solid connection-state feedback loop. Main gaps are a phantom 'Step 2' reference, a padded intro paragraph, and no validation guidance after running actions.

Suggestions

Fix the dangling 'Step 2' reference — either add a labeled '## Step 2: ...' heading or reword the skip instruction to point at the actual section (e.g. 'Searching for actions').

Trim the opening marketing paragraph about metasfresh to one line or move it to a reference; assume Claude knows what an ERP is.

Add a brief validation note after 'Running actions' (e.g. check the `output`/error fields and retry on non-READY or error responses), since action runs and proxy requests can be destructive/batch.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but the opening ERP marketing paragraph ('open-source ERP system that focuses on streamlining business processes...') and lines like 'so you can focus on the integration logic rather than auth plumbing' are mild over-explanation that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get --wait, action list, action run with JSON input, request proxy) plus a flag table covering the common cases.	5 / 5
Workflow Clarity	Clear install→login→connect→discover→run sequence with a genuine feedback loop (poll BUILDING state, handle CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but it references a 'Step 2' that is never labeled and lacks post-action-run validation.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and a self-contained structure; the ~30-item flat entity list is mildly reference-like inline content that could justify a separate file, keeping it just below 5.	4 / 5
	Total	17 / 20 Passed

Description

70%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 has an explicit trigger clause and names a distinct product niche, but its capability list is generic rather than concrete. Tightening the 'what' to specific metasfresh operations would lift specificity and completeness.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete metasfresh operations, e.g. 'Create sales and purchase orders, manage business partners and products, handle shipments and invoices'.

Add a few natural domain synonyms/keywords (ERP, business partners, sales orders, HUs) to broaden trigger-term coverage.

Make the 'when' clause more specific, e.g. 'Use when the user wants to create or query metasfresh ERP records such as orders, business partners, or shipments'.

Dimension	Reasoning	Score
Specificity	Names the domain (metasfresh) and lists actions ('Manage data, records, and automate workflows') but these are generic verbs rather than the concrete, specific operations (e.g. create sales orders, manage HUs) that anchor 4 requires.	3 / 5
Completeness	Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with metasfresh data'); held below 5 because the 'what' is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes a natural trigger phrase ('Use when the user wants to interact with metasfresh data') with the key product term covered, though it omits common domain synonyms (ERP, business partners, orders).	4 / 5
Distinctiveness Conflict Risk	The named product 'metasfresh' gives a clear niche with minimal conflict risk, but the generic 'Manage data, records, and automate workflows' phrasing introduces minor overlap with broad data-management skills.	4 / 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/metasfresh/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.