Flywire
v1.0.2Flywire integration. Manage data, records, and automate workflows. Use when the user wants to interact with Flywire data.
⭐ 0· 92·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Flywire integration) matches the instructions: all runtime steps use the Membrane CLI to discover connectors, create connections, run actions, or proxy requests to the Flywire API. Nothing in the SKILL.md asks for unrelated cloud credentials, filesystem paths, or services.
Instruction Scope
The SKILL.md stays within the Flywire integration scope, describing membrane login, connection creation, action discovery and proxying. Important note: the instructions route requests through Membrane's proxy/service (which will receive proxied requests and injected auth headers). That is consistent with the skill's purpose but means proxied request payloads will transit Membrane servers — ensure you trust Membrane before sending sensitive data.
Install Mechanism
This is an instruction-only skill (no install spec). It instructs users to install the @membranehq/cli globally via npm and to use npx for some commands. That's a reasonable, proportional choice for a CLI-based integration, but installing global npm packages and executing npx @package@latest runs code from the registry and modifies the system environment — verify the package and maintainers before installing.
Credentials
The skill declares no required environment variables or secrets and instead relies on Membrane to manage authentication via browser login. Requesting a Membrane account and network access is proportionate to the stated functionality.
Persistence & Privilege
The skill is not set to always:true and does not request any persistent system-wide privileges or modify other skills' configs. It operates at the normal agent-invocation level.
Assessment
This skill appears internally consistent: it instructs the agent to use the Membrane CLI to access Flywire and asks for a Membrane account rather than direct API keys. Before installing or running these commands: 1) Verify you trust the @membranehq/cli npm package and the Membrane service (requests and proxied payloads will transit Membrane servers). 2) Be cautious installing global npm packages (they run with your user privileges). 3) Avoid sending extremely sensitive or unrelated data through the proxy unless you're comfortable with the service's policies. 4) If you need stronger assurance, inspect the @membranehq/cli source/release artifacts or use a pinned package version instead of npx @membranehq/cli@latest.Like a lobster shell, security has layers — review code before you run it.
latestvk976jpwk0r8x9h4sdwswbhnr2h8424c6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.