Name: lessonly
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

lessonly

Lessonly integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lessonly 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/lessonly/SKILL.md

Quality

Content

66%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 CLI integration guide with a strong connection state-machine, but it is held back by marketing-fluff padding, a dangling 'Step 2' reference with no matching label, and an absence of validation checkpoints for destructive data operations. Tightening prose and adding verification steps would materially raise the score.

Suggestions

Trim marketing-style filler ('fastest way', 'burn less tokens', 'focus on the integration logic') to improve token efficiency.

Add validation/verification guidance for destructive or batch operations, e.g. checking action output or confirming a proxy PUT/DELETE before applying it broadly.

Fix the dangling 'skip to Step 2' reference by labeling the destination section (e.g. '## Step 2 — Search and run actions') or rewording to a direct section link.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but includes unnecessary explanation and marketing fluff such as 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection', and 'This will burn less tokens'.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure/get, action list/run, request) plus a complete proxy flag table, with only minor gaps such as ID placeholders and no full end-to-end worked example.	4 / 5
Workflow Clarity	There is a clear install→auth→connect→search→run sequence with a genuine state-machine feedback loop for connections, but the core data operations (action run and proxy with POST/PUT/DELETE) lack validation/verification steps, and the destructive/batch cap at 3 applies.	3 / 5
Progressive Disclosure	Content is organized into clear, navigable sections and a single file is reasonable for a CLI-wrapper skill with no external references needed, though at ~140 lines it does not qualify for the simple-skill 5 exception.	4 / 5
	Total	14 / 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 includes an explicit 'Use when' trigger and a clear domain, but its action list is generic rather than concrete and its trigger vocabulary is limited to the brand name. It is functional but could be sharpened with specific Lessonly capabilities and synonyms.

Suggestions

Replace generic verbs with concrete Lessonly actions, e.g. 'Create and assign courses, manage users and groups, track training progress'.

Add natural trigger synonyms beyond the brand name, such as 'training', 'onboarding', 'courses', or 'LMS'.

Tighten the 'when' clause to reference concrete intents, e.g. 'Use when the user wants to create or assign Lessonly training, manage learners, or report on course completion'.

Dimension	Reasoning	Score
Specificity	The description names the Lessonly domain but its actions ('Manage data, records, and automate workflows') are generic and abstract, with no concrete Lessonly-specific operations like creating courses or enrolling users.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Lessonly data') are present, though neither is highly specific.	4 / 5
Trigger Term Quality	The only natural keyword is the brand name 'Lessonly', which users would say, but common variations and synonyms (training, courses, onboarding, LMS) are missing.	3 / 5
Distinctiveness Conflict Risk	The 'Lessonly' brand name gives a clear niche with minimal conflict risk, but the generic action verbs could overlap with other data-management skills if the brand name is absent.	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/lessonly/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.