Assembled
v1.0.0Assembled integration. Manage data, records, and automate workflows. Use when the user wants to interact with Assembled data.
⭐ 0· 53·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description say this integrates with Assembled and all runtime instructions use the Membrane CLI to discover connectors, create connections, run actions, or proxy API calls to Assembled. There are no unexplained environment variables, binaries, or unrelated requirements.
Instruction Scope
SKILL.md only instructs the agent to install and run the Membrane CLI commands (login, connect, action list/run, request proxy). It does not direct reading of unrelated files, environment variables, or posting data to unexpected endpoints. The guidance to use Membrane as the auth proxy is explicit and bounded to the stated purpose.
Install Mechanism
The skill recommends installing @membranehq/cli via npm -g. This is a common approach for CLI tools but is a system-level install that runs third-party package code. The skill itself has no install spec and will not auto-install anything; the user must opt in to install the npm package.
Credentials
No environment variables, API keys, or config paths are requested by the skill. That is proportional because authentication is delegated to the Membrane CLI and the browser-based login flow; the SKILL.md explicitly warns not to ask users for API keys.
Persistence & Privilege
The skill does not request always:true, does not claim persistent system-level changes, and contains no instructions to modify other skills or global agent config. Autonomous invocation is allowed (platform default) and is appropriate for an integration skill.
Assessment
This skill is coherent: it expects you to install and use the Membrane CLI to connect to Assembled and does not ask for local API keys. Before installing, verify you trust the Membrane project and the npm package (@membranehq/cli) because installing global npm packages runs third-party code on your machine. Also confirm Membrane's privacy/security policies since it will proxy and potentially see your Assembled data and handle authentication on your behalf. If you need a higher assurance, check the referenced GitHub repository and the package's npm publisher/maintainer details and consider installing the CLI in a controlled environment rather than system-wide.Like a lobster shell, security has layers — review code before you run it.
latestvk9777tqmzjya6snns4vc31cxzd84c8k2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.