Name: flywire
Rating: 56.8 (1 reviews)
Author: membranedev

flywire

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

Quality

65%

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

Quality

Content

68%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 content delivers concrete, executable Membrane commands and a well-structured connection workflow with good state feedback loops, but a broken "Step 2" reference and the absence of validation around potentially destructive action execution hold back workflow clarity. Minor redundancy and generic placeholders could be tightened.

Suggestions

Fix the navigation: label the post-connection section "Step 2: Run actions" so the "skip to Step 2" references resolve.

Add a validation/checkpoint step before running write actions on the payment platform, e.g. confirm the action's inputSchema and dry-run intent before executing destructive operations.

Collapse the redundant "Popular actions" and "Searching for actions" sections, and replace generic placeholders with one realistic action-run example (e.g. listing payment requests).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and operational steps; the only over-explanation is the opening paragraph describing what Flywire is and the duplicated action-list command under "Popular actions", which are minor trimmable instances.	4 / 5
Actionability	Concrete, executable `membrane` commands and a flags table cover install, auth, connection, actions, and proxy, but examples rely on generic placeholders ("{\"key\": \"value\"}", "/path/to/endpoint") and no real action-run example is shown, leaving minor gaps.	4 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with strong connection-state feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED polling), but the "skip to Step 2" reference points to no labeled Step 2, and there is no validation checkpoint around running actions on a payment platform where operations can be destructive.	3 / 5
Progressive Disclosure	The single file is well-sectioned into Overview, Working with Flywire, Auth, Connecting, Searching, Popular actions, Proxy, and Best practices with no nested references, but at ~140 lines with minor redundancy between "Popular actions" and "Searching for actions" the organization has minor gaps.	4 / 5
	Total	15 / 20 Passed

Description

62%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 correctly includes both a what and a Use-when clause and leverages a distinctive brand name, but its actions are generic and it omits the payment-specific trigger terms users would naturally say. Tightening the actions and adding payment-related triggers would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete actions, e.g. "Create and track payment requests, manage payers, and review payment options".

Add payment-specific trigger terms users actually say, e.g. "Use when the user wants to send or track Flywire payments, manage payers, or check payment status".

Mention cross-border payments or currency conversion as triggers to better distinguish this from generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the Flywire domain and lists action areas ("Manage data, records, and automate workflows"), but the actions are generic/abstract rather than concrete like "extract text" or "fill forms", so it sits at the domain-plus-actions-but-not-comprehensive anchor.	3 / 5
Completeness	Both a "what" ("Flywire integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Flywire data") are present, but the trigger is generic rather than concrete phrases, matching the both-present-but-could-be-more-specific anchor.	4 / 5
Trigger Term Quality	The brand term "Flywire" and the trigger "interact with Flywire data" are present, but the natural terms a user would actually say ("payments", "cross-border payments", "currency conversion", "payment requests") are entirely missing, leaving only some relevant keywords without common variations.	3 / 5
Distinctiveness Conflict Risk	"Flywire" is a unique proper noun giving the skill a clear niche with minimal conflict risk, but the generic action language ("manage data, records, workflows") leaves minor overlap risk with other data-management skills.	4 / 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/flywire/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.