Name: fondy
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

fondy

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

Quality

66%

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

Quality

Content

76%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 executable commands and a clear connection workflow, but it omits validation/confirmation steps for potentially destructive payment operations, which caps workflow clarity, and relies on one monolithic file rather than progressive references.

Suggestions

Add a verification/confirmation checkpoint before running payment-creating or proxy actions (e.g. confirm amount and currency with the user, then re-check the action outputSchema for idempotency keys).

Fix the dangling 'Skip to Step 2' reference by adding an explicit numbered Step 2 header so the sequence is unambiguous.

Move the action-list/proxy flag detail into a references/ file and keep SKILL.md as a lean overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Quotes tight command blocks like 'membrane connection ensure "https://fondy.eu/" --json' with minimal prose; the opening 'Fondy is a payment gateway... used by e-commerce businesses, SaaS companies' is mild audience padding but overall efficient, fitting anchor 4.	4 / 5
Actionability	Quotes copy-paste-ready commands such as 'membrane action run <actionId> --connectionId=CONNECTION_ID --input \'{"key": "value"}\' --json' and the proxy flags table, covering the common cases with fully executable guidance per anchor 5.	5 / 5
Workflow Clarity	Quotes the connect-and-poll sequence ('poll until state is no longer BUILDING', READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR branches), but running or proxying potentially irreversible payment actions lacks any validation or confirmation checkpoint, so the destructive-operation cap holds at 3.	3 / 5
Progressive Disclosure	Quotes clearly labeled sections ('## Working with Fondy', '### Connecting to Fondy', '## Best practices') in a single self-contained file with no bundle references; well-organized but a 137-line monolith whose action/proxy detail could be split, matching anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

57%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 includes an explicit 'Use when...' trigger and answers both what and when, but its actions are generic rather than reflecting Fondy's concrete payment/invoice/report capabilities, limiting specificity and trigger richness.

Suggestions

Replace generic verbs with Fondy-specific actions, e.g. 'Create and verify payment invoices, retrieve transaction reports, and automate payment workflows.'

Expand the trigger clause with natural user phrases: 'Use when the user wants to accept payments, create invoices, or query Fondy transaction data.'

Add file/URL or format cues (e.g. referencing the Fondy API) to sharpen distinctiveness from generic data skills.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' — it names the Fondy domain but the actions are generic verbs not tied to Fondy's actual payment/invoice/report capabilities, so it sits below the midpoint between anchors 2 and 3.	2 / 5
Completeness	Quotes both 'Manage data, records, and automate workflows' (what) and 'Use when the user wants to interact with Fondy data' (when); the 'when' clause is present and explicit but could be more specific, fitting anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Quotes 'Use when the user wants to interact with Fondy data' — it offers the brand term plus a natural-ish trigger phrase, but misses common variations users would say like payments, invoices, or refunds, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	Quotes 'Fondy integration' and 'interact with Fondy data' — the brand-specific name gives it a clear niche with minimal conflict risk, though the generic 'data' trigger leaves minor overlap, matching anchor 4.	4 / 5
	Total	13 / 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/fondy/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.