Triggre

v1.0.2

Triggre integration. Manage data, records, and automate workflows. Use when the user wants to interact with Triggre data.

0· 106·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Triggre integration) match the instructions: all runtime steps use the Membrane CLI and Membrane's proxy to interact with Triggre. Nothing requested (no env vars, no unrelated binaries) is outside that purpose.
Instruction Scope
SKILL.md instructs only to install and use the Membrane CLI (login, connect, action list/run, proxy requests). It does not ask the agent to read arbitrary files, export unrelated credentials, or transmit data to unexpected endpoints. Browser-based auth and CLI commands are expected for this integration.
Install Mechanism
Installation is an npm global package (npm install -g @membranehq/cli / npx usage). This is proportionate to the skill's stated need for a CLI, but npm packages are externally fetched code (moderate risk). Recommend reviewing the package repo and publisher before installing and, if possible, pin a known-good version rather than running npx @membranehq/cli@latest.
Credentials
The skill declares no required env vars, no config paths, and advises using Membrane-managed connections (so it does not request user API keys). This is proportionate to a proxy-based integration.
Persistence & Privilege
Skill is instruction-only, has no install spec writing files, and does not set always: true. It does not request persistent agent privileges or modify other skill configs.
Assessment
This skill is coherent and appears to do what it claims, but it depends on the third-party Membrane CLI/service. Before installing: (1) verify the @membranehq/cli package and the GitHub repo match the publisher you trust; (2) prefer installing a reviewed, pinned CLI version rather than running npx @membranehq/cli@latest; (3) be aware that Membrane will broker authentication to Triggre — you are trusting that service with access to your Triggre account; and (4) install CLI tools in a controlled environment (or container) if you want to limit risk from a globally installed npm package.

Like a lobster shell, security has layers — review code before you run it.

latestvk970h107nh75a0c2tgwf11x4p1843d9k

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments