Name: labs64-netlicensing
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

labs64-netlicensing

Labs64 NetLicensing integration. Manage Products, PaymentMethods, Discounts, Utilities. Use when the user wants to interact with Labs64 NetLicensing data.

Quality

61%

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/labs64-netlicensing/SKILL.md

Quality

Content

61%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 content is actionable and well-structured with concrete CLI commands and a clear connection workflow, but it pads the context with an unneeded platform description and omits validation steps for its destructive actions.

Suggestions

Add a validation/confirmation checkpoint before destructive actions, e.g. confirm the license/licensee number and require explicit user approval before running delete-license or delete-licensee.

Trim the opening overview paragraph that explains what a licensing platform is, since Claude already knows this; lead directly with the working commands.

Replace the literal "key":"value" input example with a real NetLicensing parameter example and show how to obtain CONNECTION_ID so the run examples are fully executable end-to-end.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and tables, but it opens with an unnecessary platform-description paragraph ("It's used by software vendors and developers to protect their applications and monetize them...") and several prose explanations that could be tightened, matching the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (login, connection ensure, action list/run, request) with flags and JSON examples, but leaves CONNECTION_ID and actionId as placeholders and uses a literal "key":"value" input rather than real NetLicensing parameters, placing it just below fully-executable.	4 / 5
Workflow Clarity	The connection setup has a clear state-driven sequence (ensure, wait for READY, handle clientAction, poll), but destructive and batch operations (delete-license, delete-licensee) lack any validation or confirmation checkpoint, so the destructive-operation cap holds it at 3.	3 / 5
Progressive Disclosure	The single file is well organized with clear section headers and no nested references, but the 20-row Popular actions table is inlined rather than offloaded to a reference file and no bundle files exist, leaving minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

62%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 named proprietary platform, giving it solid completeness and distinctiveness. It is held back by the generic "Manage" verb and the absence of common licensing synonyms that a user would naturally say.

Suggestions

Replace the generic verb "Manage" with differentiated concrete actions (e.g. "Create, list, update, and delete Products, Licensees, and Licenses").

Add the natural trigger terms users actually say, including "licenses", "licensees", and "licensing", alongside the existing entity names.

Make the "Use when" clause more concrete with specific trigger phrases, e.g. "Use when the user wants to create or manage NetLicensing products, licenses, or licensees."

Dimension	Reasoning	Score
Specificity	The description names the domain plus several concrete entity types ("Manage Products, PaymentMethods, Discounts, Utilities") but the verb is the generic "Manage" rather than differentiated concrete actions, matching the anchor that lists domain and 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	It states both a clear "what" ("Manage Products, PaymentMethods, Discounts, Utilities") and an explicit "when" ("Use when the user wants to interact with Labs64 NetLicensing data"), but the trigger clause is generic rather than concrete trigger phrases, matching the anchor where "when" could be more explicit.	4 / 5
Trigger Term Quality	It includes relevant natural keywords ("Products", "PaymentMethods", "Discounts", "Utilities", "Labs64 NetLicensing") but misses common variations a user would say such as "licenses", "licensees", or "licensing", so it falls between the some-keywords and good-coverage anchors.	3 / 5
Distinctiveness Conflict Risk	The proprietary brand "Labs64 NetLicensing" pins a clear niche with low conflict risk, but the description relies on the brand alone (no "licenses/licensees" triggers) leaving minor overlap risk with generic licensing skills.	4 / 5
	Total	14 / 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/labs64-netlicensing/SKILL.md
Commit: f484c82

Reviewed: 6 days 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.