Name: transfi
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

transfi

TransFi integration. Manage Recordses. Use when the user wants to interact with TransFi data.

Quality

62%

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/transfi/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 is highly actionable with executable CLI commands and a clearly sequenced, state-aware connection workflow, supported by good section structure. Its main weakness is token efficiency: a marketing-style intro and some command repetition pad the content without adding guidance value.

Suggestions

Trim or remove the opening marketing paragraph about cost reduction and conversion rates; Claude does not need TransFi's value proposition to operate the integration.

Add one concrete Records example with real input and output (e.g. `membrane action run <recordsCreateId> --input '{"name": ...}'`) so the core domain object has a copy-paste-ready illustration.

Resolve the dangling "skip to Step 2" / "1b" numbering so the connection workflow reads as a coherent numbered sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening marketing paragraph ("helps businesses manage and optimize... reduce costs, increase conversion rates, improve the overall payment experience") and the repeated `action list` command in both "Searching for actions" and "Popular actions" add unnecessary tokens.	3 / 5
Actionability	Commands are copy-paste ready and cover the common cases (install, login, connection ensure, action run, request proxy) with a flags table, but no concrete Records example with real input/output is shown — only generic `<actionId>` placeholders, leaving a minor gap.	4 / 5
Workflow Clarity	The connection flow is well sequenced with a real poll-and-check-state feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the dangling "skip to Step 2" reference and "1b" heading with no matching Step 1/2 leave a minor sequencing gap.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is organized into clear sections with no nested references, so structure is good and self-contained; it is not a 5 only because there are no explicit one-level-deep references to signal and the inlined action/proxy detail could arguably live in a reference file.	4 / 5
	Total	15 / 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 successfully pairs a clear 'what' with an explicit 'Use when' trigger and names a distinctive platform, but its action vocabulary is minimal and trigger-term coverage is thin. Tightening the action list and adding natural synonyms would lift the weaker dimensions.

Suggestions

Replace the generic "Manage Recordses" with concrete operations, e.g. "Create, read, update, delete, and list TransFi Records" to improve specificity.

Expand the trigger phrase with natural variations users would actually say, e.g. "Use when the user wants to query, create, or update TransFi Records or TransFi payment data."

Fix the awkward plural "Recordses" to "Records" so the natural keyword matches what users will say.

Dimension	Reasoning	Score
Specificity	The description names the domain ("TransFi integration") but the only action is the generic verb "Manage Recordses", comparable to the score-2 anchor "Processes PDF files" rather than 1-2 distinct concrete actions.	2 / 5
Completeness	Both halves are present and explicit — what ("TransFi integration. Manage Recordses.") and when ("Use when the user wants to interact with TransFi data") — matching the score-4 anchor, though the trigger could name more concrete use cases.	4 / 5
Trigger Term Quality	"TransFi" is a genuine natural keyword a user would say, and "Use when the user wants to interact with TransFi data" supplies a trigger, but coverage is thin and the awkward "Recordses" lacks common synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific TransFi platform gives it a clear, mostly-distinct niche with minimal overlap risk, but the generic "interact with TransFi data" trigger is not as sharply differentiated as a score-5 example.	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/transfi/SKILL.md
Commit: f484c82

Reviewed: 4 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.