amazon-seller-central
Amazon Seller Central 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 Amazon Seller Central. Routes through Apideck with serviceId "amazon-seller-central".
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 integration target (Amazon Seller Central via Apideck), lists concrete data entities (orders, products, customers, stores), specifies actions (read, write, sync), and includes an explicit 'Use when' clause. The description is concise, uses third person voice, and provides enough technical context (serviceId, unified API) to distinguish it from similar ecommerce skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'read, write, or sync orders, products, customers, and stores' and specifies the integration mechanism (Apideck's Ecommerce unified API, serviceId). These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('read, write, or sync orders, products, customers, and stores in Amazon Seller Central via Apideck') and when ('Use when the user wants to read, write, or sync orders, products, customers, and stores in Amazon Seller Central'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Amazon Seller Central', 'orders', 'products', 'customers', 'stores', 'Apideck', 'Ecommerce', 'sync'. Good coverage of terms a user working with Amazon selling would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific triggers: 'Amazon Seller Central', 'serviceId "amazon-seller-central"', and the Apideck Ecommerce unified API context. Unlikely to conflict with other skills unless there are multiple Amazon Seller Central integrations. | 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 well-structured connector skill with strong actionability and excellent progressive disclosure through clear references to related skills and external documentation. Its main weaknesses are moderate verbosity (repeating the portability value proposition, over-explaining OAuth and activation triggers) and a workflow that could be more explicitly sequenced with validation checkpoints for the coverage-check-then-fallback pattern.
Suggestions
Trim the 'Portable across 17 Ecommerce connectors' section — the intro already establishes portability; the code example showing serviceId swapping could be folded into the minimal example.
Consolidate the coverage check and proxy fallback into a single explicit workflow: 1. Check coverage → 2. If supported, use unified API → 3. If UnsupportedOperationError, use proxy → 4. Verify response, with clear decision points.
| 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, the 'When to use this skill' section over-explains activation triggers, and the authentication section explains OAuth concepts Claude already knows. However, it's not egregiously padded. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing orders, concrete curl commands for coverage verification and proxy API usage, specific serviceId strings, and real URLs. The examples are copy-paste ready with clear environment variable references. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (check coverage → use unified API → fall back to proxy if unsupported), but it's not presented as a clear sequential process with explicit validation checkpoints. The coverage verification and proxy fallback are in separate sections without a cohesive decision flow or error recovery loop. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview and well-signaled one-level-deep references to SDK skills, best practices, connector coverage, OpenAPI specs, and external docs. The 'See also' section provides clear navigation without nesting references multiple levels deep. | 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.