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

ibanfirst

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

Quality

64%

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

Quality

Content

88%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 strong, executable integration guide: concrete CLI commands, explicit state-handling with a re-poll feedback loop, and a clean proxy fallback. Its main weakness is the unnecessary opening paragraph explaining what IBanFirst is, and a self-contained layout that could offload reference material into bundle files now that none exist.

Suggestions

Trim or remove the introductory paragraph explaining what IBanFirst is as a financial platform; Claude does not need this background.

Fix the dangling 'Step 2' reference (the section is labeled '#### 1b' with no explicit 'Step 2' header) so the sequence reads unambiguously.

Consider moving the proxy flag table and clientAction schema details into a reference bundle file to keep SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and executable (CLI commands, a flag table, state-handling bullets), with only minor over-explanation such as the opening paragraph describing what IBanFirst is as a financial platform.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands across the common cases — install, login, connection ensure, polling, action list/run with JSON input, and proxy requests with a full flag table.	5 / 5
Workflow Clarity	The flow is clearly sequenced (install -> login -> connection ensure -> poll state -> search actions -> run/proxy) with explicit validation checkpoints and a feedback loop for CLIENT_ACTION_REQUIRED (user acts, then re-poll) and CONFIGURATION_ERROR (inspect error field).	5 / 5
Progressive Disclosure	Sections are well-organized with clear headers and only a one-level external link (official docs); there are no bundle files and no nested references, though the single self-contained doc is longer than the ~50-line 'simple skill' threshold so the structure, while good, is not maximally split.	4 / 5
	Total	18 / 20 Passed

Description

41%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 anchors itself to the IBanFirst niche and includes a 'Use when' trigger, but its stated capabilities are generic boilerplate ('manage data, records, automate workflows') rather than the concrete financial actions the API exposes. Adding specific verbs (payouts, transfers, rates, accounts) and broader trigger synonyms would materially raise specificity, trigger quality, and completeness.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions such as 'list and create payouts, transfers, and beneficiaries; query accounts, transactions, and exchange rates.'

Expand the 'Use when' clause with natural user phrasings, e.g. 'Use when the user mentions IBanFirst, international payments, multi-currency payouts, transfers, or exchange rates.'

Keep third person ('Manages... Interacts...') and add a reference to the API or developers.ibanfirst.com domain to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('IBanFirst integration') but its actions are generic ('Manage data, records, and automate workflows') with no concrete verbs tied to the actual API surface such as payouts, transfers, or rates.	2 / 5
Completeness	Both a 'what' and a 'when' are present ('Manage data, records...' / 'Use when the user wants to interact with IBanFirst data'), but the 'what' is vague and the 'when' is generic, sitting below the score-4 anchor which expects a clearer statement of capabilities.	3 / 5
Trigger Term Quality	Only the proper noun 'IBanFirst' recurs; there are no natural user synonyms or phrasings like 'IBanFirst API,' 'international payments,' 'payouts,' or 'rates,' leaving keyword coverage noticeably thin.	2 / 5
Distinctiveness Conflict Risk	The 'IBanFirst' proper-noun niche is distinct and unlikely to trigger for the wrong skill, though the generic 'manage data, records, and automate workflows' boilerplate leaves minor overlap risk with other integration skills.	4 / 5
	Total	11 / 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/ibanfirst/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.