Name: lightspeed-r-series
Rating: 64 (1 reviews)
Author: membranedev

lightspeed-r-series

Lightspeed R-Series integration. Manage Accounts, Employees, Locations, PurchaseOrders, Vendors, InventoryCounts. Use when the user wants to interact with Lightspeed R-Series data.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/lightspeed-r-series/SKILL.md

Quality

Content

81%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 and well-structured, with executable commands and a clearly sequenced connection workflow that includes explicit state checkpoints and a retry loop. Its chief weaknesses are some padded explanatory prose Claude does not need and a couple of large inline tables/lists that could be split into a reference file.

Suggestions

Trim the definitional opener ('Lightspeed R-Series is a retail point of sale...') and the analogy ('Think of it as a modern cash register...') to assume Claude's knowledge of the product category.

Move the full entity hierarchy and/or the 20-row popular-actions table into a separate reference file (e.g., REFERENCE.md) and link to it from the overview.

Cut the editorializing sentence 'so you can focus on the integration logic rather than auth plumbing' since the preceding clause already conveys the capability.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete command blocks, but includes unnecessary padding such as 'Think of it as a modern cash register and business analytics tool combined' and an explanatory opener defining what Lightspeed R-Series is that Claude does not need.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection setup, action search/run, and proxy requests, with flags and JSON input examples covering the common cases.	5 / 5
Workflow Clarity	The connection setup workflow is clearly sequenced with explicit state-based checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a feedback loop of polling again after the user completes an action, plus --wait polling guidance.	5 / 5
Progressive Disclosure	As a single-file skill it is well-organized into clear sections with no external references, but the large entity list and 20-row popular-actions table arguably belong in a separate reference file, leaving minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

71%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 is well-targeted to a specific product and lists concrete resources with an explicit use-when clause, giving it strong distinctiveness and completeness. Its main weakness is narrow, single-phrasing trigger language that misses natural user variations and the reliance on one generic 'Manage' verb rather than enumerated actions.

Suggestions

Expand the 'Use when' clause with concrete, user-natural triggers such as 'list sales', 'create purchase orders', 'look up an item by ID', or 'manage inventory counts'.

Replace the single generic 'Manage' verb with several specific action verbs (e.g., 'List, create, update, and retrieve Accounts, Employees...') to lift specificity.

Add common synonyms/extensions (e.g., 'Lightspeed Retail', 'R-Series POS') so the description matches more natural phrasings users actually say.

Dimension	Reasoning	Score
Specificity	Lists six concrete resources (Accounts, Employees, Locations, PurchaseOrders, Vendors, InventoryCounts) alongside a single 'Manage' verb, naming the domain with several specific items but only a generic action verb, so it sits just below comprehensive multi-action coverage.	4 / 5
Completeness	It answers 'what' (integration that manages the listed resources) and 'when' ('Use when the user wants to interact with Lightspeed R-Series data'), but the 'when' clause is single and could be more specific or varied.	4 / 5
Trigger Term Quality	The only trigger phrasing is 'Use when the user wants to interact with Lightspeed R-Series data', which references the product but lacks common natural variations, synonyms, or task-oriented phrasings a user would actually say.	3 / 5
Distinctiveness Conflict Risk	It is clearly niched to Lightspeed R-Series with product-specific triggers, making it highly distinguishable and unlikely to fire for an unrelated skill.	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-r-series/SKILL.md
Commit: f484c82

Reviewed: ~20 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.