adobe-commerce
Adobe Commerce integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adobe Commerce data.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/adobe-commerce/SKILL.mdQuality
Discovery
57%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 has proper structure with an explicit 'Use when' clause, but suffers from vague, generic language that fails to convey what Adobe Commerce-specific capabilities the skill provides. It reads like a template that could be applied to any integration by swapping the product name. Adding concrete e-commerce actions and the 'Magento' alias would significantly improve it.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with concrete Adobe Commerce actions such as 'manage product catalogs, process orders, update inventory, configure pricing rules'.
Add natural trigger terms users would actually say, including 'Magento' (the former name many users still use), 'e-commerce', 'products', 'orders', 'catalog', 'inventory', 'customers', and 'shopping cart'.
Expand the 'Use when' clause with specific scenarios like 'Use when the user mentions Adobe Commerce, Magento, e-commerce orders, product catalogs, or online store management'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to Adobe Commerce. What kind of data? What records? What workflows? These are abstract terms that could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Adobe Commerce data), with an explicit 'Use when' clause. However, both parts are quite vague in substance. | 3 / 3 |
Trigger Term Quality | It includes 'Adobe Commerce' which is a relevant keyword, but misses common variations and natural terms users might say like 'Magento', 'e-commerce', 'products', 'orders', 'catalog', 'inventory', or 'shopping cart'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with many other integration skills. The 'Adobe Commerce' qualifier provides some distinctiveness, but the lack of domain-specific terms like 'Magento' or e-commerce concepts weakens it. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional integration skill with strong actionability and workflow clarity — the CLI commands are concrete and the connection state machine is well-documented. The main weaknesses are the unnecessary introductory explanation of Adobe Commerce and the large entity bullet list that adds little actionable value. The content could be tightened by removing what Claude already knows and potentially splitting reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what Adobe Commerce is — Claude already knows this. Start directly with the entity overview or the CLI workflow.
Either remove the entity bullet list or make it actionable by mapping entities to specific action names or common queries (e.g., 'To list products: membrane action list --intent "list products"').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adobe Commerce is and who uses it is unnecessary — Claude already knows this. The entity overview list is a wall of bullet points without actionable context. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and parameter examples. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and branching logic for different states. The overall flow from install → auth → connect → discover → run is well-structured with validation checkpoints. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's somewhat monolithic — the entity overview list, proxy request details, and best practices could benefit from being split or condensed. No bundle files are referenced despite the skill being complex enough to warrant them. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- Reviewed
Table of Contents
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.