Pact Foundation

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

This skill appears to implement a Pact integration by driving the Membrane CLI, which is consistent with its description — but notice the manifest claims no required tools while the SKILL.md requires installing @membranehq/cli. Before installing/use: 1) Verify the @membranehq/cli package on the npm registry and the publisher's website (getmembrane.com) to ensure you're installing the legitimate package. 2) Prefer running commands via npx for one-off usage or install in an isolated environment/container rather than doing a global npm install. 3) Understand the login flow: you'll perform an interactive/browser auth and the CLI will store tokens/connection IDs locally. If you cannot or do not want to install third-party CLIs or grant network/browser-based auth, avoid using the skill. 4) Ask the publisher for an explicit install spec (package version and checksum) and clarification why the registry metadata lists no required binaries while SKILL.md requires the Membrane CLI — that mismatch would change this assessment if resolved.

Type: OpenClaw Skill Name: pact-foundation Version: 1.0.1 The skill requires the installation of a global npm package (@membranehq/cli) and delegates all authentication and API interactions to a third-party service (Membrane). While these actions are aligned with the stated purpose of the Pact Foundation integration, the reliance on an external CLI for credential management and the 'action create' feature—which generates logic on a remote server—introduces a significant trust dependency and broad shell/network access risks (SKILL.md).