Configure Reverse Proxy
Configure reverse proxy patterns across multiple tools including Nginx, Traefik, and ShinyProxy. Covers WebSocket proxying, path-based and host-based routing, SSL termination, and Docker label auto-discovery. Use when routing multiple services behind a single entry point, proxying WebSocket connections (Shiny, Socket.IO), auto-discovering Docker services with Traefik labels, or adding SSL termination to services that don't handle TLS natively.
Install
npx skills add pjt222/agent-almanac --skill configure-reverse-proxygit clone --depth 1 https://github.com/pjt222/agent-almanac.git /tmp/agent-almanac
mkdir -p ~/.claude/skills
cp -r /tmp/agent-almanac/i18n/caveman-lite/skills/configure-reverse-proxy ~/.claude/skills/configure-reverse-proxyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Configure Reverse Proxy Set up reverse proxy patterns for routing traffic to backend services using Nginx, Traefik, or ShinyProxy. ## When to Use - Routing multiple services behind a single entry point - Proxying WebSocket connections (Shiny, Socket.IO, live reload) - Auto-discovering Docker services with Traefik labels - Path-based or host-based routing to different backends - Adding SSL termination to services that don't handle TLS ## Inputs - **Required**: Backend services to proxy (host:port) - **Required**: Routing strategy (path-based, host-based, or both) - **Optional**: Proxy tool preference (Nginx, Traefik) - **Optional**: Domain name(s) for host-based routing - **Optional**: WebSocket endpoints to proxy ## Procedure ### Step 1: Choose Proxy Tool | Feature | Nginx | Traefik | |---|---|---| | Configuration | Static files | Docker labels / dynamic | | Auto-discovery | No (manual) | Yes (Docker provider) | | Let's Encrypt | Via certbot | Built-in ACME | | Dashboard | No (3rd party) | Built-in | | WebSocket | Manual config | Automatic | | Best for | Static config, high traffic | Dynamic Docker environments | ### Step 2: Nginx — Path-Based Routing
Details
- Skill name
configure-reverse-proxy- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/configure-reverse-proxy/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Configure Reverse Proxy skill do?
Configure reverse proxy patterns across multiple tools including Nginx, Traefik, and ShinyProxy. Covers WebSocket proxying, path-based and host-based routing, SSL termination, and Docker label auto-discovery. Use when routing multiple services behind a single entry point, proxying WebSocket connections (Shiny, Socket.IO), auto-discovering Docker services with Traefik labels, or adding SSL termination to services that don't handle TLS natively.
How do I install the Configure Reverse Proxy skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill configure-reverse-proxy. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Configure Reverse Proxy popular?
It lives in pjt222/agent-almanac, which has 45 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Adapt Architecture
45pjt222/agent-almanac
Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.
Adaptic
45pjt222/agent-almanac
Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.
Add Puzzle Type
45pjt222/agent-almanac
Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.
Correlate Observability Signals
45pjt222/agent-almanac
Unify metrics, logs, and traces for cohesive debugging. Implement exemplars for log-to-trace linking, build unified dashboards using RED/USE methods, and enable rapid root cause analysis across observability signals. Use when investigating complex incidents spanning multiple systems, reducing mean time to resolution, implementing distributed tracing, or moving from siloed tools to a unified observability platform.
Configure Nginx
45pjt222/agent-almanac
Configure Nginx as a web server and reverse proxy. Covers static file serving, reverse proxy to upstream services, SSL/TLS termination with Let's Encrypt, location blocks, load balancing, rate limiting, and security headers. Use when serving static files in production, reverse proxying to backend services (Node.js, Python, R/Shiny), terminating SSL/TLS, load balancing across instances, or adding rate limiting and security headers to harden an endpoint.
Create Dockerfile
45pjt222/agent-almanac
Create general-purpose Dockerfiles for Node.js, Python, Go, Rust, and Java projects. Covers base image selection, dependency installation, user permissions, COPY patterns, ENTRYPOINT vs CMD, and .dockerignore. Use when containerizing an application for the first time, creating a consistent build/runtime environment, preparing an app for cloud deployment or Docker Compose, or when no existing Dockerfile is present in the project.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.