Name: leiga
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

leiga

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

Quality

59%

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

Quality

Content

65%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 commands throughout, but it is marred by a placeholder non-description at the top, broken/undefined step numbering in the connection workflow, and a lack of validation checkpoints for destructive action runs. Structure is reasonable for a single file but does not split out reference detail.

Suggestions

Remove or replace the opening line "I don't have enough information about Leiga to provide a description" with a one-sentence factual overview of Leiga.

Fix the connection workflow numbering: define Step 1 (connection ensure), relabel the wait step as Step 2, and define the referenced "Step 2" consistently so the sequence is unambiguous.

Add a validation/verification checkpoint before running batch or destructive actions (e.g. confirm the resolved action and preview --input JSON before `membrane action run`) to lift the workflow_clarity cap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but it opens with "I don't have enough information about Leiga to provide a description" (noise/padding Claude cannot act on) and re-explains Membrane auth behavior, fitting the anchor for mostly efficient content with some unnecessary explanation that could be tightened.	3 / 5
Actionability	It provides fully executable, copy-paste commands for every common case (install, login, connection ensure/get --wait, action list/run with --input, request proxy) plus a concrete flags table, matching the anchor for fully executable, copy-paste ready guidance covering common cases.	5 / 5
Workflow Clarity	The connection flow has a sequence and state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED), but step numbering is broken (jumps to "1b" with no Step 1, references a "Step 2" that is never defined) and there is no validation checkpoint for batch/destructive action runs, which caps this at the anchor where steps are present but checkpoints are missing.	3 / 5
Progressive Disclosure	It is a single well-sectioned file with no bundle files, but content that could live in a separate reference (the proxy flags table, the full clientAction object schema) is inlined and there are no one-level-deep reference links, matching the anchor for some structure with content that should be separate kept inline.	3 / 5
	Total	14 / 20 Passed

Description

53%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 pairs a "what" with an explicit "Use when" trigger and is anchored on a distinct product name, but its actions are generic ("manage", "automate") and it lacks the richer trigger-term coverage that would make it highly specific. It is functional but not yet sharp.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Leiga actions, e.g. "Create and update cases, contacts, tasks, time entries, and expenses; automate Leiga workflows."

Expand the trigger clause with natural user phrasing, e.g. "Use when the user wants to create or update Leiga cases, manage contacts/tasks, track time entries, or automate Leiga workflows."

Tighten distinctiveness by naming Leiga-specific entities (cases, case notes) so the description cannot fire for a generic CRM/data skill.

Dimension	Reasoning	Score
Specificity	The phrase "Manage data, records, and automate workflows" names the Leiga domain but the actions are minimal and generic ("manage", "automate"), matching the anchor that names the domain with minimal/generic actions.	2 / 5
Completeness	It has both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Leiga data"), but the "when" is fairly generic rather than listing concrete trigger phrases, matching the anchor where both are present but the "when" could be more specific.	4 / 5
Trigger Term Quality	"interact with Leiga data" provides some relevant keywords anchored on the Leiga name, but there are no synonyms, file extensions, or common variations beyond the single product term, matching the anchor with some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The Leiga product name gives a niche, but "Manage data, records" is broad and could overlap with generic CRM or data-management skills, matching the anchor for somewhat specific but still overlapping with similar skills.	3 / 5
	Total	12 / 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/leiga/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.