N8n Monitor
PassAudited by ClawScan on May 1, 2026.
Overview
The skill appears purpose-aligned for monitoring n8n with Docker, but users should notice that it can read container logs and that Docker is not declared as a requirement.
This looks benign for its stated monitoring purpose. Before installing, make sure you intend to let the agent run Docker status/log commands on the n8n host, and avoid sharing returned logs if they contain workflow payloads, tokens, URLs, or other operational secrets.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If invoked on a Docker host, the agent can show n8n status, resource use, health, and the last 50 log lines, which may reveal operational details or workflow data.
The skill explicitly relies on raw Docker CLI commands to inspect container state and logs. This is central to the monitoring purpose, but it gives the agent access to local container information and recent log output.
- docker ps | grep n8n
- docker logs --tail 50 n8n
- docker inspect --format='{{.State.Health.Status}}' n8n
- docker stats --no-stream n8nUse it only on the intended n8n host/container, review log output before sharing it, and prefer least-privilege or read-only monitoring access where possible.
A user or agent with Docker access can inspect the n8n container's status and recent logs on that host.
Monitoring through Docker requires access to the local Docker environment and includes reading container logs. This is purpose-aligned, but Docker access is a privileged operational context.
Monitoramento operacional do N8N via Docker. ## Capabilities - Verificar status dos containers N8N - Ler logs recentes
Grant Docker access only to trusted users or agents and avoid running the skill against hosts or containers outside the intended n8n instance.
The skill may fail where Docker or grep are unavailable, and users may not get an install-time reminder that local Docker access is needed.
The metadata declares no binary requirements even though SKILL.md documents Docker and grep commands. This is an under-declared dependency rather than hidden installation behavior.
Required binaries (all must exist): none Required binaries (at least one): none Install specifications No install spec — this is an instruction-only skill.
Declare Docker, and grep or shell usage if required, in the skill metadata and document the expected container name and supported environments.