Sage Intacct
v1.0.0Sage Intacct integration. Manage data, records, and automate workflows. Use when the user wants to interact with Sage Intacct data.
⭐ 0· 61·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 is an integration wrapper for Sage Intacct that consistently instructs the agent to use the Membrane CLI and a Membrane account. Required network access and a Membrane account are directly relevant to the described functionality; no unrelated services or credentials are requested.
Instruction Scope
SKILL.md contains concrete CLI commands (installing/using @membranehq/cli, membrane login, connect, action run, request) and stays within the scope of discovering and invoking Sage Intacct actions or proxying API requests. It does not instruct reading unrelated files, environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the guide instructs installing the Membrane CLI via npm (global install) and using npx. Requiring a third-party CLI published to npm is reasonable for this integration, but it does introduce a trust dependency on the @membranehq/cli package and its publisher.
Credentials
The skill declares no required env vars or credentials and explicitly advises against requesting local API keys, instead relying on Membrane-managed connections. That is proportionate to the purpose; no unrelated secrets are requested.
Persistence & Privilege
The skill is not forced-always and does not request system-wide config paths or elevated persistence. It relies on user-run CLI authentication flows (browser or headless code exchange) and does not instruct modifying other skills or global agent settings.
Assessment
This skill appears internally consistent: it delegates auth and API calls to the Membrane service and the Membrane CLI. Before installing, verify you trust the Membrane project and the @membranehq/cli package (review its GitHub repo and npm publisher), prefer using npx or a sandboxed environment instead of a global npm install if you want to reduce risk, and understand that Membrane will hold the connection credentials and proxy requests to Sage Intacct (review their privacy/terms). If you need extra assurance, inspect the Membrane CLI source or run it in an isolated machine/container before granting it access to production data.Like a lobster shell, security has layers — review code before you run it.
latestvk9772pxmadgvqqpkwsq5xxcmk1845vab
License
MIT-0
Free to use, modify, and redistribute. No attribution required.