adobe-commerce
Adobe Commerce integration. Manage data, records, and automate workflows. Use when the user wants to interact with Adobe Commerce data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill adobe-commerce72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 what and when clauses, establishing basic completeness. However, it relies heavily on the 'Adobe Commerce' brand name for distinctiveness while using generic action language that doesn't convey the specific e-commerce capabilities. Missing the 'Magento' alias and common e-commerce terms reduces discoverability.
Suggestions
Add specific e-commerce actions like 'manage products, process orders, handle customer data, sync inventory' instead of generic 'manage data, records'
Include trigger term variations users might say: 'Magento', 'ecommerce store', 'product catalog', 'shopping cart', 'order management'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Adobe Commerce) and mentions general actions ('Manage data, records, and automate workflows'), but lacks specific concrete actions like 'create products', 'process orders', or 'sync inventory'. | 2 / 3 |
Completeness | Has both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Adobe Commerce data') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Adobe Commerce' which is a key term, but misses common variations users might say like 'Magento', 'ecommerce', 'product catalog', 'orders', or 'shopping cart'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is generic phrasing that could overlap with many integration skills; only 'Adobe Commerce' provides distinctiveness. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for Adobe Commerce integration via Membrane, with good coverage of connection setup, action discovery, and proxy requests. However, it wastes tokens explaining what Adobe Commerce is, lacks validation/error handling in workflows, and could benefit from better progressive disclosure by linking to detailed entity-specific documentation.
Suggestions
Remove the opening paragraph explaining what Adobe Commerce is - Claude already knows this
Add validation steps after key operations (e.g., verify connection was created successfully, check action output for errors)
Consider moving the entity overview list to a separate reference file and linking to it
Add error handling guidance - what to do when commands fail or return unexpected results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Adobe Commerce is, which Claude already knows. The entity list is useful but could be more compact. The CLI instructions are reasonably efficient but include some redundant explanations. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including JSON parameter passing, proxy requests with flag documentation, and concrete examples for connection setup and action discovery. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced but lack validation checkpoints. No error handling or verification steps after running actions. The 'check existing connections' step is good but could be better integrated into a decision flow. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one file. The entity overview list could link to detailed documentation. No references to external files for advanced topics like error handling or specific entity operations. | 2 / 3 |
Total | 9 / 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 | |
- 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.