Name: tutor-lms
Rating: 56.8 (1 reviews)
Author: membranedev

tutor-lms

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

Quality

65%

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

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.

The body is a well-structured, actionable integration guide with concrete Membrane CLI commands and a solid connection-state workflow. Its main weaknesses are mild verbosity in introductory/marketing prose and an undefined 'Step 2' reference that slightly disrupts the workflow sequence.

Suggestions

Trim the introductory paragraph and the 'so you can focus on the integration logic rather than auth plumbing' framing; assume Claude knows what an LMS plugin is.

Define the referenced 'Step 2' explicitly (e.g. relabel 'Searching for actions' as Step 2) or remove the dangling cross-reference.

Consider extracting the proxy flag table and full clientAction state spec into a references file to shorten the main SKILL.md and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command-focused code blocks, but the opening paragraph explains what Tutor LMS is and the auth section includes marketing framing ('so you can focus on the integration logic rather than auth plumbing'). Not 4 because several sentences could be trimmed without losing clarity.	3 / 5
Actionability	Provides concrete copy-paste commands for install, login, connection ensure/get, action list/run, and proxy requests, plus a full flag table. Not 5 because placeholders (CONNECTION_ID, QUERY, <agentType>) and the absence of a worked end-to-end example leave minor gaps.	4 / 5
Workflow Clarity	Clear sequence (install -> authenticate -> connect -> poll state -> search actions -> run) with feedback loops for BUILDING and CLIENT_ACTION_REQUIRED states. Not 5 because the body references 'Step 2' which is never defined as a labeled step, leaving one sequencing gap.	4 / 5
Progressive Disclosure	Single SKILL.md (no bundle files present) with well-organized, clearly headed sections covering overview, setup, connection, actions, proxy, and best practices. Not 5 because it exceeds 50 lines with inline detail (full clientAction spec, flag table) that could optionally live in reference files.	4 / 5
	Total	15 / 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 cleanly answers both what the skill does and when to use it with an explicit trigger clause, but its action language is generic and its trigger coverage is narrow. It is distinct as a Tutor LMS-specific skill yet could be sharper.

Suggestions

Replace generic verbs with concrete Tutor LMS capabilities, e.g. 'Create and manage courses, lessons, quizzes, assignments, enrollments, and earnings' instead of 'Manage data, records, and automate workflows'.

Broaden the trigger clause with natural variations: 'Use when the user wants to manage Tutor LMS courses, students, quizzes, assignments, or enrollment data.'

Add common synonyms/extensions users might say (e.g. 'Tutor LMS courses', 'Themeum Tutor') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Tutor LMS domain and lists a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete capabilities. Not a 2 because more than one action is named; not a 4 because none of the actions are specific or comprehensive.	3 / 5
Completeness	It states both what ('Tutor LMS integration. Manage data, records, and automate workflows.') and an explicit when ('Use when the user wants to interact with Tutor LMS data.'). Not 5 because the trigger clause is narrow and lacks multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	'Tutor LMS' is the natural product keyword a user would say, but the description includes no synonyms, common variations, or related natural phrases. Matches the 'some relevant keywords but missing common variations' anchor rather than 4-level broad coverage.	3 / 5
Distinctiveness Conflict Risk	Tutor LMS is a specific WordPress plugin niche with distinct triggers, but the generic 'manage data, records' phrasing creates minor overlap risk with other LMS/course-management skills. Not 5 because the action wording is not uniquely distinguishing.	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/tutor-lms/SKILL.md
Commit: f484c82

Reviewed: 3 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.