Name: ispring-learn
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

ispring-learn

iSpring Learn integration. Manage data, records, and automate workflows. Use when the user wants to interact with iSpring Learn 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/ispring-learn/SKILL.md

Quality

Content

61%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 a well-structured, largely executable integration guide with a clear connection workflow. Its main weaknesses are minor verbosity in the intro, missing verification steps for destructive proxy operations, and a dangling 'skip to Step 2' reference with no defined Step 2.

Suggestions

Add a validation/verification step after destructive proxy requests (e.g. re-fetch the resource or check the response status before reporting success) to satisfy the destructive-operations feedback-loop requirement.

Trim the LMS background paragraph and padded phrases like 'so you can focus on the integration logic rather than auth plumbing' to improve token efficiency.

Resolve the dangling 'skip to Step 2' reference by either defining a labeled Step 2 section or rewording to 'skip to Searching for actions' so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding like the LMS intro paragraph ('iSpring Learn is a cloud-based learning management system...') and phrases such as 'so you can focus on the integration logic rather than auth plumbing'.	3 / 5
Actionability	It provides many concrete, executable commands (membrane login, connection ensure, action run, request) plus a full flag table, but most rely on runtime placeholders (CONNECTION_ID, actionId) and there is no fully worked example with real values, leaving minor gaps.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based branching, but the proxy section supports destructive methods (POST/PUT/PATCH/DELETE) with no validation or verification steps, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	No bundle files exist and the guide is organized into clean, well-signaled sections (Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices); the only gap is the inline entity overview tree that reads like reference material that could live separately.	4 / 5
	Total	14 / 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 includes both a 'what' and a 'Use when' trigger clause, which is a solid baseline. It is weakened by generic action verbs and a trigger phrase limited to the product name without natural synonyms.

Suggestions

Replace generic verbs ('manage data, records, automate workflows') with concrete actions users perform in iSpring Learn, such as 'manage users and organizations, enroll learners in courses, pull reports'.

Expand the trigger phrase with natural terms users would say, e.g. 'Use when the user wants to manage iSpring Learn users, courses, enrollments, or reports'.

Add a few file-format or entity synonyms (users, courses, learning paths, quizzes) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the iSpring Learn domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete specific verbs, matching the anchor that lists 1-2 non-comprehensive actions.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with iSpring Learn data'), but the 'when' is generic rather than explicit, matching the anchor for both present with an improvable 'when'.	4 / 5
Trigger Term Quality	The trigger clause references only the product name ('iSpring Learn data') with no synonyms or natural phrasing variations, fitting the anchor for some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The named product 'iSpring Learn' gives it a clear niche, though the generic 'manage data, records' phrasing leaves minor overlap risk with other LMS or Membrane integration skills.	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/ispring-learn/SKILL.md
Commit: f484c82

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