Faradaysec

v1.0.2

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

0· 98·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Faraday integration) match the instructions: installing the Membrane CLI, creating a connection, listing/running actions, and proxying requests to Faraday are all expected for this purpose.
Instruction Scope
The SKILL.md stays within the stated purpose but explicitly instructs the agent/user to proxy arbitrary API calls through Membrane (membrane request) and to run actions with potentially arbitrary input. That is appropriate for an integration, but it means any data you send will flow through Membrane and the connected Faraday account — review what you allow the skill to do after connection.
Install Mechanism
Install instructions ask the user to run `npm install -g @membranehq/cli`. This is a public npm package (moderate risk compared with no install); it requires global npm privileges and will put a CLI on your system. The install mechanism is proportionate but you should verify the package source if you care about supply-chain risk.
Credentials
The skill requests no environment variables or local config paths and delegates authentication to Membrane. That aligns with the described design (Membrane manages credentials).
Persistence & Privilege
always:false and normal autonomous invocation are used. This is standard, but if you allow the skill to be invoked autonomously and you create a Faraday connection, the skill could run actions (including reads/changes) against that account — grant only the minimum-permission connection you trust.
Assessment
This skill appears to be what it says: a Faraday integration that relies on the Membrane CLI. Before installing or connecting: (1) Confirm you trust the @membranehq/cli npm package and its GitHub/source; (2) be aware `npm install -g` modifies your system and may require elevated privileges — consider a local or containerized install if concerned; (3) understand that Membrane will proxy requests and handle auth, so any data you send through the skill will be routed via Membrane to Faraday; only connect accounts with appropriate, least-privilege access and review the actions the skill runs before allowing autonomous execution.

Like a lobster shell, security has layers — review code before you run it.

latestvk979ebq1e73177emr8jhkkavsd843k9p

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments