Name: medusa-commerce
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

medusa-commerce

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

Quality

64%

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

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 highly actionable with executable CLI commands, clear flag reference, and a well-branched connection workflow with feedback loops. It is held back by mild verbosity (a redundant intro and duplicated action-list section) and a monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Remove or trim the introductory 'Medusa Commerce is an open-source, headless commerce platform...' paragraph and merge the redundant 'Popular actions' section into 'Searching for actions' to reduce token overhead.

Fix the step labeling: the body references 'Step 2' and '1b' without a labeled Step 1/Step 2, so renumber the connection sequence consistently.

Consider moving the detailed connection-state machine and the proxy request flag table into a separate reference file (e.g. references/connections.md) and linking from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference, but includes some unnecessary explanation such as the introductory 'Medusa Commerce is an open-source, headless commerce platform...' paragraph and a 'Popular actions' section that duplicates the earlier 'Searching for actions' command, matching the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor.	3 / 5
Actionability	The content provides copy-paste ready commands throughout (install, login, connection ensure/get, action list/run, request) with a clear flag-options table and concrete JSON-input examples covering the common cases, matching the 'fully executable; copy-paste ready code or commands; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state-based branches (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a feedback loop (re-poll after the user completes the action), matching 'clear sequence with most checkpoints present'; minor gaps include a 'Skip to Step 2' reference with no labeled Step 1/Step 2.	4 / 5
Progressive Disclosure	The skill is a single ~158-line file with no bundle files and no external references; section headers provide structure, but heavier reference material (the detailed connection-state machine and the proxy flag table) is inlined in SKILL.md rather than split into separate files, matching the 'some structure but could be better organized; content that should be separate is inline' anchor.	3 / 5
	Total	15 / 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 cleanly states both what the skill does and when to use it, anchored to a distinct named platform. Its main weakness is generic action verbs ('manage data, records, automate workflows') that lack concrete, specific capabilities and natural trigger synonyms.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Create and update orders, products, customers, and fulfillments; search and run Medusa Commerce actions via the Membrane CLI.'

Add natural trigger terms users would say, such as 'online store', 'e-commerce', 'headless commerce', 'orders', or 'products', alongside 'Medusa Commerce data'.

Expand the 'Use when' clause to list concrete scenarios (e.g. managing orders/products, automating store workflows) rather than only 'interact with Medusa Commerce data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Medusa Commerce integration') but its actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete capabilities like creating orders or updating products, matching the 'names domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Medusa Commerce data') are present and explicit, though the 'when' clause could name more concrete trigger phrases, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Medusa Commerce' and 'interact with Medusa Commerce data' give some relevant keywords, but common natural variations a user might say ('online store', 'e-commerce', 'orders', 'products', 'headless commerce') are missing, matching the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the specific named platform 'Medusa Commerce' gives it a clear niche with minimal conflict risk against unrelated skills, though the generic 'manage data, records, automate workflows' phrasing leaves minor overlap risk with other commerce integrations, matching the 'mostly distinct; minor overlap risk' anchor.	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/medusa-commerce/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.