Name: demandware
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

demandware

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

Quality

66%

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

Quality

Content

75%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 highly actionable CLI guide with concrete commands and a well-validated connection workflow, weakened only by a redundant intro/duplicate section and broken step-numbering labels. It is a strong, copy-paste-ready skill body.

Suggestions

Remove or trim the opening 'Demandware, now Salesforce Commerce Cloud, is a cloud-based platform...' paragraph since Claude already knows the platform.

Delete the redundant 'Popular actions' section that repeats the `action list` command already shown under 'Searching for actions'.

Fix the broken step references: replace 'skip to Step 2' with a real '## Step 2' anchor and relabel '#### 1b' into the numbered sequence.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient concrete commands, but the intro ('Demandware, now Salesforce Commerce Cloud, is a cloud-based platform for e-commerce...') over-explains a platform Claude already knows, and the 'Popular actions' section duplicates the `action list` command already shown under 'Searching for actions', matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	The body is fully executable: copy-paste commands for install (`npm install -g @membranehq/cli@latest`), login, `connection ensure`, `action run` with `--input` JSON, `membrane request`, plus a complete proxy-flags table, covering the common cases per the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	There is a clear install→auth→connect→search→run sequence with validation checkpoints (polling connection state, branching on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the step labelling is broken ('skip to Step 2' with no Step 2, and a lone '#### 1b'), fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	The single-file skill is organized into clear, well-signaled sections (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references and no bundle files to misroute, fitting 'good structure; most content is appropriately placed'; it is over 50 lines so the simple-skill 5 does not quite apply.	4 / 5
	Total	16 / 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 includes both a what and a when clause tied to a distinct platform niche, but its capability verbs are generic buzzwords and its trigger keyword coverage is narrow. Tightening the actions to concrete operations and adding synonyms would lift it from mid-range to strong.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Query orders, sync product catalogs, and manage customer records in Demandware'.

Add trigger synonyms so users who say 'Salesforce Commerce Cloud' or 'SFCC' also match, e.g. 'Use when the user wants to query or update Demandware / Salesforce Commerce Cloud data'.

Spell out 1-2 more concrete trigger scenarios (e.g. 'when managing orders, products, promotions, or sites').

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain but the actions are generic buzzwords rather than concrete operations (no verbs like 'extract', 'sync', 'query'), matching the 'names the domain but actions are minimal or generic' anchor and falling below the concrete-action anchor at 3.	2 / 5
Completeness	Both 'what' ('Demandware integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Demandware data') are explicitly present, but the 'when' clause is single and the 'what' is generic, fitting the 'has both what and when; when could be more explicit' anchor rather than the fully concrete 5.	4 / 5
Trigger Term Quality	'Demandware' and 'Demandware data' are relevant niche keywords with a usable trigger phrase, but coverage lacks synonyms or variations (e.g. 'Salesforce Commerce Cloud', 'SFCC'), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Demandware' is a specific platform niche giving clear distinctiveness and low conflict risk, but the generic 'manage data, records, workflows' phrasing leaves minor overlap with other data-integration skills, fitting 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/demandware/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.