Expose Docker containers at trusted HTTPS .test hosts and diagnose routing, browser, and container failures.
npx skills add https://github.com/filippolmt/skills --skill proximo-filippolmt
Please help me install this Agent Skill. Skill: proximo Source: https://github.com/filippolmt/skills/tree/main/skills/proximo Command: npx skills add https://github.com/filippolmt/skills --skill proximo-filippolmt
proximo.hosts=<name>.test labels to a Compose service and get local DNS, a trusted certificate, and Host-based routing, with optional labels for ports, path prefixes, TCP/SNI, auth, CORS, and health gating. - Structured triage: proximo status and proximo doctor classify the failure — missing route, routing failure, browser-side breakage, or server-side error — and each failed check names its exact remedy. - Browser and backend observability: Exchanges combine access records, container transcripts, and browser client reports (with DOM snapshots), while Incidents capture runtime events like exits, OOM kills, and healthcheck failures for workers that serve no requests. - Use Case: A developer's queue consumer stops draining with no visible error. The skill guides checking proximo errors --service <service> for Incidents and readings, quoting the container's transcript for the window, and proposing a healthcheck so future stalls become visible. ## Quick Start Ask the assistant to check why https://api.test returns a 502 and have it run proximo status and proximo doctor to diagnose the route.High-intent search queries and answers about installing and using this skill.
Add the label proximo.hosts=<name>.test to the container's Compose service and run docker compose up -d. proximo assigns local DNS, a trusted certificate, and a Host-based route; confirm with proximo status and curl the qualified host.
A 502/503 means the route matched but the backend did not answer. Common causes are healthcheck gating right after a restart, an outdated stack missing the inspection hop, or the container listening on a different port than proximo.port expects.
Run proximo trust to re-add the local CA to the system store and Firefox's NSS store. It requires a password, so the machine's owner should run it; this also fixes Chrome profiles whose trust store was rebuilt.
Yes, set proximo.inspect=true on the container so its HTML responses are served through the inspection hop. Then run proximo errors --json --host <host> to read client reports, breadcrumbs, and DOM snapshots; Chrome is the supported browser.
A live but blocked worker declares no Incident, so an empty listing means proximo saw nothing happen, not that nothing is wrong. Check the readings under proximo errors --service, quote the transcript window, and add a healthcheck that fails when the worker stops advancing.
Transcripts quote only stdout and stderr within a time window and are temporal, not causal, so interleaved output from overlapping requests cannot be separated. proximo redacts nothing, so transcripts may contain credentials or personal data.
beratcelik1Apply Docker and Docker Compose patterns for multi-service development and security.
sddevelopment-beReproduce software bugs with failing tests, then fix and re-verify.
lofibrainwavMonitor Docker container health and restart failed containers automatically.
BagelHoleConfigure Nginx and Traefik reverse proxies for routing and SSL termination.