ClawHub

Caddy

v1.0.0

Configure Caddy as a reverse proxy with automatic HTTPS and simple Caddyfile syntax.

⭐ 2· 968·7 current·8 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (Caddy reverse proxy + HTTPS) align with the requirements and instructions: the SKILL.md only references Caddy-specific commands, config paths (/etc/caddy/Caddyfile, /data, /config, ~/.local/share/caddy) and Docker networking relevant to running Caddy. No unrelated binaries, services, or credentials are requested.
✓
Instruction Scope
The runtime instructions stay within the scope of configuring and debugging Caddy: advice on ACME, formatting/validation commands (caddy fmt, caddy validate, caddy adapt), reload vs restart, certificate storage, Docker networking, and debugging paths. It does reference local filesystem paths and ports 80/443, but these are expected and necessary for Caddy operation and not extraneous data-collection or exfiltration steps.
✓
Install Mechanism
Instruction-only skill with no install spec or code to fetch. This is low-risk: nothing will be written or executed by the skill itself beyond instructing the agent to use the existing caddy binary that the environment must provide.
✓
Credentials
No environment variables, credentials, or unrelated config paths are requested. The only required binary is caddy, which is proportionate to the stated functionality of configuring Caddy.
✓
Persistence & Privilege
The skill is not marked always:true and does not request persistent system modifications. It only advises on using system paths that Caddy normally uses; it does not instruct the agent to modify other skills or global agent settings.
Assessment
This skill is a safe, instruction-only reference for configuring Caddy. Before using it: ensure the caddy binary on your system is from an official/trusted source; be aware Caddy needs permission to bind ports 80/443 (may require root or CAP_NET_BIND_SERVICE); back up /data and /config if you rely on persisted certificates; use Let's Encrypt staging for testing to avoid rate limits; review any commands the agent executes (caddy validate/format/reload) to confirm they match your system paths and intentions.

Like a lobster shell, security has layers — review code before you run it.

latestvk979rybece2xf7fexrsf7r814x80wbz9

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🔒 Clawdis
OSLinux · macOS · Windows
Binscaddy

Comments