Perplexity

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

This skill appears to genuinely wrap Perplexity access through the Membrane CLI, but before installing or using it you should: (1) verify the Membrane CLI package on npm (publisher @membranehq) and prefer running it via npx if you don't want a global install; (2) confirm the GitHub repo/homepage (getmembrane.com and the listed repository) match the package you install; (3) be aware the skill requires you to authenticate to Membrane (browser-based or code flow) and to create a Perplexity connector — that will grant Membrane access to Perplexity on your behalf, so review Membrane's privacy/security docs; (4) ask the skill author or registry to declare the required binary (membrane CLI) in the metadata or provide a formal install spec if you want automated installation; and (5) avoid pasting unrelated secrets into any prompts. The main issues are metadata omissions and a moderate install-time risk from a global npm install — not direct evidence of malicious behavior, but enough reason to review the package and provider first.

Type: OpenClaw Skill Name: perplexity-integration Version: 1.0.1 The skill provides instructions for an AI agent to integrate with Perplexity via the Membrane framework. It directs the agent to install the Membrane CLI (@membranehq/cli), authenticate through their service (getmembrane.com), and manage API actions through Membrane's middleware. While the process involves high-privilege actions like global NPM package installation and routing data through a third-party platform, these behaviors are transparently documented and strictly aligned with the stated purpose of the integration. The instructions also include security best practices, such as advising the agent to let the platform handle credential lifecycles rather than requesting raw API keys from the user.