Name: formance
Rating: 60.8 (1 reviews)
Author: membranedev

formance

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/formance/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 an executable, well-structured integration guide with concrete commands and a clear connection state-machine workflow. Minor gaps are the dangling 'Step 2' reference and the absence of action-result validation.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with executable command blocks and minimal concept explanation, though a few prose lines (e.g. 'so you can focus on the integration logic rather than auth plumbing') could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready bash commands for login, connection ensure/get, action list/run, and proxy requests, with a flag table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with a state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED) and re-polling feedback loop, but the text references an undefined 'Step 2' and offers no validation of action-run results.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files present; structure is good though some reference-like material (the proxy flag table) is inlined.	4 / 5
	Total	17 / 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 distinct and has an explicit trigger clause, but its capability list is generic rather than reflecting Formance's concrete financial primitives. Specificity and trigger-term coverage are the main weaknesses.

Suggestions

Replace generic verbs with concrete Formance actions, e.g. 'Post ledger transactions, manage accounts, and automate payment workflows.'

Expand the trigger to surface natural phrases users say, e.g. 'Use when working with Formance ledgers, transactions, accounts, or payment flows.'

Keep the concise third-person voice but tie each listed action to a Formance concept so the 'what' is as specific as the 'when'.

Dimension	Reasoning	Score
Specificity	The description names the Formance domain but the actions — 'Manage data, records, and automate workflows' — are generic rather than concrete Formance-specific operations (e.g. posting ledger transactions, creating accounts).	2 / 5
Completeness	Both a 'what' (manage data/records, automate workflows) and an explicit 'when' clause are present, though the 'what' is generic and the 'when' could name concrete triggers.	4 / 5
Trigger Term Quality	It includes the relevant keyword 'Formance' and an explicit trigger ('Use when the user wants to interact with Formance data'), but lacks natural synonyms or variations a user might say.	3 / 5
Distinctiveness Conflict Risk	Formance is a specific named platform with a distinct trigger ('interact with Formance data'), giving it a clear niche with minimal conflict risk against other skills.	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/formance/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.