How do I install the Caddy skill?

Run npx skillmds@latest add dvcrn/caddy-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Caddy safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: WARNING. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Caddy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Caddy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Caddy by dvcrn — Agent Skill

Name: Caddy
Rating: 4.666666666666667 (3 reviews)
Author: dvcrn

File contents

Caddy — Wildcard Reverse Proxy for Local Apps

Routes *.YOUR_DOMAIN subdomains to local services over HTTPS via Caddy reverse proxy with automatic Let's Encrypt certificates. Designed for Tailscale-only access (no public exposure).

DNS provider: This skill uses Vercel DNS for DNS-01 ACME challenges. If you use a different DNS provider, swap the caddy-dns/vercel plugin and TLS snippet for your provider's equivalent (see caddy-dns).

Add a New App

Create a background service (LaunchAgent on macOS, systemd on Linux) — see reference.md for templates
Add to Caddyfile (~/.config/caddy/Caddyfile):
```
appname.YOUR_DOMAIN {
    import vercel_tls
    reverse_proxy localhost:31XX
}
```
Also add a <li> entry in the dashboard HTML block at the top.

Reload Caddy:

~/.local/bin/caddy reload --config ~/.config/caddy/Caddyfile --address localhost:2019

TLS cert provisioning takes 30–60 seconds (DNS-01 challenge).

If it connects to OpenClaw Gateway — see OPENCLAW.md in this folder for gateway-specific config.

Quick Dev Servers

Companion skill: dev-serve — one-command dev server + Caddy routing.

dev-serve up ~/projects/myapp        # → https://myapp.YOUR_DOMAIN
dev-serve down myapp
dev-serve ls

Reload / Restart

# Reload config (no restart, no sudo)
~/.local/bin/caddy reload --config ~/.config/caddy/Caddyfile --address localhost:2019

# Full restart
# macOS:
sudo launchctl unload /Library/LaunchDaemons/com.caddyserver.caddy.plist
sudo launchctl load /Library/LaunchDaemons/com.caddyserver.caddy.plist
# Linux:
systemctl --user restart caddy

Troubleshoot

Cert not issuing: tail -50 /var/log/caddy-error.log | grep -i error — likely expired Vercel API token
DNS not resolving: dig +short appname.YOUR_DOMAIN — should return your Tailscale IP
TLS error (curl exit 35): Cert hasn't provisioned yet, wait 30-60s

For full reference (example apps, key files, build instructions): see reference.md. For OpenClaw gateway integration: see OPENCLAW.md.

---name: caddy-2description: Add, manage, and troubleshoot Caddy reverse proxy routes for local apps via wildcard subdomains.--- # Caddy — Wildcard Reverse Proxy for Local Apps Routes `*.YOUR_DOMAIN` subdomains to local services over HTTPS via Caddy reverse proxy with automatic Let's Encrypt certificates. Designed for Tailscale-only access (no public exposure). > **DNS provider:** This skill uses **Vercel DNS** for DNS-01 ACME challenges. If you use a different DNS provider, swap the `caddy-dns/vercel` plugin and TLS snippet for your provider's equivalent (see [caddy-dns](https://github.com/caddy-dns)). ## Add a New App 1. **Create a background service** (LaunchAgent on macOS, systemd on Linux) — see `reference.md` for templates 2. **Add to Caddyfile** (`~/.config/caddy/Caddyfile`): ```caddy appname.YOUR_DOMAIN { import vercel_tls reverse_proxy localhost:31XX } ``` Also add a `<li>` entry in the dashboard HTML block at the top. 3. **Reload Caddy:** ```bash ~/.local/bin/caddy reload --config ~/.config/caddy/Caddyfile --address localhost:2019 ``` TLS cert provisioning takes 30–60 seconds (DNS-01 challenge). 4. **If it connects to OpenClaw Gateway** — see `OPENCLAW.md` in this folder for gateway-specific config. ## Quick Dev Servers Companion skill: [dev-serve](https://clawhub.com/skills/dev-serve) — one-command dev server + Caddy routing. ```bash dev-serve up ~/projects/myapp # → https://myapp.YOUR_DOMAIN dev-serve down myapp dev-serve ls ``` ## Reload / Restart ```bash # Reload config (no restart, no sudo) ~/.local/bin/caddy reload --config ~/.config/caddy/Caddyfile --address localhost:2019 # Full restart # macOS: sudo launchctl unload /Library/LaunchDaemons/com.caddyserver.caddy.plist sudo launchctl load /Library/LaunchDaemons/com.caddyserver.caddy.plist # Linux: systemctl --user restart caddy ``` ## Troubleshoot - **Cert not issuing:** `tail -50 /var/log/caddy-error.log | grep -i error` — likely expired Vercel API token - **DNS not resolving:** `dig +short appname.YOUR_DOMAIN` — should return your Tailscale IP - **TLS error (curl exit 35):** Cert hasn't provisioned yet, wait 30-60s For full reference (example apps, key files, build instructions): see `reference.md`. For OpenClaw gateway integration: see `OPENCLAW.md`.

Frequently asked questions

Caddy