Ataccama
v1.0.2Ataccama integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ataccama data.
⭐ 0· 65·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
Name/description: Ataccama integration. Declared and actual behavior: uses the Membrane CLI to discover connectors, create connections, run actions, and proxy API calls to Ataccama. No unrelated environment variables, binaries, or config paths are requested. The dependency on a Membrane account is sensible for a proxy-based integration.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, creating/inspecting connections, running actions, and using Membrane's proxy. It does not instruct reading arbitrary files, scanning system configs, or exfiltrating environment variables. The proxy feature does allow arbitrary requests to Ataccama through the connection (expected for this integration).
Install Mechanism
There is no install spec in the registry (instruction-only), but SKILL.md asks to run 'npm install -g @membranehq/cli'. Global npm installs are a common but higher-friction install step (requires write privileges). This is expected but worth noting as it executes arbitrary code from the npm package; consider using npx or verifying the package source before installing.
Credentials
The skill declares no required env vars or secrets and explicitly advises against asking users for API keys, recommending Membrane-managed connections. That aligns with the described flow where Membrane handles auth. The only external requirement is a Membrane account (and network access).
Persistence & Privilege
Skill is not always-enabled and does not request persistent platform privileges. It is user-invocable and allows autonomous invocation (platform default). There is no instruction to modify other skills or global agent configs.
Assessment
This skill appears internally consistent, but review a few practical points before installing: 1) The SKILL uses the Membrane CLI (npm package). Verify the @membranehq/cli package on npm and the GitHub repo before running a global install; consider using 'npx @membranehq/cli' to avoid global installation. 2) Membrane acts as a proxy and will handle auth and make requests to Ataccama on your behalf — only install/use this if you trust Membrane and are comfortable granting it access to your Ataccama connections. 3) Authentication opens a browser flow; use a test/non-production account when first trying the integration. 4) Monitor and review any connections created in Membrane and limit permissions where possible (least privilege). 5) If you need higher assurance, confirm the skill publisher identity (registry owner and GitHub repo) and review the Membrane CLI source code or release artifacts before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97c3j9vbm424rzjv66xkbrk118428vb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.