Name: ibanity
Rating: 56.8 (1 reviews)
Author: membranedev

ibanity

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

Quality

65%

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/ibanity/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 with ready-to-run Membrane CLI commands and a clear connection state machine, but it carries some unnecessary explanatory padding, a broken 'Step 2' cross-reference, and no validation guidance before executing potentially destructive actions.

Suggestions

Fix or remove the dangling 'Step 2' references (e.g., label the connection and action-run phases explicitly) so the sequence is navigable.

Add a validation/checkpoint step before running write or payment actions, such as confirming the action's inputSchema and previewing the call before execution.

Trim the intro platform description and fold the duplicate action-list command in 'Popular actions' into the earlier 'Searching for actions' section to save tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the introductory platform explanation ("Ibanity is a platform that provides open banking APIs..."), the verbose clientAction enumeration, and the redundant "Popular actions" section that repeats the action-list command add padding that could be trimmed, fitting the 'Mostly efficient but includes some unnecessary explanation' anchor rather than the lean anchor at 4.	3 / 5
Actionability	Copy-paste-ready commands appear throughout ("membrane connection ensure", "membrane action run <actionId> --input '{...}'", "membrane request CONNECTION_ID /path"), and the proxy flag table covers the common cases, matching the 'Fully executable; copy-paste ready' top anchor.	5 / 5
Workflow Clarity	A sequenced connect-then-poll flow with a state-checkpoint retry loop exists, but the text references a "Step 2" that is never defined and there are no validation steps before running actions (which can be destructive writes), so it sits at 'Steps listed but validation gaps' rather than the clear-checkpoint anchor at 4.	3 / 5
Progressive Disclosure	The ~155-line body is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references, fitting 'Good structure; most content appropriately placed'; it is not the well-signaled multi-file reference pattern at 5, and not the inlined-wall-of-text anchor at 3.	4 / 5
	Total	15 / 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 names a distinct, specific platform and includes an explicit 'Use when' trigger, but the capability actions are generic ('manage data, records') rather than concrete, and trigger-term coverage relies on a single proper noun with no synonyms.

Suggestions

Replace generic verbs with concrete Ibanity actions, e.g. 'List account access requests, fetch customer records, and synchronize financial-institution data'.

Add natural trigger variations such as 'open banking', 'European bank data', or 'payment initiation' alongside 'Ibanity'.

Tighten the 'when' clause to specific intents, e.g. 'Use when the user wants to query Ibanity banking data or initiate payments.'

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the Ibanity domain but the actions are minimal and generic, matching the anchor 'Names the domain but actions are minimal or generic' rather than the concrete-action anchor above.	2 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Ibanity data") are present; because the 'Use when' trigger is explicit it is not capped at 3, but the generic 'what' keeps it below the concrete-trigger anchor at 5.	4 / 5
Trigger Term Quality	The single natural keyword "Ibanity" ("Use when the user wants to interact with Ibanity data") is relevant but lacks synonyms or file extensions, fitting the 'Some relevant keywords but missing common variations' anchor and not the comprehensive anchor at 5.	3 / 5
Distinctiveness Conflict Risk	"Ibanity integration" targets a single specific platform with distinct triggers, giving it a clear niche and minimal conflict risk per the top anchor; it is not the broad-overlap anchor at 4.	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/ibanity/SKILL.md
Commit: f484c82

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