React Native Logs

Use rn-logs to read React Native Metro logs via CDP without MCP overhead. Default output is plain text and safe for non-interactive agent runs.

This skill is coherent with its description: it tells you to install and run rn-logs-cli to stream Metro logs. Before installing or running: 1) verify the rn-logs-cli package (author, npm page, repository) because global npm/bun installs execute third‑party code and can require elevated privileges; 2) prefer using npx or a local (non-global) install or a disposable container if you don't trust the package; 3) be aware the tool connects to Metro (default localhost:8081) and to any simulator/device you have running; and 4) ensure you only run it in an environment where accessing device logs is permitted. If you want a tighter review, provide the npm package URL or repository so I can check the package source and maintainer details.

Type: OpenClaw Skill Name: react-native-logs-cli Version: 1.0.1 The skill bundle instructs the agent to install and execute an external CLI tool (`rn-logs-cli`) using `npm install -g` and `bun add -g` commands, and then to run `rn-logs` commands with user-provided arguments (e.g., `--app "<id|name>"`, `--host "<host>"`). While the stated purpose is benign (reading React Native logs), the reliance on installing and executing external binaries, especially with user-controlled input passed to shell commands, introduces a supply chain risk and a potential shell injection vulnerability if the agent or the `rn-logs` tool itself does not adequately sanitize inputs. This is classified as suspicious due to these inherent risks and potential attack surface, rather than clear malicious intent within the skill's instructions.