Penneo
v1.0.2Penneo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Penneo data.
⭐ 0· 73·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 skill integrates with Penneo by directing the agent to use the Membrane CLI/proxy rather than calling Penneo APIs directly. The homepage and instructions point to Membrane (getmembrane.com), which is coherent with the described purpose but means the skill depends on a third-party (Membrane) rather than direct Penneo credentials.
Instruction Scope
SKILL.md is explicit about the CLI commands to install and use Membrane, how to create and list connections, run actions, and proxy raw API requests. It does not instruct reading unrelated files, harvesting environment variables, or sending data to unexpected endpoints. It does require interactive browser-based login (with a headless fallback) which is expected for this flow.
Install Mechanism
There is no formal install spec in the registry; the SKILL.md instructs installing the official @membranehq/cli via npm (global or npx). That is a reasonable, low-risk instruction, but the skill does not itself perform installation — the user/agent must run npm or npx to obtain the CLI.
Credentials
The skill declares no required environment variables or credentials and explicitly advises not to ask the user for API keys, because Membrane handles auth. This is proportionate to the stated purpose. The agent will rely on Membrane-managed connections for access to Penneo data.
Persistence & Privilege
The skill is not always-on and uses normal autonomous invocation settings. It does not request persistent system-wide changes or access to other skills' configs.
Assessment
This skill is coherent: it expects you to use the Membrane CLI to connect to Penneo and does not ask for your Penneo API keys. Before installing or running commands, verify you trust the @membranehq/cli npm package and Membrane as the intermediary. Be aware that membrane login opens a browser (or uses a copy-paste code flow in headless environments) to complete authentication — whoever completes that login creates the connection the skill will act through. If you permit the agent to run commands autonomously, it could operate against any existing Membrane connections (including Penneo) with the permissions of that connection, so ensure connections are created with the minimum necessary privileges. If you prefer tighter control, install and run the CLI yourself and create the connection manually rather than letting an automated agent perform the login.Like a lobster shell, security has layers — review code before you run it.
latestvk977h17twqj0499nkwbemzmstn8427z8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.