Set up TLS certificates with Let's Encrypt and automate renewal
Scanned 9/3/2026
Install to Claude Code
npx -y skills add black141312/ada --skill ssl-setup --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ssl Setup?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/black141312-ssl-setup)More formats (shields.io, HTML) on the badges page.
---
name: ssl-setup
description: Set up TLS certificates with Let's Encrypt and automate renewal
category: cloud
---
# SSL Setup
Use this to get a domain onto HTTPS with a free, auto-renewing Let's Encrypt certificate — and to make sure renewal won't silently lapse.
1. Confirm the domain's DNS A/AAAA record points at the server and ports 80/443 are reachable.
2. Pick a challenge: HTTP-01 (certbot --webroot/--nginx) for a public server, or DNS-01 for wildcards and private hosts.
3. Issue the cert with certbot (e.g. `certbot --nginx -d example.com -d www.example.com`), supplying a contact email.
4. Wire the cert into the server (nginx/apache) and force HTTP→HTTPS redirects.
5. Verify the chain and expiry with `openssl s_client -connect host:443` or an SSL Labs scan.
6. Confirm auto-renewal: `certbot renew --dry-run` and ensure the systemd timer / cron job is active.
## Rules
- Let's Encrypt certs last 90 days — renewal MUST be automated; a manual process will eventually expire.
- Test against the staging ACME endpoint first to avoid hitting rate limits on bad attempts.
- Use DNS-01 for wildcard (`*.example.com`) certs; HTTP-01 can't issue wildcards.
- Keep private keys `600` and owned by the service user; never commit them to git.
- After renewal, reload (not restart) the web server so it picks up the new cert with zero downtime.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.