1C
v1.0.01C-Bitrix integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1C-Bitrix data.
⭐ 1· 100·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 (1C‑Bitrix integration) matches the runtime instructions which use the Membrane CLI to discover connectors, create connections, run actions, and proxy API requests to 1C‑Bitrix. Requiring a Membrane account and a CLI is appropriate for this stated purpose.
Instruction Scope
SKILL.md only instructs use of the Membrane CLI and browser-based auth flows; it does not ask the agent to read arbitrary host files or environment variables. One note of caution: the documented 'membrane request' proxy allows arbitrary API calls (to the 1C API via Membrane), which is expected for an integration but could be misused to send or fetch arbitrary data if the agent is given overly broad instructions.
Install Mechanism
This is an instruction-only skill with no install spec. It tells users to install the Membrane CLI via 'npm install -g' or to run commands via npx. That is reasonable for a CLI-based integration but carries the usual risks of installing global npm packages—verify the CLI package source and maintainers before installing.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. It relies on Membrane to manage auth, which is consistent with its guidance to avoid asking users for API keys.
Persistence & Privilege
The skill does not request always:true or other elevated persistence. Model invocation is allowed (default), which is normal for skills and matches its documented runtime behavior.
Assessment
This skill appears to do what it says: it delegates auth and API calls to the Membrane platform and tells you how to use the Membrane CLI. Before installing or using it: 1) verify the Membrane CLI package (publisher and repo) to ensure you're installing the official tool; 2) avoid providing unrelated credentials to the agent—use Membrane connections as intended; 3) be aware the 'membrane request' proxy can run arbitrary API calls against your 1C instance, so limit who/what can instruct the agent to run such requests; and 4) if you want to restrict autonomous calls, consider disabling model invocation for this skill or supervising any automated actions.Like a lobster shell, security has layers — review code before you run it.
latestvk97af69f5zm81yk4vxecc5fgq984h935
License
MIT-0
Free to use, modify, and redistribute. No attribution required.