CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/axis-lms/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A solidly actionable skill body with concrete CLI commands, a sensible connection lifecycle workflow including error-state recovery, and clean sectioning. Its main weaknesses are padding around the genuine instructions, duplicated guidance, and broken cross-references in the workflow steps.

Suggestions

Trim the marketing-style introduction and filler sentences ("It's used by businesses of all sizes...", "so you can focus on the integration logic rather than auth plumbing") and lead with the install/auth commands.

Fix the broken step references: replace "skip to **Step 2**" with the actual section name and either number the sections consistently (1, 1b, 2...) or drop the numbering.

Consolidate the duplicated action-discovery guidance in "Searching for actions" and "Popular actions" into one section, and clarify what should be passed to "membrane connection ensure" instead of the bare empty string.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands and tables, but includes unnecessary padding: the marketing-style opener ("Axis LMS is a learning management system that allows companies to create, deliver, and track online training courses..."), filler like "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", and duplicated action-discovery guidance in "Searching for actions" and "Popular actions". This matches anchor 3 (mostly efficient but includes some unnecessary explanation or could be tightened) rather than anchor 4's minor instances.

3 / 5

Actionability

Concrete, copy-paste-ready CLI commands throughout, e.g. "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json" and a complete proxy flag table, plus state-machine handling with explicit polling ("--wait --timeout"). Minor gaps keep it at anchor 4 rather than 5: "membrane connection ensure \"\"" passes an empty string with no explanation of what to supply, and "membrane" vs "npx @membranehq/cli" are used inconsistently.

4 / 5

Workflow Clarity

A clear install → authenticate → connect → poll-until-ready → discover → run → proxy sequence exists, with explicit error-state handling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop ("After the user completes the action... poll again"). It falls short of anchor 5 due to broken step references: "skip to **Step 2**" points to no Step 2, and a lone "#### 1b." heading appears without a Step 1/2 numbering scheme — minor coherence gaps characteristic of anchor 4.

4 / 5

Progressive Disclosure

With no bundle files present, the skill is a self-contained body with well-organized, clearly headed sections and no nested references. It matches anchor 4 (good structure, content appropriately placed, minor organization gaps): detail like the full proxy flag table and the clientAction state documentation could arguably live in a reference file, keeping the core overview leaner.

4 / 5

Total

15

/

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.

A compact, well-formed description with an explicit 'Use when' clause and a distinctive product-named trigger. Its weaknesses are generic action phrasing and thin natural-language keyword coverage — the words users actually say (training, courses, learning management) are missing.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete actions drawn from the body's own overview, e.g. "Manage users, courses, learning objects, files, reports, and e-commerce transactions in Axis LMS".

Add natural trigger terms users would say, such as "training", "courses", "learning management system", or "compliance training", to the 'Use when' clause.

Extend the 'when' clause with concrete trigger phrases, e.g. "Use when the user mentions Axis LMS, training courses, or learning management data".

DimensionReasoningScore

Specificity

The description names the domain ("Axis LMS integration") and a few actions ("Manage data, records, and automate workflows"), but the verbs and objects are generic rather than concrete. It fits anchor 3 (domain plus 1-2 actions, not comprehensive) and falls short of anchor 4, which expects several specific actions like managing users, courses, or reports.

3 / 5

Completeness

It answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Axis LMS data") explicitly. Anchor 4 fits because the 'when' clause, while present, could be more explicit with concrete trigger phrases as in anchor 5.

4 / 5

Trigger Term Quality

"Axis LMS" is the key natural keyword, supported by "data" and "records", but common user phrasings such as "training", "courses", "learning management", or "compliance" are absent. This matches anchor 3 (some relevant keywords, missing common variations or synonyms), not anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

"Axis LMS" names a specific product, giving the description a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.