Name: lightspeed-vt
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

lightspeed-vt

LightSpeed VT integration. Manage Organizations. Use when the user wants to interact with LightSpeed VT data.

Quality

74%

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-vt/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 executable commands and a strong, validated connection workflow. Its main weaknesses are minor verbosity and a dangling "Step 2" reference with no corresponding labeled step.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command examples and tables, with only minor padding (e.g., "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection") that could be trimmed.	4 / 5
Actionability	Every section provides copy-paste-ready commands (membrane login, connection ensure, action list/run, request proxy) with flag tables and a concrete popular-actions table covering the common cases.	5 / 5
Workflow Clarity	The connection setup is a clear sequenced flow with an explicit polling/validation loop (BUILDING → READY / CLIENT_ACTION_REQUIRED / error states), but the body references "Step 2" without a matching numbered header, leaving a small navigation gap.	4 / 5
Progressive Disclosure	Single-file skill with no bundle directories; content is well-organized into clear sections with no nested references, though the 16-row popular-actions table is bulk content that could optionally live in a reference file.	4 / 5
	Total	17 / 20 Passed

Description

66%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 a clear niche, but its action list and trigger terms are sparse and generic. Adding concrete verbs (manage users, assign training, pull reports) and natural user phrasings would lift specificity and trigger quality.

Suggestions

Replace the generic "Manage Organizations" with concrete actions drawn from the body (e.g., "Manage users, assign training, list courses, and generate SSO URLs").

Expand the 'Use when' clause with natural trigger terms users actually say, such as "training assignments," "course completion," or "LightSpeed VT users."

Mirror the popular-actions vocabulary (create-user, assign-training, get-user-sso-url) so the description surfaces the terms most likely to match a user request.

Dimension	Reasoning	Score
Specificity	Names the domain ("LightSpeed VT integration") and one concrete action ("Manage Organizations"), but coverage is thin and not comprehensive, matching the 'domain + 1-2 concrete actions' anchor.	3 / 5
Completeness	It states a clear 'what' ("LightSpeed VT integration. Manage Organizations.") and an explicit 'when' ("Use when the user wants to interact with LightSpeed VT data"), but the 'when' could be more specific about which tasks trigger it.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with LightSpeed VT data" surfaces the platform name but uses generic wording ("interact with data") and omits natural variations like "training," "courses," or "assignments" that users would say.	3 / 5
Distinctiveness Conflict Risk	"LightSpeed VT integration" names a specific platform niche with distinct triggers, so it is unlikely to fire for unrelated skills.	5 / 5
	Total	15 / 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-vt/SKILL.md
Commit: f484c82

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