Ringba

Name/description (Ringba integration) match the instructions: the SKILL.md directs the agent to use the Membrane CLI to connect to Ringba, discover and run actions, and create actions when needed. No unrelated capabilities or credentials are requested.

Instructions are scoped to installing and using the Membrane CLI, authenticating via browser/URL, creating a connection to Ringba, discovering and running actions. They require network access and routing requests through Membrane. The SKILL.md explicitly instructs not to collect user API keys (use Membrane connections instead). Because Membrane handles auth server‑side, Ringba access and action execution will involve sending data/credentials to Membrane — this is expected for the stated design but is an important privacy consideration.

This is instruction-only with no install spec in the registry, but the README tells users to install the Membrane CLI via npm (global install) or run via npx. Using npm/npx is common and traceable to the @membranehq package on the public registry; it's not an arbitrary binary download. Consider using npx to avoid a persistent global install if you prefer less footprint.

The skill declares no required env vars or local credentials, which is consistent with delegating auth to Membrane. However, because Membrane manages the auth lifecycle server‑side, the user should be aware that Ringba credentials and API access will be handled by Membrane's service rather than kept locally.

always is false, there are no requested config paths, and the skill does not ask to modify other skills or system config. Autonomous invocation is allowed (default) but not combined with other red flags.