Name: leyr
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

leyr

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

76%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 highly actionable with executable Membrane CLI commands and a clear connection workflow including state feedback loops. Its gaps are minor marketing fluff and the absence of validation guidance for destructive proxy/action operations, plus no use of bundle files to offload reference material.

Suggestions

Add a verification step after destructive proxy calls (e.g., re-fetch the resource to confirm the change) to satisfy the workflow_clarity cap.

Trim flavor text like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection."

Move the proxy flag table or popular-actions reference into a bundled reference file linked from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven prose with copy-paste blocks, but includes minor fluff such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection," fitting the efficient-with-minor-trims anchor; not a 5 because of those padded phrases.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands across install, login, connection ensure/get, action list/run, and proxy requests with flags and JSON input examples, matching the anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The connection setup is well-sequenced with state polling and CLIENT_ACTION_REQUIRED feedback, but the proxy section explicitly enables destructive methods (DELETE/PUT) and action runs with no verification step, so the destructive-operation cap of 3 applies; not a 4 because validation for those operations is absent.	3 / 5
Progressive Disclosure	Content is well-organized into clear headed sections with no nested or buried references and a focused proxy flag table, matching the good-structure anchor; not a 5 because everything lives in one ~120-line file with no offloaded reference material, and the under-50-line exception does not apply.	4 / 5
	Total	16 / 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 is a solid third-person statement with an explicit "Use when" trigger and a named app niche. Its main weakness is generic action verbs ("manage", "automate") instead of concrete capabilities, which limits specificity and trigger richness.

Suggestions

Replace generic verbs with concrete Leyr capabilities (e.g., "track referrals, manage candidates, sync employee records") to lift specificity.

Expand the trigger with natural user phrasing and synonyms (e.g., "Use when the user mentions referrals, candidate sourcing, or Leyr records").

Add a file-extension or object hint if Leyr exposes specific record types users would name.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the Leyr domain plus three actions, but the actions are generic ("manage", "automate") rather than concrete, matching the anchor that lists domain + 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states both a clear "what" (Leyr integration: manage data/records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Leyr data"), matching the anchor where both are present though the "when" could be more specific; not a 5 because the trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Leyr data" surfaces the keyword "Leyr" and "data" but offers no synonyms or variations, fitting the anchor with some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific SaaS app "Leyr" gives it a clear niche with minimal conflict risk, matching the mostly-distinct anchor; not a 5 because the supporting action language ("manage data") is generic and could overlap with other data 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/leyr/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.