magento
Magento integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Magento. Routes through Apideck with serviceId "magento".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the specific platform (Magento), the integration mechanism (Apideck Ecommerce unified API), concrete actions (read, write, sync), target entities (orders, products, customers, stores), and explicit trigger conditions. The description is concise, uses third person voice, and provides enough detail for Claude to distinguish it from similar ecommerce skills for other platforms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read, write, sync orders, products, customers, and stores in Magento. Also mentions the unified API pattern and serviceId mechanism. | 3 / 3 |
Completeness | Clearly answers both what (Magento integration via Apideck's Ecommerce unified API for reading, writing, syncing orders/products/customers/stores) and when ('Use when the user wants to read, write, or sync orders, products, customers, and stores in Magento') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Magento', 'orders', 'products', 'customers', 'stores', 'sync', 'Apideck', 'Ecommerce', and 'serviceId'. Good coverage of terms a user working with Magento ecommerce would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Magento via Apideck with serviceId 'magento'. The mention of the specific connector and serviceId makes it very unlikely to conflict with other ecommerce or Apideck skills for different platforms. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid connector-specific skill that provides actionable code examples, good progressive disclosure to related skills, and clear escape hatches. Its main weaknesses are some verbosity around the portability value proposition (which reads more like marketing than instruction) and a lack of explicit workflow sequencing that would help Claude navigate the verify-then-use-or-fallback pattern more reliably.
Suggestions
Trim the 'Portable across 17 Ecommerce connectors' section to 2-3 lines — the portability point is already made in the intro and the code example speaks for itself.
Add an explicit numbered workflow: 1. Verify connection → 2. Check coverage for needed operations → 3. Use unified API for supported ops → 4. Fall back to Proxy API for unsupported ops, with a validation checkpoint after step 2.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 17 Ecommerce connectors' section repeats the portability concept already stated in the intro, and the marketing-style language ('compounding advantage') adds no actionable value. The 'When to use this skill' section explains obvious things. However, it's not egregiously padded. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing orders, a concrete curl command for verifying coverage, and a complete proxy API escape hatch with real headers. The serviceId, auth setup link, and SDK references give Claude everything needed to act. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (set up auth → verify coverage → use unified API → fall back to proxy if needed), but it's not explicitly sequenced with numbered steps or validation checkpoints. The coverage verification step is present but not integrated into a clear workflow with feedback loops for when operations are unsupported. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the skill provides a concise overview with well-signaled one-level-deep references to SDK skills, best practices, connector coverage, OpenAPI specs, and external docs. Content is appropriately split between this overview and referenced materials. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- apideck-libraries/api-skills
- Commit
9e04d86
- 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.