lightspeed
Lightspeed 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. Routes through Apideck with serviceId "lightspeed".
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 (Lightspeed via Apideck), lists concrete data entities and operations, and provides explicit trigger guidance. The mention of the unified API pattern and serviceId switching adds useful context for disambiguation. It uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions and entities: 'read, write, or sync orders, products, customers, and stores in Lightspeed.' Also mentions the unified API pattern and serviceId switching mechanism. | 3 / 3 |
Completeness | Clearly answers both what ('read, write, or sync orders, products, customers, and stores in Lightspeed' via Apideck's unified API) and when ('Use when the user wants to read, write, or sync orders, products, customers, and stores in Lightspeed'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Lightspeed', 'orders', 'products', 'customers', 'stores', 'Apideck', 'Ecommerce', 'sync', and the specific serviceId 'lightspeed'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets specifically Lightspeed via Apideck with a unique serviceId. The combination of 'Lightspeed', 'Apideck', 'Ecommerce unified API', and 'serviceId "lightspeed"' makes it very unlikely to conflict with other 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 (marketing language, repeated portability messaging, explanations of when to use the skill) and a workflow that could be more explicitly sequenced with validation checkpoints. The escape hatch and coverage verification sections are valuable additions.
Suggestions
Trim the 'Portable across 17 Ecommerce connectors' section — the intro already explains portability; the code example showing serviceId swapping could be folded into the minimal example as a one-line comment.
Restructure the implicit workflow (verify coverage → call unified API → handle errors → fall back to proxy) as an explicit numbered sequence with validation checkpoints, especially around checking for UnsupportedOperationError before falling back.
| 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 'When to use this skill' section explains things Claude can infer. However, the quick facts and code 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, 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 explicit validation checkpoints. The coverage verification step exists but isn't integrated into a numbered 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 sibling connectors. 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.