Name: finapi
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

finapi

FinAPI integration. Manage data, records, and automate workflows. Use when the user wants to interact with FinAPI 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/finapi/SKILL.md

Quality

Content

67%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 delivers concrete, executable Membrane CLI guidance with a sensible connect-and-poll workflow and feedback handling for connection states. The main weaknesses are mild verbosity in the introductory/background prose and loosely numbered workflow steps that could be tightened into an explicit checklist.

Suggestions

Trim the opening 'FinAPI is a German open banking platform...' paragraph to one line of only-the-essential context Claude would not already know.

Re-number the connection workflow as an explicit ordered checklist (1. install, 2. authenticate, 3. ensure connection, 4. poll until READY, 5. search/run) with a clear validation gate before running actions.

Condense the clientAction field enumeration into a compact reference table to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening paragraph ('FinAPI is a German open banking platform...') and the detailed clientAction field explanations add unnecessary background, fitting 'Mostly efficient but includes some unnecessary explanation.' It is above 2 because the core CLI guidance is tight and unpadded.	3 / 5
Actionability	Concrete, copy-paste-ready commands (`membrane connection ensure`, `membrane action run`, `membrane request`) with a flags table cover the common cases, matching 'Mostly executable guidance; concrete code or commands with minor gaps.' It does not reach 5 because CONNECTION_ID and parameter placeholders leave small gaps for the reader to fill.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-until-ready → search → run sequence includes a feedback loop (CLIENT_ACTION_REQUIRED → user acts → poll again), matching 'Clear sequence with most checkpoints present; minor validation gaps.' It is below 5 because step numbering is loose (a 'Step 2' is referenced without a clearly labeled Step 1) and checkpoints are implicit rather than a clean checklist.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Overview, Working with FinAPI, Authentication, Connecting, Popular actions, Best practices) with no nested or buried references, and no bundle files are present to mis-signal, matching 'Good structure; most content appropriately placed.' It does not reach 5 because the file exceeds 50 lines and inlines content (clientAction details, proxy flags) that, while reasonable here, keeps it just shy of the clean overview-plus-refs ideal.	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 is a focused, third-person trigger for a specific named product with an explicit 'Use when' clause, but its capability list relies on generic verbs ('manage', 'automate') rather than concrete actions. Strengthening the action specificity and adding trigger synonyms would raise it.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete FinAPI actions such as 'query transactions, initiate payments, and sync account data'.

Add natural trigger synonyms/variations (e.g. 'FinAPI, open banking, bank account data, payment initiation') to broaden keyword coverage.

Tighten the 'what' so it lists 2-3 specific capabilities a user would actually request.

Dimension	Reasoning	Score
Specificity	The description names the FinAPI domain but its actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete verbs like extract or fill, matching the anchor 'Names the domain but actions are minimal or generic.' It does not reach 3 because it lists no genuinely concrete action.	2 / 5
Completeness	It states a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with FinAPI data'), matching 'Has both what and when; when could be more explicit.' It stops short of 5 because the 'what' is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with FinAPI data' supplies the natural product keyword 'FinAPI', but coverage lacks common variations or synonyms, fitting 'Some relevant keywords but missing common variations.' It is above 2 because a real user-triggered phrase is present.	3 / 5
Distinctiveness Conflict Risk	Targeting a specific named product (FinAPI) with the trigger 'interact with FinAPI data' gives a clear niche with minimal overlap risk, matching 'Clear niche with distinct triggers; minimal conflict risk.'	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/finapi/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.