lightspeed-ecommerce
Lightspeed eCom (C-Series) 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 Lightspeed eCom (C-Series). Routes through Apideck with serviceId "lightspeed-ecommerce".
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 specific platform (Lightspeed eCom C-Series), the integration mechanism (Apideck Ecommerce unified API), concrete actions (read, write, sync), target entities (orders, products, customers, stores), and explicit trigger guidance. The description is concise, uses third person voice, and provides enough detail for accurate skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, or sync orders, products, customers, and stores' and mentions the unified API pattern with serviceId switching. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('integration via Apideck's Ecommerce unified API' with read/write/sync of orders, products, customers, stores) and when ('Use when the user wants to read, write, or sync orders, products, customers, and stores in Lightspeed eCom (C-Series)'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Lightspeed eCom', 'C-Series', 'orders', 'products', 'customers', 'stores', 'Apideck', 'Ecommerce', 'lightspeed-ecommerce', 'sync'. Good coverage of both brand-specific and domain terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific platform name 'Lightspeed eCom (C-Series)', the specific serviceId 'lightspeed-ecommerce', and the Apideck routing context. Unlikely to conflict with other skills unless there are other Lightspeed 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 to related skills and references. Its main weaknesses are moderate verbosity from repeated marketing-style portability messaging and a workflow that could be more explicitly sequenced with validation checkpoints, especially given the beta status of the connector.
Suggestions
Consolidate the portability messaging — the intro paragraph and the 'Portable across 17 Ecommerce connectors' section say the same thing; keep one concise version.
Add an explicit numbered workflow: 1) Verify coverage → 2) Use unified API → 3) Handle UnsupportedOperationError → 4) Fall back to Proxy API, with validation at each step.
Remove the 'When to use this skill' section's explanatory bullets — Claude doesn't need to be told what the skill teaches it; the content itself demonstrates that.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 17 Ecommerce connectors' section repeats the portability pitch already made in the intro, and the 'When to use this skill' section over-explains activation triggers. The marketing-style language ('compounding advantage') wastes tokens. However, the core technical content is reasonably efficient. | 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 type, and SDK initialization are all copy-paste ready. | 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 beta status warning mentions verifying coverage but doesn't integrate this into a step-by-step workflow with error handling feedback loops. | 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 official 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.