Zendesk Guide
v1.0.0Zendesk Guide integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zendesk Guide data.
⭐ 0· 50·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
medium confidencePurpose & Capability
The name/description (Zendesk Guide integration) matches the runtime instructions: all actions documented use the Membrane CLI to access Zendesk Guide APIs or prebuilt actions. There are no unrelated env vars, binaries, or config paths requested that would be incoherent with a Zendesk integration.
Instruction Scope
SKILL.md is instruction-only and stays on-topic: it tells the agent/user to install the Membrane CLI, run browser-based login, create a connection, list actions, run actions, or proxy raw API calls via Membrane. It does not instruct reading arbitrary local files or exfiltrating unrelated data. Important: proxying requests via Membrane means request/response bodies and any Zendesk data you send will traverse Membrane's servers — the document explicitly relies on that behavior.
Install Mechanism
No registry install spec is included (instruction-only), but the README tells users to run `npm install -g @membranehq/cli`. This is a standard approach but carries the usual risks of installing a global npm package (network fetch, code execution on install). Verify the npm package provenance and that you trust @membranehq before installing globally.
Credentials
The skill requests no environment variables or extra credentials in the manifest. Authentication is delegated to Membrane's browser OAuth flow and connection management. That is proportionate for a proxy-based integration, but it means credentials and proxied data are managed by Membrane — ensure that is acceptable for your data/privacy requirements.
Persistence & Privilege
always is false, no install spec writes files via the skill itself, and no instruction requests modifications to other skills or system-wide agent settings. Installing the CLI may create local configuration (tokens or config files) in the user's environment, which is expected for a CLI tool.
Assessment
This skill is coherent for interacting with Zendesk Guide via Membrane, but consider the following before installing:
- Trust & data flow: Using the skill proxies your Zendesk API calls through Membrane. That means request/response bodies and any sensitive content will traverse Membrane's infrastructure — review their privacy, data retention, and security controls and confirm this is acceptable.
- Install provenance: The SKILL.md instructs installing @membranehq/cli globally via npm. Verify the package name, publisher, and npm page (and prefer scoped installs or non-global installs if your org restricts global packages).
- Least privilege: Create or test with a non-production Zendesk account or scoped connector where possible to limit exposure while you validate behavior.
- Org policy: If you’re in a corporate environment, check with IT/security before installing a global CLI or routing support data through a third-party.
If you want a deeper assessment, ask for: the npm package metadata (publisher, latest version checksum), Membrane's security/privacy documentation, or any network egress rules that would apply in your environment.Like a lobster shell, security has layers — review code before you run it.
latestvk97awhx334jqz2e9kfah6c98yd84hxj9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.