Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentsSaaS White-Label Platform Builder
Fixing broken Docker setups manually often leads to hours of trial-and-error, messy workarounds, and accidental data loss.
$39.99
SaaS White-Label Platform Builder
Example session with this skill installed
My node app fails to start in Docker Compose. It says 'Error: Cannot find module /app/dist/index.js' even though I run npm run build in my Dockerfile. I'm using a multi-stage build.
- Read your context and instructions
- Compiled the saas white-label platform
The failure occurs during the
runtime/startup stage. The application expects a build artifact that is likely missing from the final production image due to an incorrect path in the COPY --from instruction.
Root-Cause Analysis
| Rank | Likely cause | Evidence | Confidence | Confirmation |
|---|---|---|---|---|
| 1 | Missing build artifacts | Error: Cannot find module /app/dist/index.js | High | Check contents of production image |
| 2 | Workdir mismatch | Standard multi-stage path divergence | Medium | Verify WORKDIR in both stages |
| 3 | .dockerignore exclusion | Build logs show 0 bytes copied for src | Low | Check .dockerignore for dist/ |
Recommended Fix
- File:
Dockerfile
Exact change: Ensure the production stage COPY command targets the absolute path where the build stage generated the files.
Reason: Multi-stage builds start with a fresh filesystem; if WORKDIR differs between stages, relative copies fail.
- Risks: Minimal. Ensure the build stage actually completes successfully.
Corrected Configuration
# Build Stage
FROM node:20-slim AS builder
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm install
COPY . .
RUN npm run build
# Production Stage
FROM node:20-slim
WORKDIR /app
# Use absolute path from builder or match WORKDIR
COPY --from=builder /usr/src/app/dist ./dist
COPY --from=builder /usr/src/app/node_modules ./node_modules
COPY package*.json ./
CMD ["node", "dist/index.js"]
Validation Commands
| Command | What it checks | Expected result |
|---|---|---|
docker compose build --no-cache | Fresh build integrity | Build completes |
docker run --rm <image_id> ls -R /app/dist | File existence | index.js is listed |
docker compose up | Container lifecycle | Service status 'Up' |
Next steps
- Update the
COPY --frompaths to match yourbuilderstageWORKDIR. - Run
docker compose configto verify the YAML structure before rebuilding. - Add a healthcheck to your Compose file to monitor service readiness.
Connects securely to your tools. The creator never sees your data.
About this skill
Fixing broken Docker setups manually often leads to hours of trial-and-error, messy workarounds, and accidental data loss. This skill provides a systematic approach to diagnosing and repairing containerization issues without suggesting dangerous "quick fixes" like privileged mode or mass volume deletion.
What it does
- Diagnoses failures by classifying issues across build stages, networking, volume permissions, and resource constraints.
- Analyzes root causes using an evidence-based approach to rank likely failure points from high to low confidence.
- Generates minimal repairs focusing on targeted configuration changes rather than complete rewrites to preserve existing architecture.
- Validates configurations by providing specific CLI commands tailored to the failure type for safe testing and verification.
- Hardens environments by suggesting multi-stage builds, non-root execution, and improved healthcheck logic.
How it works
- Provide the failing
Dockerfile,docker-compose.yml, or specific error logs from your build or runtime environment. - The agent classifies the failure stage (e.g., build-context, networking, or entrypoint permissions) and establishes facts vs. hypotheses.
- Review the prioritized table of root causes and the recommended minimal repair code.
- Execute the provided validation commands to confirm the fix works without compromising security or data.
Frameworks & tools
This skill supports Docker Engine, Docker Desktop, Docker Compose, and various container orchestration concepts. It handles standard Linux-based images, multi-platform builds (ARM/x86), and common package managers used within Dockerfiles.
Why this beats prompting it yourself
Generic AI prompts often suggest destructive commands like docker system prune -a or insecure chmod 777 fixes. This skill follows a strict safety protocol that preserves persistent data, keeps secrets out of image layers, and prioritizes evidence over guesswork.
Use cases
- Debugging "Exec format error" during multi-platform builds.
- Resolving DNS and networking failures between services in a Compose stack.
- Fixing permission denied errors on bind mounts and named volumes.
- Troubleshooting containers that exit immediately after startup without clear logs.
Known limitations
Does not perform live execution of commands. Requires manual input of logs and configuration files. Cannot retrieve secrets or private keys.
Cannot execute commands directly; relies on provided logs and files. Does not handle secret recovery or private key management.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 7 days ago