Name: commercetools
Rating: 52.8 (1 reviews)
Author: membranedev

commercetools

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

Quality

59%

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

Quality

Content

61%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 a concrete, well-structured CLI usage guide with genuinely executable commands and a strong connection-state workflow, but it carries conceptual padding and an inline entity dump, and omits verification steps for its destructive-capable action and proxy operations. Tightening the prose and adding result-validation guidance would raise both conciseness and workflow clarity.

Suggestions

Remove the introductory 'what is Commercetools' paragraph and the bare 27-item entity list (or relocate it to a references file), keeping only guidance Claude cannot infer.

Add a validation/verification step after destructive action runs and proxy writes, e.g. re-fetch the resource or check the response 'output'/'error' field before reporting success, to satisfy the destructive-operations workflow cap.

Standardize the CLI invocation (pick either 'membrane' or 'npx @membranehq/cli') and show how to resolve the CONNECTION_ID placeholder end-to-end to close the actionability gaps.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI command reference, but it pads with concepts Claude already knows ('Commercetools is a headless commerce platform that provides APIs...'), a 27-item entity dump, and filler like 'Use action names and parameters as needed', fitting the 3-anchor 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Provides many copy-paste-ready commands (login, connection ensure, polling, action list/run, proxy) plus a flags table covering common cases, but has minor gaps — mixed 'membrane' vs 'npx @membranehq/cli' invocation and unresolved placeholders (CONNECTION_ID, QUERY) — fitting the 4-anchor 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connection workflow has a clear sequence with state-feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but the destructive-capable action-run and proxy-request steps (POST/PUT/PATCH/DELETE) lack validation/verification, so the destructive-operations cap holds it at 3 rather than the 4-5 its connection sequence would otherwise earn.	3 / 5
Progressive Disclosure	Well-organized single-file sections with clear headers and no nested/buried references, but all reference material (entity list, full command/flag catalog) is inline with no one-level-deep external file split, fitting the 4-anchor 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	14 / 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 correctly answers both what and when and is anchored to a specific platform, but its action verbs are generic and its trigger vocabulary is limited to the brand name with no synonyms. It is functional but could be sharpened with concrete Commercetools operations and richer natural triggers.

Suggestions

Replace generic verbs with concrete Commercetools operations, e.g. 'Manage products, orders, customers, carts, and discount codes' instead of 'Manage data, records, and automate workflows'.

Add natural trigger synonyms users would actually say, such as 'e-commerce', 'headless commerce', 'product catalog', or 'storefront data', beyond just 'Commercetools data'.

Tighten the 'when' clause to name concrete scenarios, e.g. 'Use when the user wants to query or update Commercetools products, orders, or customers via the API'.

Dimension	Reasoning	Score
Specificity	It names the domain ('Commercetools integration') but the actions are generic verbs — 'Manage data, records, and automate workflows' — with no concrete Commercetools-specific operations, matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Commercetools data') are present, but the 'when' trigger is generic rather than concrete, fitting the 4-anchor where 'when could be more explicit or specific' rather than the 5-anchor requiring concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural keyword is the brand 'Commercetools' / 'Commercetools data'; common synonyms (e-commerce, headless commerce, product catalog) and any file/extension terms are absent, so it has 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Commercetools' brand gives it a clear niche, but the generic 'manage data, records, and automate workflows' framing overlaps with sibling Membrane integration skills, so it is 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5-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/commercetools/SKILL.md
Commit: f484c82

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