Stats
Actions
Tags
From portainer-tools
View container logs from a Portainer-managed Docker host. Use when asked to "view logs", "show logs", "tail logs", "check logs", or "read console output" for a specific container.
How this skill is triggered — by the user, by Claude, or both
Slash command
/portainer-tools:portainer-logsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
```text
$ARGUMENTS
Fetch and display logs for a named container on a Docker host via the Portainer API.
Parse $ARGUMENTS:
on (e.g. on docker01)--tail <n> if present (default: 100)Run:
python3 $SKILL_DIR/portainer_logs.py <container> [--host <host>] [--tail <n>]
Example: python3 $SKILL_DIR/portainer_logs.py n8n --host docker02 --tail 200
Display the output in a code block.
If the script reports multiple matches, ask the user to specify the host.
If auth fails, tell the user:
Set
PORTAINER_TOKEN=ptr_...before invoking. Generate one in Portainer: User Settings > Access Tokens.
npx claudepluginhub sinositato/tato-claude-plugins --plugin portainer-toolsSets up and uses Gonzo TUI to tail, filter, and AI-analyze real-time logs from stdout pipes. Detects platforms like AWS, Vercel, Kubernetes; generates commands.
Debug container agent issues including failures, authentication problems, and sandbox runtime behavior. Covers logs, environment variables, mounts, and common fixes.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.