Finch
v1.0.0Finch integration. Manage data, records, and automate workflows. Use when the user wants to interact with Finch data.
⭐ 0· 60·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's name/description (Finch integration) matches the instructions (use Membrane to access Finch). Minor inconsistency: the registry metadata lists no required binaries, but SKILL.md explicitly instructs installing the @membranehq/cli npm package and using the membrane CLI.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to the Finch API. They do not instruct reading unrelated files, exporting secrets, or arbitrary system interrogation.
Install Mechanism
There is no platform install spec; SKILL.md directs the user to run `npm install -g @membranehq/cli` (and examples using npx). Installing a global npm package writes code to disk and should be verified. The package and repository are publicly referenced (membranehq/membranedev), reducing but not eliminating risk.
Credentials
No environment variables or credentials are requested by the skill. SKILL.md explicitly recommends letting Membrane manage auth via browser-based login and advises not to ask users for API keys — this is proportional to the described functionality.
Persistence & Privilege
The skill does not request always-on presence and is instruction-only. It does not attempt to modify other skills or system-wide agent settings. The main privilege is asking users to install a CLI, which is an expected level of persistence for this integration.
Assessment
This skill is coherently focused on using the Membrane CLI to access Finch. Before installing: verify the @membranehq/cli package on npm and the GitHub repository (review recent commits, maintainers, and npm publisher), prefer running with npx or in a controlled environment if you don't want a global install, and only authenticate with your browser if you trust Membrane. Be cautious installing global npm packages on shared machines. Note the small metadata mismatch (registry lists no required binaries while the README instructs installing the CLI) — not a safety failure, but you may want to confirm installation expectations.Like a lobster shell, security has layers — review code before you run it.
latestvk97fsc544bxcq2t153zpmptam984ap2v
License
MIT-0
Free to use, modify, and redistribute. No attribution required.