Name: salt-edge
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

salt-edge

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/salt-edge/SKILL.md

Quality

Content

61%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 well-structured, actionable CLI reference with strong command examples, but it includes some concept padding and its destructive action/proxy workflows lack explicit validation checkpoints. The broken "Step 2" reference also weakens workflow clarity.

Suggestions

Add an explicit validation/verification checkpoint before running actions or proxy requests that could be destructive (e.g. confirm the action's outputSchema or dry-run a payment before initiating).

Fix the dangling "skip to Step 2" reference by labeling the corresponding section (e.g. "## Step 2: Search and run actions").

Trim the opening paragraph explaining what Salt Edge is and remove the filler line "When to use which actions: Use action names and parameters as needed." to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command reference, but it pads with concepts Claude knows ("Salt Edge is a service that provides open banking solutions...") and filler like "When to use which actions: Use action names and parameters as needed.", fitting the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	Concrete executable commands throughout (install, login, connection ensure, action list/run, request with a full flag table), with only minor gaps like placeholder CONNECTION_ID/actionId values, matching the score-4 anchor.	4 / 5
Workflow Clarity	The connect-to-poll-to-action sequence is present with state-polling checkpoints, but it references a "Step 2" that is never labeled and the action-run/proxy-request flow (which can initiate payments or send DELETE/POST) lacks explicit validation, so the destructive-operation cap of 3 applies.	3 / 5
Progressive Disclosure	Content is organized into clear headed sections with no nested references and a single external docs link; it is over 50 lines so the simple-skill exception does not apply, but the structure is good with only minor organization gaps, matching the score-4 anchor.	4 / 5
	Total	14 / 20 Passed

Description

61%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 answers what and when and is well-distinctived by the Salt Edge niche, but its actions are generic and it lacks natural keyword synonyms. It uses correct third-person voice throughout.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Salt Edge capabilities such as listing connections, fetching transactions, or initiating payments.

Add natural trigger synonyms users might actually say, e.g. "Use when the user wants to access bank account data, fetch transactions, or initiate payments via Salt Edge."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain (Salt Edge) but the actions are generic abstractions rather than concrete capabilities, matching the score-2 anchor of minimal/generic actions.	2 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Salt Edge data"), but the trigger could be more specific about which interactions, matching the score-4 anchor.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Salt Edge data" surfaces the key term "Salt Edge" but misses natural synonyms users might say (open banking, bank accounts, payments), fitting the score-3 anchor of some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"Salt Edge" is a distinct, named niche service with a unique trigger phrase, giving it minimal conflict risk with other skills per the score-5 anchor.	5 / 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/salt-edge/SKILL.md
Commit: f484c82

Reviewed: 4 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.