Name: lightspeed-ecom
Rating: 64.8 (1 reviews)
Author: membranedev

lightspeed-ecom

Lightspeed eCom integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lightspeed eCom data.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/lightspeed-ecom/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with copy-paste commands and a well-structured connection workflow that includes feedback loops. The main gaps are an unnecessary introductory explanation of what the platform is and the absence of validation checkpoints around running potentially destructive actions.

Suggestions

Trim the opening "Lightspeed eCom is an e-commerce platform that enables businesses..." paragraph; Claude does not need a description of what the platform is.

Add a validation/verification step around running actions that modify data (e.g. confirm the action's inputSchema, run against a test connection, or check the output field for errors) to lift workflow clarity.

Consider moving the proxy flag table and detailed clientAction state handling into a referenced file (e.g. CONNECTIONS.md) to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is command-driven and lean ("npm install -g @membranehq/cli@latest", "membrane connection ensure ... --json"), but opens with over-explanation Claude does not need ("Lightspeed eCom is an e-commerce platform that enables businesses to create and manage online stores...") plus minor marketing prose ("so you can focus on the integration logic rather than auth plumbing"); matches score 4 (efficient, minor trimmable instances) rather than 5 (every token earns its place) due to that intro paragraph.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure, connection get --wait, action list, action run, request) with a flag table and JSON-input example; matches the score-5 anchor (fully executable, covers common cases) rather than 4 because examples span the common cases with real flags.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll after user action), matching score 4; not 5 because action execution against potentially destructive e-commerce data (orders, customers) lacks explicit validation/verification steps, which the rubric flags as a gap.	4 / 5
Progressive Disclosure	The single-file body is well-organized with clear section headers (Overview, Working with, Install, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices) and no nested references; matches score 4 (good structure, minor organization gaps) rather than 5 because at ~150 lines some content (full proxy flag table, detailed clientAction handling) could live in a separate reference file.	4 / 5
	Total	17 / 20 Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description answers both what and when with an explicit trigger tied to a distinctive platform, keeping conflict risk low. The main weakness is generic action verbs ("manage data, records, automate workflows") that lack concrete capability specifics.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Create and update products, orders, customers, and inventory; search and run actions against Lightspeed eCom data."

Add a few natural trigger synonyms/variations such as "Lightspeed eCom store", "Lightspeed orders", or "Lightspeed catalog" to broaden trigger coverage.

Consider listing the headline data types from the body (Orders, Customers, Products, Categories) directly in the description to raise specificity.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the Lightspeed eCom domain with two-to-three actions, but the actions ("manage data, records") are generic rather than concrete; matches the score-3 anchor (names domain and 1-2 actions, not comprehensive) rather than score 2 (minimal/generic) because multiple actions are listed, and short of score 4 (several specific actions) since none are concrete.	3 / 5
Completeness	Has an explicit "what" ("Lightspeed eCom integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Lightspeed eCom data"), matching score 4; not score 5 because the "what" is generic and the "when" trigger is narrow.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Lightspeed eCom data" surfaces the natural product keyword a user would say ("Lightspeed eCom") with good coverage; sits at score 4 (good keyword coverage, a few natural terms missing) rather than 5 because it lacks synonyms or variations beyond the product name.	4 / 5
Distinctiveness Conflict Risk	"Lightspeed eCom" names a specific platform with a clear niche and distinct triggers, so conflict risk with other skills is minimal; matches the score-5 anchor (clear niche, distinct triggers, minimal conflict) rather than 4 (minor overlap with closely related skills).	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/lightspeed-ecom/SKILL.md
Commit: f484c82

Reviewed: ~21 hours ago

Table of Contents

Discovery Implementation Validation

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.