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

lyanthe

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/lyanthe/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 largely executable Membrane-CLI guide with a clear connection workflow and state feedback loop, undermined by a broken placeholder intro and a vague overview section that add noise without value.

Suggestions

Delete the broken opening paragraph ("I am unable to provide a description...") and replace the vague Lyanthe Overview list with a one-line statement of what Lyanthe is.

Number the connection workflow steps consistently (Step 1, Step 2) so the "skip to Step 2" references resolve clearly.

Merge the redundant "Popular actions" section into "Searching for actions" to avoid repeating the same command.

Dimension	Reasoning	Score
Conciseness	Most of the body is command-focused and reasonably efficient, but it opens with a nonsensical placeholder paragraph ("I am unable to provide a description of Lyanthe because it is uncategorized") and a vague "Lyanthe Overview" list that are unnecessary padding.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxy requests with a flags table, but placeholders like CONNECTION_ID/QUERY and the vague "Use action names and parameters as needed" leave minor gaps.	4 / 5
Workflow Clarity	The connection flow is sequenced with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, though the "skip to Step 2" references are slightly confusing because steps are not consistently numbered.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into labeled sections with no nested external references and no bundle files, appropriate for this size; the redundant "Popular actions" section that repeats the search command is a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

66%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 pairs a what-statement with an explicit Use-when trigger and is safely distinct thanks to the named app, but its action verbs and trigger phrases are generic enough to limit specificity and trigger-term richness.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Lyanthe operations such as "create, query, and update records; trigger workflows".

Expand the Use-when clause with concrete trigger phrases users would actually say, e.g. "Use when the user mentions Lyanthe records, projects, or wants to automate a Lyanthe workflow."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Lyanthe domain and lists several actions, but the verbs are generic ("manage") rather than concrete operations, so it sits at the anchor-3 level rather than the more concrete anchor-4.	3 / 5
Completeness	It states a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Lyanthe data"), but the trigger is a single generic phrase rather than multiple concrete triggers, so it is below the anchor-5.	4 / 5
Trigger Term Quality	The natural trigger is essentially the proprietary name "Lyanthe" plus "interact with Lyanthe data"; relevant but with limited synonyms or variations, matching the some-keywords-but-missing-variations anchor-3.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the named proprietary app ("Lyanthe integration" / "interact with Lyanthe data") gives it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	15 / 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/lyanthe/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.