Name: leapfin
Rating: 55.2 (1 reviews)
Author: membranedev

leapfin

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

Quality

63%

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

Quality

Content

68%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, packed with executable CLI commands and a proxy flags table, and is well-structured into clear sections. Its weaknesses are modest padding, a broken "Step 2" reference, and absent result-validation steps for action runs.

Suggestions

Remove the redundant "Popular actions" section (it repeats the action-list command) and trim the marketing-style Leapfin company description to save tokens.

Resolve the undefined "Step 2" reference — either define that step (e.g. "Step 2: Search and run actions") or remove the cross-reference so the workflow is self-consistent.

Add a validation checkpoint after running actions, e.g. inspect the response `output`/`error` fields and retry or surface failures before proceeding, to satisfy the destructive/batch workflow bar.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but includes unnecessary padding such as the Leapfin company description ("finance automation platform that helps companies streamline their accounting processes") and the redundant "Popular actions" section that repeats the action-list command already shown in "Searching for actions", matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides copy-paste-ready CLI commands throughout (npm install, membrane login, connection ensure, connection get --wait, action list/run, request) plus a complete flags table for proxy requests, covering the common cases fully and executably.	5 / 5
Workflow Clarity	The connection sub-workflow has a clear sequence with a feedback loop (poll --wait, handle READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll), but it references an undefined "Step 2" and the action-running workflow lacks validation/verification of results; the destructive/batch cap holds this at 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references and no bundle files to mismanage; the single inline guide is coherent and appropriately placed, matching the good-structure anchor with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

57%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 explicitly covers both what the skill does and when to use it, and the named app Leapfin keeps conflict risk low. Its main weakness is generic, non-concrete action language and limited trigger-term coverage.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Query Leapfin records, create journal entries and adjustments, and run reconciliation reports."

Broaden trigger phrases to natural variations users say, e.g. "Use when the user wants to query, create, or reconcile Leapfin records, journal entries, adjustments, or reports."

Keep the explicit "Use when..." clause but pair it with the specific Leapfin object types (transactions, journal entries, adjustments) to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the domain and a couple of actions, but the actions are generic ("manage data, records") rather than concrete, fitting the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It states both a what ("Leapfin integration. Manage data, records, and automate workflows.") and an explicit when ("Use when the user wants to interact with Leapfin data."), but the when could be more specific with additional concrete triggers, matching the anchor for both present with room for greater specificity.	4 / 5
Trigger Term Quality	The phrase "Use when the user wants to interact with Leapfin data" supplies a relevant natural keyword ("Leapfin data", "records") but misses common variations or synonyms a user might say, matching the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	Repeatedly naming the specific app Leapfin ("Leapfin integration", "interact with Leapfin data") gives a clear niche with minimal conflict risk, though the generic "manage data, records, automate workflows" phrasing leaves minor overlap with other finance/data skills, matching the mostly-distinct anchor.	4 / 5
	Total	13 / 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/leapfin/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.