Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Freebies — Port Clash Doctor

    1

    Identify and resolve Docker Compose port collisions and network binding conflicts instantly.

    Free

    2 usesSecurity scanned
    Freebies — Port Clash Doctor

    Freebies — Port Clash Doctor

    Example session with this skill installed

    Check my docker-compose.yml for port conflicts. I have a web app on 8080, a db on 5432, and I just added a dashboard also trying to use 8080.

    • Read your context and instructions
    • Compiled the freebies

    I have analyzed your `docker-compose.yml` file and identified a port collision on the host machine. ## Port Conflict Audit | Service Name | Host Port | Container Port | Status | Recommendation | | :--- | :--- | :--- | :--- | :--- | | `web-app` | `8080` | `3000` | **CONFLICT** | Keep as is or move to `8081` | | `dashboard` | `8080` | `80` | **CONFLICT** | Change host port to `8082` | | `database` | `5432` | `5432` | OK | No action required | ### Resolution Steps The services `web-app` and `dashboard` are both attempting to bind to port `8080` on your host machine. This will cause the second service to fail on startup. Update your `docker-compose.yml` as follows: ```yaml services: web-app: image: node:18 ports: - "8081:3000" # Changed from 8080 networks: - app-tier dashboard: image: nginx:latest ports: - "8082:80" # Changed from 8080 networks: - app-tier ``` **The Upsell:** Building a massive homelab? Grab my premium 'OpenClaw & n8n Local Orchestrator' skill for production-ready, clash-free architecture blueprints. **Next steps** 1. Apply the port changes to your `docker-compose.yml`. 2. Run `docker-compose up -d` to restart the services. 3. Verify the dashboard is accessible at `http://localhost:8082`.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    ## The problem Running multiple containerized services often leads to port collisions, where two services attempt to bind to the same host port. Identifying these overlaps in large `docker-compose.yml` files or hidden `.env` variables is manual and error-prone. ## What it does - Scans `ports:` directives across all services in your configuration files. - Identifies duplicate host port mappings that prevent containers from starting. - Detects network bridge issues and binding conflicts. - Provides safe, alternative port mapping suggestions to resolve clashes. ## Frameworks & tools Docker, Docker Compose, and environment configuration files (.env). ## Why this beats prompting it yourself General LLMs often miss port conflicts buried in multi-service files or external environment variables. This skill uses a specialized scanning logic focused specifically on networking bridge integrity, ensuring no collision goes unnoticed before you run `docker-compose up`. ## Use cases - Debug "address already in use" errors during local development. - Audit complex homelab setups with dozens of containers. - Validate new service additions against existing port bindings. - Refactor static port mappings to avoid host-level conflicts.

    Requires visibility into both docker-compose.yml and any referenced .env files to detect variable-based collisions. Does not check ports already used by non-Docker host processes.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    2 uses

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    • Free with an Agensi account

    Permissions

    Read Files

    Reads Docker Compose and environment configuration files to detect colliding host port bindings.

    Listed1 month ago
    Updated4 days ago

    What's inside

    Frequently Asked Questions

    This skill analyzes your Docker Compose files and .env variables to pinpoint identical host port assignments, preventing the common 'address already in use' errors before you attempt to deploy.

    Yes, the skill is designed to parse both hardcoded port strings and those defined via variables in .env files, ensuring it catches hidden conflicts that manual inspection might miss.

    The skill works with any standard Docker Compose (YAML) configuration and is compatible with most AI agents that support file analysis and code debugging workflows.

    Beyond just identifying the clash, the skill suggests available alternative port mappings based on common conventions, helping you reconfigure your services quickly and safely.

    You receive the specialized port-scanning logic and integration instructions for your AI agent; as a 'freebie' listing, you get full access to the current version at no cost.

    No, this skill operates as a static analyzer for your configuration files, meaning it can identify potential conflicts in your code without needing access to your live system or Docker daemon.

    New in DevOps & Cloud