Name: lifterlms
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

lifterlms

LifterLMS integration. Manage Courses. Use when the user wants to interact with LifterLMS data.

Quality

66%

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

Quality

Content

76%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 throughout, but its workflow clarity is capped by the absence of validation/verification for destructive and batch operations, and a minor dangling 'Step 2' reference. Progressive disclosure is good for a self-contained file though slightly long.

Suggestions

Add a validation/verification checkpoint before and after destructive actions (e.g. confirm the target ID, run a get-* afterward to verify deletion, and warn the user before delete-* runs).

Fix the dangling navigation: label 'Step 2' explicitly or replace 'skip to Step 2' with a concrete section link so the connection-to-actions handoff is unambiguous.

Consider moving the 20-row Popular actions table into a references/ file and keeping a concise 'most-used' subset inline to tighten the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands, tables, and terse operational prose with only minor over-explanation (e.g. the one-line LifterLMS intro and the Membrane-auth framing), fitting 'Efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It provides copy-paste-ready commands for every stage (login, connection ensure, polling, action list/run, request proxy) plus a flag table and a populated actions table, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connect → poll → search → run sequence is present with a state feedback loop, but destructive actions (delete-course, delete-student, etc.) lack any validation/verification or confirm-before-delete checkpoint, which caps workflow clarity at 3 per the destructive-operations rule; a dangling 'skip to Step 2' with no labeled Step 2 adds a gap.	3 / 5
Progressive Disclosure	No bundle files exist; the skill is a single self-contained file with clear section headers (Overview, Working with LifterLMS, Popular actions, Best practices), giving good structure, though the ~160-line length and the large inline actions table keep it just short of the ideal split of a 5.	4 / 5
	Total	16 / 20 Passed

Description

57%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 correctly pairs a what with an explicit 'Use when' trigger and leverages a distinctive product name, but it is thin: only one generic action and a narrow trigger clause that omits common LifterLMS entities. It is functional but not comprehensive.

Suggestions

Expand the what to list concrete actions and entities, e.g. 'Create, update, and list courses, lessons, memberships, and students'.

Broaden the trigger to cover natural phrasings: 'Use when the user wants to manage LifterLMS courses, lessons, memberships, or students'.

Keep the third-person imperative voice already in use; avoid padding with marketing language about the integration.

Dimension	Reasoning	Score
Specificity	"Manage Courses" names the LifterLMS domain but only offers one generic action ("manage"), mirroring the anchor 'Names the domain but actions are minimal or generic'; it does not reach the 1-2 concrete-actions breadth of a 3.	2 / 5
Completeness	It states a what ("LifterLMS integration. Manage Courses.") and an explicit when ("Use when the user wants to interact with LifterLMS data"), but the when is narrow and the what is thin, so it sits at 'Has both what and when; when could be more explicit or specific' rather than a 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with LifterLMS data" gives a relevant trigger keyword (LifterLMS) but misses common variations like courses, lessons, memberships, or students, fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	LifterLMS is a specific named product with a distinct trigger, giving minimal conflict risk, but the description's brevity and generic 'Manage Courses' keep it just short of the fully distinct niche of a 5.	4 / 5
	Total	13 / 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/lifterlms/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.