Name: talentlms
Rating: 52 (1 reviews)
Author: membranedev

talentlms

TalentLMS integration. Manage Users, Branchs, Categories, Rules, Certificates, Tags and more. Use when the user wants to interact with TalentLMS data.

Quality

57%

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

Quality

Content

52%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 CLI usage guidance is executable and reasonably well-sequenced with a polling feedback loop, but the document is dragged down by a massive inlined entity catalog with no external reference files and a broken "skip to Step 2" cross-reference. Moving the catalog to a reference file and fixing the step labels would substantially improve it.

Suggestions

Move the ~460-line entity catalog into a separate references file (e.g. references/entities.md) and replace the inline list with a one-line pointer, so SKILL.md stays a lean overview.

Fix the dangling "skip to Step 2" reference — either label the action-search section as "Step 2" or reword to "skip to Searching for actions" — so the workflow navigation is coherent.

Trim the duplicated "File <Entity>" variant list, which adds no actionable guidance over the base entity list and roughly doubles the token cost.

Dimension	Reasoning	Score
Conciseness	The body inlines a ~460-line catalog of entity names (the raw list at lines 23–128 then the same list duplicated with a "File" prefix at lines 129–259) plus a one-line "Use action names and parameters as needed", which is heavily padded reference material Claude gains little from; the CLI sections themselves are lean, so it is noticeably rather than severely verbose.	2 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands throughout (npm install, membrane login, connection ensure, action list/run with --json, request proxy) with real flags documented in a table, leaving only minor gaps such as the undefined CONNECTION_ID source.	4 / 5
Workflow Clarity	The connection setup is sequenced (ensure → poll until READY → handle CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR → search actions → run/proxy) with a state-based feedback loop, but the dangling "skip to Step 2" reference (no labeled Step 2 exists, only "1b") is a minor gap keeping it below 5.	4 / 5
Progressive Disclosure	No bundle files exist and the giant entity catalog that clearly belongs in a separate reference file is inlined directly in SKILL.md, matching the anchor where content that should be split out is inlined; the CLI sections have headers but overall structure is minimal.	2 / 5
	Total	12 / 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 answers both what and when with an explicit trigger clause and a distinct product niche, but the action vocabulary is reduced to the single generic verb "Manage" and the trigger relies on one keyword without synonyms. Tightening the verbs and adding varied trigger phrasings would lift it.

Suggestions

Replace the single generic verb "Manage" with concrete operations (e.g., create, update, enroll, list, delete) so the capability set is explicit rather than implied by "and more".

Expand the "Use when" clause with natural trigger variations users might say, such as "Use when the user wants to create or manage TalentLMS courses, users, or enrollments."

Fix the typo "Branchs" → "Branches" for professionalism and accurate entity naming.

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates several concrete entities ("Users, Branchs, Categories, Rules, Certificates, Tags"), but the single verb "Manage" is generic and the trailing "and more" leaves the actual actions unspecified, so it sits between anchors 3 and 4 rather than reaching comprehensive concrete actions.	3 / 5
Completeness	It has a clear "what" (TalentLMS integration managing the listed entities) and an explicit "when" clause ("Use when the user wants to interact with TalentLMS data"), matching the anchor where both are present though the "when" could be more specific.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with TalentLMS data" anchors on the product name "TalentLMS", which is the natural term users would say, but there are no synonyms or varied phrasings beyond that one keyword.	3 / 5
Distinctiveness Conflict Risk	"TalentLMS integration" is a clearly named product niche with distinct triggers and minimal overlap with other skills, though the generic "Manage ... data" framing leaves slight room for ambiguity versus a 5.	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/talentlms/SKILL.md
Commit: f484c82

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