Wicked Reports
v1.0.2Wicked Reports integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wicked Reports data.
⭐ 0· 48·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
Name/description (Wicked Reports integration) align with the instructions: the SKILL.md exclusively describes using the Membrane CLI to connect to Wicked Reports and run proxied API actions. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
The runtime instructions are narrowly scoped to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Wicked Reports. The docs do not instruct reading arbitrary local files, environment variables, or sending data to third-party endpoints outside Membrane/Wicked Reports. It explicitly advises not to ask users for API keys.
Install Mechanism
There is no automated install spec in the skill bundle (instruction-only). The SKILL.md tells users to run `npm install -g @membranehq/cli`. This is a standard, traceable npm package install but note that a global npm install executes package install scripts and writes binaries to the system PATH — users should verify the npm package and trust the provider before running.
Credentials
The skill declares no required env vars, no primary credential, and the instructions rely on browser-based Membrane authentication (no local secrets requested). That matches the described workflow where Membrane stores & refreshes credentials server-side.
Persistence & Privilege
always is false and there are no code files or automated installers shipped with the skill, so it does not persist code automatically. disable-model-invocation is false (platform default), meaning the agent may invoke the skill autonomously—this is normal but note the agent could call the Membrane CLI if given runtime access.
Assessment
This skill appears coherent: it delegates auth and API calls to Membrane and does not ask for unrelated credentials. Before installing/using it: 1) Verify and trust the @membranehq/cli npm package and the Membrane service (check npm page, GitHub repo, and getmembrane.com) because the CLI runs locally and install scripts execute during global npm installs. 2) Be aware you'll authenticate in a browser to grant Membrane access to your Wicked Reports account — review what permissions you grant. 3) Because the agent can invoke the skill autonomously (platform default), only enable it for agents you trust. If you prefer, run the CLI manually rather than giving an agent autonomous runtime access.Like a lobster shell, security has layers — review code before you run it.
latestvk9721vdnksf80fy3ytsw9t8bhh8439kn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.