N8N Docker Monitor
PassAudited by ClawScan on May 14, 2026.
Overview
This appears to be a simple, purpose-aligned n8n Docker monitoring helper, with minor cautions around Docker/log access and inconsistent packaging metadata.
Before installing, make sure you are comfortable with the agent running read-only Docker inspection commands against your n8n container and viewing recent n8n logs. Also verify the package identity because the registry metadata and internal metadata do not fully match.
Findings (2)
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.
The agent may inspect local n8n container status, health, resource usage, and recent logs; those logs could reveal operational details or secrets if the container logs them.
The skill documents Docker CLI commands for monitoring an n8n container. They are purpose-aligned and read-only, but Docker/log inspection is still a powerful local operational capability.
- docker ps | grep n8n
- docker logs --tail 50 n8n
- docker inspect --format='{{.State.Health.Status}}' n8n
- docker stats --no-stream n8nUse this only on hosts where you intend to let the agent inspect the n8n Docker container, and review any log output before sharing it further.
The package may be mislabeled or republished from a different internal identity, which can make it harder to verify updates or provenance.
The internal metadata does not match the supplied registry metadata, which lists a different owner ID, slug `n8n-docker-monitor`, and version `1.0.0`. This is a provenance/packaging inconsistency, though no hidden install script or malicious code is shown.
"ownerId": "kn7369bn37xq0wajevgzvkzk0d802tb4", "slug": "n8n-monitor", "version": "1.0.1"
Confirm the publisher, slug, and version before relying on this skill, especially if installing updates later.