Marvel

Things to consider before installing: - Metadata vs. instructions: the registry metadata omits required tooling, but SKILL.md asks you to install @membranehq/cli via npm or npx. Expect to install Node/npm and run third‑party npm code — verify the package and its source (GitHub/repo) before installing globally. - Membrane auth flow: the CLI opens a browser for authentication and stores credentials in Membrane; you will not be asked for Marvel API keys locally. If you run this in a headless environment you will need to perform code-based completion flows. - Proxied requests: the CLI's 'membrane request' can send arbitrary proxied HTTP requests to Marvel. That is necessary for advanced use but means the agent could send data to external APIs — avoid passing sensitive secrets or unrelated data through the skill. - Risk mitigation: review @membranehq/cli source (repo/release), run npm packages in an isolated environment or container if you're cautious, and validate connector IDs/actions before executing. If you require higher assurance, ask the author/maintainer for an explicit install manifest and for the skill to declare required binaries and network requirements in metadata. - When to avoid: do not install this into always-on or highly-privileged agents if you cannot verify the npm package and Membrane account policies, and avoid using it with secrets unrelated to Marvel.