nginx

    1

    Deploy production-ready Nginx configurations for reverse proxies, TLS termination, and load balancing.

    Free

    1 installSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    nginx

    Example session with this skill installed

    I need a secure Nginx config for a Node.js app running on port 3000. It needs HTTPS, WebSockets on /ws, and should serve static files from /var/www/dist with a 1-year cache.

    • Read your context and instructions
    • Compiled the nginx

    I have generated a hardened Nginx configuration for your Node.js application, including TLS settings, WebSocket proxying, and optimized static asset handling.

    Hardened Nginx Configuration

    
    # /etc/nginx/sites-available/node-app.conf
    
    upstream node_backend {
        server 127.0.0.1:3000;
        keepalive 64;
    }
    
    server {
        listen 80;
        listen [::]:80;
        server_name example.com;
        return 301 https://$host$request_uri;
    }
    
    server {
        listen 443 ssl;
        listen [::]:443 ssl;
        http2 on;
        server_name example.com;
    
        ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
    
        # Security Headers
        add_header Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" always;
        add_header X-Frame-Options "SAMEORIGIN" always;
        add_header X-Content-Type-Options "nosniff" always;
    
        # Static Assets
        location /static/ {
            alias /var/www/dist/;
            expires 1y;
            add_header Cache-Control "public, immutable";
            access_log off;
        }
    
        # WebSocket Support
        location /ws/ {
            proxy_pass http://node_backend;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            proxy_read_timeout 3600s;
        }
    
        # Default Proxy
        location / {
            proxy_pass http://node_backend;
            include /etc/nginx/proxy_params;
        }
    }
    

    Next steps

    1. Run nginx -t to verify the configuration syntax.
    2. Link the file: ln -s /etc/nginx/sites-available/node-app.conf /etc/nginx/sites-enabled/.
    3. Reload the service with systemctl reload nginx.

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

    About this skill

    The problem

    Manually configuring Nginx is error-prone, leading to 502 Bad Gateway errors, insecure TLS settings, and degraded performance due to unoptimized buffers or logging. Developers often struggle with the "if is evil" directive and complex location matching priority.

    What it does

    • Generates production-ready virtual host configurations for Node.js, Python, Go, and Ruby applications.
    • Configures secure HTTPS/TLS termination with modern ciphers, HSTS, and Let's Encrypt integration.
    • Implements upstream load balancing with keepalive connections and health-conscious tuning.
    • Sets up granular rate limiting zones and security headers like CSP and X-Frame-Options.
    • Optimizes static file delivery using gzip compression, caching headers, and zero-copy sendfile settings.

    Why this beats prompting it yourself

    Generic LLM prompts often overlook critical production details like worker_rlimit_nofile constraints or binary_remote_addr memory efficiency. This skill applies hardened security defaults and prevents common anti-patterns that cause silent failures under high load.

    Use cases

    • Deploying a reverse proxy for a microservices architecture with persistent upstreams.
    • Migrating an application from HTTP to hardened HTTPS with automated redirects.
    • Setting up a high-performance SPA server with optimized caching and fallback routing.
    • Debugging and resolving persistent 504 Gateway Timeout or 413 Request Entity Too Large errors.

    Known limitations

    Does not handle application-level logic or Kubernetes Ingress controllers. Requires existing SSL certificates for TLS features.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    1 install

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 12 days ago

    • Free to download with an account

    Listed12 days ago

    What's inside

    Frequently Asked Questions