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.

Security Scan

The skill's instructions and requirements match its stated purpose (reading React Native Metro logs); there are no unexplained credential or file accesses, but the SKILL.md tells the user to install a third‑party npm package which you should verify before installing.

Purpose & Capability

Name/description (read Metro logs via CDP) align with the runtime instructions (install and run rn-logs-cli and use rn-logs apps/logs). Nothing requested or instructed is outside the stated purpose.

Instruction Scope

Instructions stay within the tool's scope (list/stream/snapshot logs from Metro). They ask the agent/operator to install and run the rn-logs binary and to connect to Metro (host/port). They do not ask to read unrelated files, environment variables, or external endpoints beyond the Metro host. Note: the SKILL.md instructs global npm/bun installs, which are operational actions with side effects (package code execution) that the user should be aware of.

Install Mechanism

The skill is instruction-only (no install spec in the manifest). SKILL.md recommends 'npm install -g rn-logs-cli' or 'bun add -g rn-logs-cli' which pulls code from the public npm/bun registries; this is a normal but moderate-risk action because it runs third-party code on install and may require elevated permissions for global installs.

Credentials

No environment variables, credentials, or config paths are requested in the manifest or the instructions. The commands use host/port flags (defaults to localhost:8081) which are appropriate for connecting to Metro.

Persistence & Privilege

always is false and the skill does not request persistent system modifications or access to other skills' configurations. It simply instructs installing and running a CLI tool when needed.

Assessment

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.

rn-logs cli

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.

When to use

• You need live Metro logs from a running RN app
• You want low-context, plain text log output

Installation

npm install -g rn-logs-cli

bun add -g rn-logs-cli

Then verify:

rn-logs --help

Requirements

• rn-logs is installed and available in PATH
• Metro is running
• App is running on a simulator or device

Core workflow

# 1. List connected apps
rn-logs apps

# 2. Stream logs
rn-logs logs --app "<id|name>"

# 3. Snapshot logs
rn-logs logs --app "<id|name>" --limit 50

Command options

# Changing default port or host
rn-logs "[command]" --host "<host>"    # Metro host (default: localhost)
rn-logs "[command]" --port "<port>"    # Metro port (default: 8081)

rn-logs help

Non-interactive mode

• When multiple apps are connected, you must pass --app.
• Output is plain text for agent-friendly consumption.

Common failures

• metro not reachable -> start Metro or fix host/port
• no apps connected -> run app on simulator or device
• multiple apps connected -> pass --app