Wip Xai Grok Private

xAI Grok API. Search the web, search X, generate images, generate video.

This package implements the claimed Grok features, but there are a few red flags to consider before installing: - The registry metadata does NOT declare that the skill needs XAI_API_KEY or the 1Password (op) CLI, yet SKILL.md and core.mjs expect XAI_API_KEY and call 'op read'. Confirm you are comfortable granting the skill access to that API key and that the 'op' binary (if present) is safe to use. - core.mjs uses child_process.execSync('op read ...') and will run that CLI on your system if the env var is missing. If you do not want third-party code to invoke local CLIs, do not install/run this skill or inspect and remove the fallback before use. - The edit_image function reads local files (readFileSync) when given a file path and can base64-encode them for upload. Do not pass sensitive filesystem paths to this skill; audit the code if you plan to allow user-controlled file paths. - package.json and package-lock.json show many npm dependencies; install in a sandbox or verify dependency integrity (e.g., audit lockfile) before running in production. Recommendations: 1) Ask the publisher to update registry metadata to declare required env vars (XAI_API_KEY) and required binaries ('op' if relying on 1Password CLI). 2) If you plan to use it, run it in an isolated environment (container) and inspect or remove the execSync fallback if you don't want CLI access. 3) Verify the API key scope and rotate it if you test in a shared environment. 4) If you need higher assurance, request a signed release or a reproducible build and review the package-lock dependencies.

Type: OpenClaw Skill Name: wip-xai-grok Version: 1.0.3 The skill bundle is a legitimate integration for the xAI Grok API, providing tools for web search, X (Twitter) search, and media generation. It includes a CLI, an MCP server, and clear instructions for AI agents in SKILL.md. The code in core.mjs features an automated credential retrieval mechanism that attempts to read the xAI API key from 1Password using the 'op' CLI via execSync; while execSync is a high-risk primitive, its usage here is constrained to a hardcoded 1Password path and serves the stated purpose of secure secret management. All external communication is directed to the official xAI API (api.x.ai), and no evidence of data exfiltration or malicious prompt injection was found.