Name: axis-lms
Rating: 61.6 (1 reviews)
Author: membranedev

axis-lms

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

Quality

72%

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/axis-lms/SKILL.md

Quality

Content

78%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 highly actionable with concrete commands and a well-sequenced connection workflow including feedback loops, but it is a monolithic inline document with minor padding and one dangling step reference.

Suggestions

Fix or remove the dangling "skip to Step 2" references by either adding an explicit numbered Step 2 (Searching for actions) or rewording to "skip to Searching for actions".

Move the proxy flag table and the detailed clientAction state machine into a separate reference file (e.g. references/connections.md) and link to it from the body to improve progressive disclosure.

Trim promotional phrasing ("fastest way", "burn less tokens", "focus on the integration logic") to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but includes minor marketing/padding phrases ("This is the fastest way to get a connection", "so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens") that could be trimmed — matching anchor 4 (efficient, minor over-explanation).	4 / 5
Actionability	The body is full of copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, proxy request with a flag table) covering the common cases, matching anchor 5's "fully executable; copy-paste ready code or commands."	5 / 5
Workflow Clarity	There is a clear multi-step sequence (install → auth → connect → poll until ready → search → run/proxy) with explicit polling feedback loops for BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR states, but the repeated "skip to Step 2" reference points to a Step 2 that does not exist, a minor structural gap that keeps it below anchor 5.	4 / 5
Progressive Disclosure	Sections are well-organized with headers, but the ~140-line body is entirely monolithic with no external references, and content like the proxy flag table and the clientAction state machine could plausibly live in separate files — matching anchor 3 (some structure, content that should be separate is inline) rather than the under-50-line exception for a 5.	3 / 5
	Total	16 / 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 cleanly states a distinct niche (Axis LMS) with both a what and a when clause, but the capability verbs are generic and the trigger vocabulary is narrow, limiting specificity and trigger-term quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Axis LMS actions such as "create courses, enroll users, pull reports, and automate learning workflows".

Expand the "Use when" clause with natural trigger phrases users would say, e.g. "Use when managing Axis LMS courses, users, learning objects, or reports."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Axis LMS domain plus a few actions, but the actions are generic ("manage data", "manage records") rather than concrete like extracting or filling — matching anchor 3 (domain + 1-2 actions, not comprehensive) and falling short of anchor 4's several specific actions.	3 / 5
Completeness	Both "what" ("Axis LMS integration. Manage data, records, and automate workflows.") and "when" ("Use when the user wants to interact with Axis LMS data.") are explicitly present; the "when" clause is clear but somewhat narrow and generic, so it is not the anchor-5 concrete-trigger-phrases level.	4 / 5
Trigger Term Quality	"Axis LMS" plus "data, records, workflows" gives some relevant keywords, but the description lacks natural synonyms or variations a user might say (e.g., courses, training, enrollments), matching anchor 3's "some relevant keywords but missing common variations."	3 / 5
Distinctiveness Conflict Risk	"Axis LMS" is a specific named product niche with distinct triggers and minimal overlap risk with other skills, matching anchor 5's "clear niche with distinct triggers; minimal conflict risk."	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/axis-lms/SKILL.md
Commit: f484c82

Reviewed: less than a minute 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.