etsy
Etsy 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 Etsy. Routes through Apideck with serviceId "etsy".
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 (Etsy), the integration mechanism (Apideck Ecommerce unified API), specific data entities (orders, products, customers, stores), and explicit trigger guidance. The description is concise, uses third person voice, and provides enough technical context (serviceId) to distinguish it from similar ecommerce integrations for other platforms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read, write, sync orders, products, customers, and stores. Also mentions the technical mechanism (Apideck unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both what ('read, write, or sync orders, products, customers, and stores in Etsy via Apideck') and when ('Use when the user wants to read, write, or sync orders, products, customers, and stores in Etsy'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Etsy', 'orders', 'products', 'customers', 'stores', 'sync', 'Ecommerce', 'Apideck'. Users asking about Etsy integration would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Etsy' as a specific platform, 'Apideck' as the integration layer, and 'serviceId "etsy"' as a unique identifier. Unlikely to conflict with other skills unless there are multiple Etsy skills. | 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 progressive disclosure and actionable code examples. Its main weaknesses are moderate verbosity (repeating the portability pitch, explaining OAuth basics) and a workflow that could be more explicitly sequenced with validation checkpoints. The skill effectively serves as a routing document pointing Claude to the right resources.
Suggestions
Trim the 'Portable across 17 Ecommerce connectors' section to 2-3 lines — the portability concept is already stated in the intro paragraph and the code example speaks for itself.
Condense the Authentication section to just the auth type, that Vault manages it, and the setup guide link — remove explanations of OAuth flows and token refresh that Claude already understands.
Add an explicit workflow sequence: 1. Verify coverage → 2. If supported, call unified API → 3. Handle errors (check for UnsupportedOperationError) → 4. Fall back to Proxy API if needed.
| 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 authentication section explains OAuth concepts Claude already knows. However, the quick facts and examples are reasonably tight. | 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 (check coverage → use unified API → fall back to proxy if unsupported), but it's not presented as a clear sequential process with validation checkpoints. The 'When to use this skill' section lists considerations but doesn't sequence them into a decision flow. No explicit error handling or feedback loops for failed API calls. | 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.