CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commercetools

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/commercetools/SKILL.md
SKILL.md
Quality
Evals
Security

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 body delivers strong executable guidance: complete CLI commands, connection lifecycle states with feedback loops, and a proxy fallback. Its weaknesses are the padded conceptual intro and entity-list filler that add tokens without new information, plus a dangling "Step 2" reference that slightly muddies the workflow.

Suggestions

Cut the "Commercetools is a headless commerce platform..." intro paragraph and the "Use action names and parameters as needed." filler — Claude already knows what Commercetools is.

Fix the dangling "skip to **Step 2**" references by naming or numbering the target section (e.g. "Searching for actions").

Move the 26-item entity taxonomy and the proxy flag table into a references/ file (e.g. ENTITIES.md) and keep a one-line pointer in SKILL.md.

DimensionReasoningScore

Conciseness

The intro paragraph ("Commercetools is a headless commerce platform... It's used by businesses who want flexible and scalable solutions") explains concepts Claude already knows, and "Use action names and parameters as needed." is filler; the rest is mostly efficient CLI instruction.

3 / 5

Actionability

Concrete copy-paste commands throughout (install, login, connection ensure, action list/run with --input, proxy flag table). Not a 5 because there is no worked example with a real action and input payload, and `membrane login --tenant --clientName=<agentType>` shows a flag with no value.

4 / 5

Workflow Clarity

Clear sequence (install → authenticate → connection ensure → poll state → search actions → run → proxy fallback) with state-based checkpoints and error-state handling (READY / CLIENT_ACTION_REQUIRED with re-poll / CONFIGURATION_ERROR). Not a 5 because "skip to **Step 2**" references a step that is never defined, leaving a dangling reference in the flow.

4 / 5

Progressive Disclosure

No bundle files exist, and the single SKILL.md is organized into clear, well-placed sections at its size. Not a 5 because the 26-item entity taxonomy and the proxy flag table are inline content that would sit better in a reference file.

4 / 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 correctly names the domain and includes an explicit 'Use when' clause, satisfying basic completeness. However, its capability statement is generic and it misses the natural trigger vocabulary (e-commerce, storefront, orders, products) that would make it reliably surfaced.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete Commercetools capabilities, e.g. "Query and update products, orders, carts, customers, and discounts via the Commercetools API".

Expand the 'Use when' clause with natural trigger phrases: "Use when the user mentions Commercetools, e-commerce data, storefront products, orders, or carts".

Avoid generic verbs like "manage data" that could collide with other data-integration skills; anchor every action to a Commercetools resource.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the domain but the actions are generic — no concrete Commercetools capabilities (products, orders, carts, discounts, subscriptions) are stated.

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; the 'what' is vague and the 'when' lacks concrete trigger phrases, so not a 5.

4 / 5

Trigger Term Quality

"Commercetools" and "Commercetools data" are relevant keywords, but natural variations users would say (e-commerce, storefront, products, orders, carts) are missing.

3 / 5

Distinctiveness Conflict Risk

The Commercetools name carves a clear niche with minimal conflict risk, but the broad phrasing ("manage data", "automate workflows") leaves minor overlap with generic data-integration skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill