bigcommerce
BigCommerce 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 BigCommerce. Routes through Apideck with serviceId "bigcommerce".
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 (BigCommerce via Apideck), lists concrete entities and actions (read/write/sync orders, products, customers, stores), and provides explicit trigger guidance. The description is concise, uses third person voice, and includes enough technical specificity (serviceId, unified API) to be both discoverable and distinguishable from similar skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, or sync orders, products, customers, and stores in BigCommerce.' Also mentions the unified API pattern and serviceId switching mechanism. | 3 / 3 |
Completeness | Clearly answers both what ('BigCommerce integration via Apideck's Ecommerce unified API' with specific entity types) and when ('Use when the user wants to read, write, or sync orders, products, customers, and stores in BigCommerce') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'BigCommerce', 'orders', 'products', 'customers', 'stores', 'Apideck', 'Ecommerce', 'sync', and the specific serviceId 'bigcommerce'. Good coverage of terms a user working with BigCommerce would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets BigCommerce via Apideck with a named serviceId. The mention of 'serviceId "bigcommerce"' and the Apideck Ecommerce unified API creates a clear niche that is unlikely to conflict with other e-commerce or general API 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 weakness is moderate verbosity — the portability/marketing language and the 'When to use this skill' section add tokens without proportional value. The workflow could benefit from explicit error handling guidance, especially for the Proxy API fallback path.
Suggestions
Trim the 'Portable across 17 Ecommerce connectors' section to 2-3 lines — the portability point is already made in the intro paragraph and the sibling connectors section.
Remove or drastically shorten the 'When to use this skill' section — Claude doesn't need instructions on when to activate a skill; the frontmatter description handles that.
Add a brief error-handling note for the Proxy API (e.g., check response status, common BigCommerce error codes) to improve workflow clarity for the escape hatch path.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 17 Ecommerce connectors' section is marketing-flavored and repeats the portability point already made in the intro. The 'When to use this skill' section over-explains activation triggers Claude doesn't need. However, the entity mapping table and coverage highlights are efficient and useful. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing orders, filtering by date, and using the Proxy API escape hatch with a complete curl command. The entity mapping table and coverage highlights give concrete guidance on what's supported vs. what requires the Proxy. | 3 / 3 |
Workflow Clarity | The skill covers a relatively simple integration pattern (API calls), but for the Proxy API escape hatch — which involves constructing raw HTTP requests to BigCommerce's API — there's no validation or error-handling guidance. The workflow for determining when to use Proxy vs. unified API is implicit rather than explicitly sequenced. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick facts, minimal example up front, and well-signaled one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage tools. Content is appropriately split between this skill and referenced resources. | 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.