Name: lean-technologies
Rating: 61.6 (1 reviews)
Author: membranedev

lean-technologies

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

Quality

72%

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

Quality

Content

82%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 copy-paste commands and a clear state-driven connection workflow, kept reasonably lean. The main gaps are a confusing step-numbering reference and the absence of an explicit validation/verification step before running potentially destructive payment actions.

Suggestions

Add a short validation step before running payment-creating or batch actions (e.g., confirm the connection is READY and echo the action's inputSchema before 'action run').

Fix the 'skip to Step 2' reference by labeling the connection sequence as explicit numbered steps (1. ensure, 2. wait/handle, 3. search) so the cross-references resolve.

Merge or clearly differentiate 'Searching for actions' and 'Popular actions' to remove redundancy around 'membrane action list'.

Dimension	Reasoning	Score
Conciseness	Mostly lean with copy-paste commands and a useful flag table; only minor padding such as the introductory paragraph about Lean's market positioning ('helps businesses in Latin America... streamline financial operations').	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases — install, login, connection ensure/get, action list/run, and proxy requests — each with real flags and a concrete options table.	5 / 5
Workflow Clarity	The connection flow has a clear state-driven sequence with checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and polling), but the 'skip to Step 2' reference has no labeled Step 1/Step 2 and there is no validation step for potentially destructive payment actions.	4 / 5
Progressive Disclosure	Self-contained, well-organized with clear section headers and no nested references needed; minor organization gaps include redundancy between 'Searching for actions' and 'Popular actions' and the inconsistent step numbering.	4 / 5
	Total	17 / 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, but relies on generic verbs ('manage data, records, automate workflows') and misses the domain-specific terms (payments, reconciliation) that would sharpen its triggers and specificity.

Suggestions

Replace generic verbs with concrete Lean capabilities, e.g. 'create payments, request payment links, manage beneficiaries, and reconcile reports'.

Add concrete trigger phrases tied to the real domain: 'Use when the user wants to send payments, manage beneficiaries, or reconcile transactions via Lean Technologies.'

Include a natural synonym or file/extension-style cue where applicable to broaden trigger coverage beyond 'interact with Lean Technologies data'.

Dimension	Reasoning	Score
Specificity	Names the domain plus a few actions ('Manage data, records, and automate workflows'), but these are generic verbs rather than concrete capabilities like creating payments or reconciling transactions.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' trigger, but the trigger is generic ('interact with Lean Technologies data') rather than concrete.	4 / 5
Trigger Term Quality	Includes the platform name and the natural phrase 'interact with Lean Technologies data', but omits the actual domain terms (payments, reconciliation) and any synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	Names the specific Lean Technologies platform, giving it a clear niche and minimal conflict risk, though the generic 'manage data, records' framing has minor overlap with other 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/lean-technologies/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.