Mercury

Mercury integration. Manage Organizations. Use when the user wants to interact with Mercury data.

What to consider before installing/using this skill: - Trust the intermediary: This skill relies on the Membrane service and its CLI. All Mercury API requests and authentication flows will be mediated by Membrane, so sensitive account and transaction data will route through their infrastructure—confirm you trust Membrane and understand their data handling/privacy policies. - CLI installation: The README tells you to run 'npm install -g @membranehq/cli'. That installs a program globally on your machine and may require administrator privileges. Only install packages from sources you trust and verify the package name and maintainer. - Docs mismatch: The SKILL.md contains a link to an unrelated 'Mercury web-parser' doc (Postlight). This looks like an editorial error; verify with the skill author or repository that the integration targets the Mercury service you expect (banking vs web-parser) before granting access. - Least privilege: When creating connections in Membrane, review the scopes/permissions requested by the connector and grant only what's necessary. - If you need stronger assurance: ask the skill author for the source repository or a signed release of the CLI, and verify Membrane's privacy/security documentation and SOC/ISO attestations (if applicable) before using the skill with sensitive financial data.

Type: OpenClaw Skill Name: mercury Version: 1.0.2 The skill provides a standard integration for the Mercury banking platform using the Membrane CLI. While the documentation in SKILL.md contains minor errors (such as a placeholder LLM refusal message and a link to the unrelated Mercury Web Parser), the core logic and instructions are consistent with the stated purpose of managing financial data. It follows security best practices by delegating authentication and secret management to the Membrane platform rather than requesting or storing API keys locally.