bol-com
bol.com 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 bol.com. Routes through Apideck with serviceId "bol-com".
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 platform (bol.com), the integration mechanism (Apideck Ecommerce unified API), specific data entities (orders, products, customers, stores), and explicit trigger conditions. It uses third person voice appropriately and provides enough detail for Claude to distinguish it from other ecommerce connector skills via the serviceId.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read, write, sync orders, products, customers, and stores. Also specifies the integration mechanism (Apideck's Ecommerce unified API) and the serviceId parameter. | 3 / 3 |
Completeness | Clearly answers both 'what' (bol.com integration via Apideck's Ecommerce unified API for orders, products, customers, stores) and 'when' (explicit 'Use when the user wants to read, write, or sync orders, products, customers, and stores in bol.com'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'bol.com', 'orders', 'products', 'customers', 'stores', 'Apideck', 'Ecommerce', 'sync', and the specific serviceId 'bol-com'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific platform 'bol.com', the specific serviceId 'bol-com', and the Apideck Ecommerce context. Unlikely to conflict with other skills unless there are other bol.com integration 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 actionability and progressive disclosure. Its main weaknesses are moderate verbosity (marketing language, repeated portability messaging, explaining OAuth basics) and a workflow that could be more explicitly sequenced with validation checkpoints for common failure scenarios.
Suggestions
Remove the 'Portable across 17 Ecommerce connectors' section or reduce it to a single sentence — the portability point is already made in the intro paragraph.
Trim the Authentication section to just the auth type, the setup guide link, and a note about Vault handling refresh — Claude doesn't need OAuth flow concepts explained.
Add an explicit numbered workflow: 1. Verify coverage → 2. Call unified API → 3. Handle UnsupportedOperationError → 4. Fall back to Proxy, with inline error handling examples.
| 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 core information density is reasonable. | 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 | The implicit workflow (check coverage → use unified API → fall back to proxy) is present but not explicitly sequenced with validation checkpoints. There's no clear 'if this fails, do that' feedback loop for common failure modes like UnsupportedOperationError — it just references another skill. | 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 official docs. Content is appropriately split between this skill 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.