Tyk
v1.0.2Tyk integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tyk data.
⭐ 0· 91·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 (Tyk integration) match the SKILL.md: it uses Membrane to connect to Tyk, list actions, run actions, and proxy requests. The declared lack of required env vars/credentials aligns with the guidance to authenticate via Membrane rather than local secrets.
Instruction Scope
Instructions stay within scope: they direct installing and using the Membrane CLI, logging in, creating connections, listing/running actions, and proxying requests to Tyk. The instructions do not ask the agent to read unrelated files, environment variables, or system paths.
Install Mechanism
Install is via npm (npm install -g @membranehq/cli), which is a standard public-registry mechanism; this is expected for a CLI but is a moderate-risk operation compared with instruction-only skills because it installs code on the host. No obscure download URLs are used.
Credentials
The skill does not request local secrets or unrelated credentials. It explicitly relies on Membrane to manage auth server-side and uses browser-based login flow, which is proportionate for this integration.
Persistence & Privilege
The skill does not request always-on presence and has no install-time behavior beyond instructing the user to install a CLI. Autonomous invocation is allowed by platform default but is not combined with elevated privileges or broad credential access.
Assessment
This skill is coherent for interacting with Tyk through Membrane. Before installing: (1) confirm you trust the @membranehq npm package and its publisher (npm global installs run code on your machine); (2) understand that using the skill requires a Membrane account and a browser-based login flow that grants Membrane access to connectors for your Tyk instance; (3) review Membrane's privacy/security docs and the connector configuration so you know what access will be granted to Membrane; and (4) prefer running the CLI in a controlled environment (not on sensitive production hosts) until you've validated behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk978tp9dvr0andzja1jefdp4ds842g1a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.