Financialforce

v1.0.2

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

0· 74·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
medium confidence
Purpose & Capability
Name/description say 'FinancialForce integration' and the SKILL.md only describes using the Membrane CLI and proxy to list actions, create connections, run actions, and proxy FinancialForce API calls — all coherent with the stated purpose.
Instruction Scope
Instructions are focused on installing the Membrane CLI, logging in, creating/listing connections, running actions, and proxying API requests. They do not ask the agent to read unrelated files, environment variables, or system config.
Install Mechanism
There is no registry install spec, but the SKILL.md advises running `npm install -g @membranehq/cli`. Installing a global npm package is a normal step for a CLI integration but does modify the system PATH and pulls code from the npm registry; verify the package's origin and reputation before installing.
Credentials
The skill declares no required env vars or credentials and instructs using Membrane-managed browser auth. This is proportionate, but it means you must trust Membrane (getmembrane.com / @membranehq) to handle and possibly store/relay FinancialForce credentials and proxied data.
Persistence & Privilege
Skill is instruction-only, requests no persistent system presence, and does not set always:true. Default autonomous invocation is allowed (platform default) but the skill itself does not request elevated persistence or cross-skill config changes.
Assessment
This skill is coherent: it simply teaches the agent to use the Membrane CLI to interact with FinancialForce. Before installing or following its steps, verify the Membrane CLI package and its publisher (@membranehq) on the npm registry and GitHub. Understand that using the proxy means Membrane will see API traffic and handle auth for you — if your FinancialForce data is sensitive, confirm Membrane’s data handling, storage, and security policies. Installing a global npm package will modify your system environment (requires npm and appropriate permissions). If you prefer not to trust a third party with credentials/data, consider using your own direct FinancialForce integration or ephemeral/test accounts.

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

latestvk972gs4jsh2yjgdpqh95cqj659843ejm

License

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

Comments