ebay
eBay 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 eBay. Routes through Apideck with serviceId "ebay".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 platform (eBay), the integration mechanism (Apideck Ecommerce unified API), the concrete actions (read, write, sync), the data entities (orders, products, customers, stores), and explicit trigger guidance. The description is concise, uses third person voice, and provides enough detail for Claude to distinguish it from other ecommerce or Apideck skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, or sync orders, products, customers, and stores in eBay.' Also mentions the integration mechanism (Apideck's Ecommerce unified API) and the serviceId pattern. | 3 / 3 |
Completeness | Clearly answers both 'what' (eBay 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 eBay'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'eBay', 'orders', 'products', 'customers', 'stores', 'sync', 'Apideck', 'Ecommerce'. These cover the main terms a user would naturally use when requesting eBay integration work. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically eBay via Apideck with serviceId 'ebay'. The mention of the specific connector, serviceId, and platform name makes it very unlikely to conflict with other skills, even other Apideck ecommerce connectors. | 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 to related skills and references. Its main weaknesses are some marketing-style verbosity (explaining Apideck's value proposition rather than just instructing) and a workflow that could be more explicitly sequenced, particularly around the coverage-check-then-fallback pattern.
Suggestions
Remove or significantly trim the 'Portable across 17 Ecommerce connectors' section — the portability point is already made in the intro and the code example is redundant with the minimal example.
Add an explicit numbered workflow: 1. Verify coverage → 2. Use unified API → 3. Handle UnsupportedOperationError → 4. Fall back to Proxy API, with clear decision points.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 17 Ecommerce connectors' section over-explains the value proposition of Apideck (Claude doesn't need to be sold on it), and phrases like 'This is the compounding advantage' are marketing fluff. The 'When to use this skill' section also restates what's already clear from context. However, the core technical content is reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing orders, concrete curl commands for coverage verification and proxy API usage, and specific serviceId strings. The examples are copy-paste ready with clear environment variable references. | 3 / 3 |
Workflow Clarity | The skill implicitly describes a workflow (check coverage → use unified API → fall back to proxy), but it's not explicitly sequenced with numbered steps or validation checkpoints. The coverage verification step is mentioned but not integrated into a clear decision flow with error handling for when coverage checks fail. | 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 sibling connectors. 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.