Name: make-commerce
Rating: 56.8 (1 reviews)
Author: membranedev

make-commerce

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

Quality

65%

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

Quality

Content

67%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 well-structured, highly actionable guide to driving Make Commerce through the Membrane CLI, with strong validation/feedback loops in the connection flow. Its main weaknesses are some marketing-style padding, a redundant actions section, and inconsistent step numbering.

Suggestions

Trim the introductory marketing prose and the filler line 'Use action names and parameters as needed.' to improve token efficiency.

Remove or merge the redundant 'Popular actions' section that re-states the search command from 'Searching for actions'.

Fix the step numbering (label the referenced 'Step 2' and add a '1a') so the multi-step workflow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable CLI commands, but it includes padded marketing prose ('It provides tools for product listing... It is used by small to medium-sized businesses...'), a filler line ('Use action names and parameters as needed.'), and a redundant 'Popular actions' section that repeats the search command already shown.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests with a clear options table, matching 'mostly executable guidance with minor gaps'; placeholders like CONNECTION_ID and QUERY are never shown filled in a worked example.	4 / 5
Workflow Clarity	The connection flow has explicit state-based branching and feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED, handle CONFIGURATION_ERROR), but the overall numbering is loose ('skip to Step 2' with no labeled Step 2, a '1b' without a 1a), leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single self-contained file with clear, well-organized section headers and no nested references; it is monolithic by necessity rather than poorly split, fitting 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	15 / 20 Passed

Description

62%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 what the skill does and when to use it, anchored by a distinctive product name. Its main weakness is generic action verbs that under-specify the e-commerce capabilities the body actually covers.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete e-commerce verbs such as managing products, orders, customers, and payments.

Expand the trigger to mention natural user phrases like 'Make Commerce orders', 'products', or 'store data' to improve keyword coverage.

Add common synonyms/file or entity terms users would actually say so the trigger surfaces for more varied requests.

Dimension	Reasoning	Score
Specificity	It names the Make Commerce domain and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete e-commerce operations (no products, orders, customers, or payments), so it matches 'names domain and 1-2 concrete actions but not comprehensive'.	3 / 5
Completeness	It states both what ('Make Commerce integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Make Commerce data.'), but the 'what' is generic and the single trigger could be more explicit, fitting 'has both what and when; when could be more specific'.	4 / 5
Trigger Term Quality	The product name 'Make Commerce' and the trigger 'interact with Make Commerce data' are relevant, but the supporting keywords ('data', 'records', 'workflows') are generic and common e-commerce synonyms (products, orders, payments) are missing.	3 / 5
Distinctiveness Conflict Risk	The specific product name 'Make Commerce' anchors a clear niche with low conflict risk, though the generic action verbs ('manage data, records, automate workflows') leave minor overlap with general data-integration skills.	4 / 5
	Total	14 / 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/make-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.