Addevent
v1.0.2Addevent integration. Manage data, records, and automate workflows. Use when the user wants to interact with Addevent data.
⭐ 0· 101·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 name/description promise an Addevent integration and the SKILL.md exclusively documents using the Membrane CLI to connect to Addevent, list/run actions, and proxy requests—these requirements align with the stated purpose.
Instruction Scope
Runtime instructions only cover installing/using the Membrane CLI, performing OAuth-style connection flows, listing and running actions, and proxying API requests. The instructions do not ask the agent to read unrelated files, request unrelated credentials, or exfiltrate data to unexpected endpoints.
Install Mechanism
The skill is instruction-only (no install spec), but the SKILL.md tells users to run `npm install -g @membranehq/cli`. This is a reasonable client-side step for using Membrane, but installing global npm packages modifies the local system and should be done only if the user trusts the @membranehq/cli package and understands npm global installs.
Credentials
No environment variables, credentials, or config paths are required by the skill. The SKILL.md explicitly instructs users to create a connection via Membrane (OAuth/browser flow) and not to share API keys, which is consistent and proportionate.
Persistence & Privilege
The skill does not request always:true and is user-invocable; it does not ask to modify other skills or system-wide settings. Autonomous invocation remains enabled by default but is not accompanied by other concerning privileges.
Assessment
This skill appears to be a straightforward Membrane-based Addevent integration. Before installing/using it: (1) verify you trust the Membrane project and the @membranehq/cli npm package (review its source/repo and permissions) because the SKILL.md asks you to install it globally; (2) expect to authenticate via a browser OAuth flow—Membrane will hold the connection credentials and proxy API calls on your behalf; (3) do not provide Addevent API keys directly to the skill—use the Membrane connection flow as documented; and (4) ensure you are comfortable granting network access and a third-party service (Membrane) access to your Addevent account since that is necessary for this integration.Like a lobster shell, security has layers — review code before you run it.
latestvk979pg2qn2bmaxrtt8h7x6gtv5843fwz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.