Fonoa
v1.0.0Fonoa integration. Manage data, records, and automate workflows. Use when the user wants to interact with Fonoa data.
⭐ 0· 91·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 name/description (Fonoa integration) aligns with the instructions: the SKILL.md explains how to use the Membrane CLI to connect to Fonoa, list actions, run actions, and proxy requests. There are no unrelated credential or system requirements declared.
Instruction Scope
Instructions are narrowly scoped to installing/using the Membrane CLI and interacting with connections/actions/requests for Fonoa. They do not instruct reading arbitrary system files or exfiltrating environment variables; authentication is performed via Membrane's browser login flow as described.
Install Mechanism
This is an instruction-only skill (no install spec). The doc recommends installing @membranehq/cli via npm (global install). That is a reasonable approach for this integration, but installing a third-party CLI pulls code from the public npm registry — users should confirm they trust the package and its publisher. The skill itself will not auto-install anything.
Credentials
The skill declares no required environment variables or credentials. Authentication is delegated to Membrane via an interactive browser login and per-connection flows. No broad secrets (AWS keys, generic tokens, etc.) are requested or documented.
Persistence & Privilege
The skill is not always-enabled and does not request special persistent privileges or modify other skills. It relies on user-invoked CLI operations and standard Membrane-managed connections.
Assessment
This skill is coherent for interacting with Fonoa through Membrane, but before proceeding: (1) confirm you trust the @membranehq/cli npm package and its publisher (installing it runs third-party code on your machine); (2) be aware that authentication uses a browser login which grants Membrane access to the connected Fonoa account — review Membrane's privacy/security docs and permissions for connector access; (3) the skill will not auto-install the CLI or request other credentials, so you must install and log in yourself in environments where interactive browser auth is required (headless flow is documented). If you need higher assurance, review the CLI source (GitHub repo) and Membrane's docs before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97bmr4q0ct6nh5qphy2h4zx1984gfwd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.