Stats
Actions
Tags
From portainer-tools
Manage Docker networks across all Portainer-managed hosts. Use when asked to list networks, inspect a network, create a network, remove a network, check network configuration, or troubleshoot container connectivity.
How this skill is triggered — by the user, by Claude, or both
Slash command
/portainer-tools:portainer-networksThis 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
Manage Docker networks across hosts using the Portainer API.
Parse $ARGUMENTS to determine the action and parameters:
list [host-name|all]
inspect <network-name> [--host HOST]
create <network-name> --host HOST [--driver bridge] [--subnet CIDR] [--gateway IP]
--host is requiredremove <network-name> --host HOST
--host is required; refuses to delete default networks (bridge, host, none)Build and run the command:
python3 $SKILL_DIR/portainer_networks.py <action> [name] [--host HOST] [--driver DRIVER] [--subnet CIDR] [--gateway IP]
Present the output:
[default] tag for built-in networks.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-toolsConfigures Docker Compose networks for service communication and isolation, covering default bridge networks, custom bridges, overlay networks, aliases, and service discovery in multi-container apps.
Provides Docker networking patterns including bridge/host/overlay types, DNS resolution, port mapping, multi-service communication, and PHP-FPM/Nginx TCP/Unix socket setups for PHP stacks.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.