adobe-commerce
Adobe Commerce integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adobe Commerce data.
73
67%
Does it follow best practices?
Impact
Pending
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 correctly structures a 'what' and 'when' clause but is far too vague in its capability listing. 'Manage data, records, and automate workflows' could describe almost any integration skill. It also misses the critical alias 'Magento' which many users would use interchangeably with Adobe Commerce.
Suggestions
Replace generic actions with Adobe Commerce-specific operations such as 'manage products, orders, customers, inventory, and catalog data'.
Add common trigger terms and aliases like 'Magento', 'ecommerce store', 'product catalog', 'shopping cart', 'order management'.
Expand the 'Use when' clause with specific scenarios, e.g., 'Use when the user mentions Adobe Commerce, Magento, ecommerce product management, order processing, or storefront configuration'.
| 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. It doesn't mention specific operations like managing products, orders, customers, catalogs, or inventory. | 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 generic. | 3 / 3 |
Trigger Term Quality | Includes 'Adobe Commerce' as a key trigger term, but misses common variations users might say such as 'Magento', 'ecommerce', 'product catalog', 'orders', 'shopping cart', or 'storefront'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with many integration skills. The 'Adobe Commerce' qualifier provides some distinctiveness, but missing 'Magento' means it could fail to trigger when users use that common alternative name. | 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.
The skill provides strong actionable guidance with well-structured CLI workflows and clear state-based validation checkpoints. Its main weakness is the opening section which wastes tokens explaining what Adobe Commerce is and listing entity types without actionable context. The progressive disclosure could be improved by extracting detailed state handling or entity references into separate files.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Adobe Commerce is — Claude already knows this.
Remove or condense the entity bullet list; it provides no actionable guidance and consumes significant tokens. If needed, reference it as discoverable via `membrane action list --intent`.
Consider extracting the detailed connection state handling (CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR, etc.) into a separate reference file to keep the main skill leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adobe Commerce is wastes tokens on knowledge Claude already has. The long bullet list of entity types adds little value without actionable context. However, the CLI workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection management, action discovery, action creation, and action execution, including JSON parameter passing. Commands are specific and executable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit state-based validation checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR). The connection and action creation workflows include polling/retry loops and clear branching logic for each state. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the long entity list and the inline detail about all connection states could be better organized. There are no references to separate files for advanced topics, and the document is somewhat monolithic for its length. | 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
88db8c5
- 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.