Name: finastra
Rating: 62.4 (1 reviews)
Author: membranedev

finastra

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

Quality

74%

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

Quality

Content

82%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 copy-paste-ready CLI commands and a well-structured connection workflow including state-driven feedback loops. Minor conciseness redundancy and a small workflow numbering inconsistency prevent a top score.

Suggestions

Remove the duplicated `membrane action list --intent=QUERY` command from 'Popular actions' or merge that section into 'Searching for actions' to avoid redundancy.

Fix the workflow numbering: label a clear 'Step 2' (e.g. searching/running actions) and reconcile the '1b' heading with a '1a', or drop the numbered-suffix scheme.

Tighten or relocate the introductory 'Finastra is a large financial technology company...' paragraph, which explains a vendor Claude can look up rather than skill-specific guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands, flags, and a table, but has minor over-explanation: the opening 'Finastra is a large financial technology company...' paragraph and a duplicated action-list command in both 'Searching for actions' and 'Popular actions'. It is more efficient than anchor 3 but not perfectly lean.	4 / 5
Actionability	Commands are fully executable and copy-paste ready across the common cases — install, login (interactive and headless), connection ensure/get, action list/run, and proxy requests — with flag tables and JSON input examples, matching anchor 5.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a feedback loop (poll again after the user acts), but the numbering is inconsistent ('1b', 'Step 2' with no labeled Step 2) and action execution lacks result validation, keeping it below anchor 5.	4 / 5
Progressive Disclosure	The body is well-organized into clearly-headed sections with no deep nesting and no bundle files to misreference; all content is appropriately inline for this skill. It falls short of anchor 5 only because nothing is split out into one-level-deep reference files, which is acceptable here but not exemplary.	4 / 5
	Total	17 / 20 Passed

Description

66%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 is highly distinct because it names a specific vendor. It is held back by generic action verbs and a single trigger keyword with no synonyms or product variations.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with concrete Finastra actions such as 'query account balances, list transactions, initiate payments, manage beneficiaries'.

Expand the 'Use when' trigger to include natural user phrases and product names, e.g. 'Use when the user wants to query Finastra/FusionFabric account balances, transactions, payments, or statements'.

Add common synonyms or file/API extensions users might mention (FusionFabric.cloud, Finastra API) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Finastra domain and lists a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete like the anchor 3 example; not comprehensive enough for a 4.	3 / 5
Completeness	Both a clear 'what' ("Finastra integration. Manage data, records, and automate workflows.") and an explicit 'when' ("Use when the user wants to interact with Finastra data.") are present, but the trigger guidance is a single phrase rather than multiple concrete triggers, so it falls short of anchor 5.	4 / 5
Trigger Term Quality	The single relevant keyword "Finastra" appears, but there are no synonyms, variations, or product names (e.g. FusionFabric.cloud), matching anchor 3's 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The description targets a clear niche (the specific company Finastra) with a distinct trigger ("interact with Finastra data"), giving minimal conflict risk with other skills, matching anchor 5.	5 / 5
	Total	15 / 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/finastra/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.