Built Accounting
v1.0.2Built Accounting integration. Manage data, records, and automate workflows. Use when the user wants to interact with Built Accounting data.
⭐ 0· 55·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.md describes connecting to Built Accounting via the Membrane platform and only requires the Membrane CLI and a Membrane account. The commands and workflows in the instructions (login, connect, action list/run, proxy) match the stated purpose of integrating with Built Accounting.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, creating/listing connections, running actions, and proxying requests to the Built Accounting API. The file does not instruct reading unrelated files or environment variables, or exfiltrating data to unknown endpoints. Note: proxying means requests and their payloads will transit Membrane's servers (expected for this design).
Install Mechanism
This is instruction-only but asks users to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal step for a CLI, but global installs may require elevated permissions and you should verify the package name and publisher before installing.
Credentials
No environment variables, credentials, or config paths are requested. Auth is delegated to Membrane (the skill explicitly instructs creating an authenticated connection), which is proportionate to the stated purpose. Be aware that credentials are stored/managed by Membrane server-side per the instructions.
Persistence & Privilege
The skill does not request always:true or other elevated persistence. It is user-invocable and allows autonomous invocation by default (the platform default), which is expected for a functional integration skill.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to connect to Built Accounting and run actions. Before installing: (1) verify the @membranehq/cli package and publisher on npm (and the getmembrane.com / GitHub links) to avoid installing a malicious package, (2) understand that requests and data will transit Membrane's servers (review Membrane's privacy/security docs if your data is sensitive), and (3) be cautious with global npm installs (they may require elevated privileges). Otherwise the skill's requirements are proportional and coherent with its purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk97cy8h2w65xgbfz4z4h60kygh8420tp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.