ssl-certificate-management — Claude Code skill: install & guide
Automates SSL/TLS certificate provisioning, renewal, and monitoring using Let's Encrypt, AWS ACM, or Vault. Keeps production HTTPS running without manual overhead.
npx skills add aj-geddes/useful-ai-prompts --skill ssl-certificate-management -a claude-codeWhat ssl-certificate-management does
The skill provides guidelines and templates for TLS infrastructure. It includes cert-manager manifests for Kubernetes, covering HTTP-01 ingress solvers and Route53 DNS-01 challenges for wildcard domains. This setup prevents downtime during rotations.
Guides also cover AWS ACM workflows, certificate pinning, and HashiCorp Vault for internal PKI. Cryptographic baselines require at least RSA 2048 or ECDSA 256 keys.
Committing private keys to git destroys transport security. The skill strictly bars committing certificates to version control and forbids self-signed certificates in production environments.
What it helps with
- configure cert-manager ClusterIssuers with HTTP-01 and Route53 solvers
- automate TLS certificate issuance and renewal via Let's Encrypt
- issue wildcard certificates for multi-domain infrastructures
- set up certificate expiration monitoring and alerts
- configure AWS ACM certificate provisioning and rotation
Example prompts for the agent
- Generate a cert-manager ClusterIssuer manifest using Let's Encrypt and Route53 DNS-01 for wildcard domains.
- Set up automated TLS certificate renewal and expiration alerting.
- Create an AWS ACM certificate configuration with automated validation.
How to install ssl-certificate-management
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill ssl-certificate-management -a claude-code2Manually: put the files in place
~/.claude/skills/ssl-certificate-management/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ssl-certificate-management/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill ssl-certificate-management -a codex2Manually: put the files in place
.agents/skills/ssl-certificate-management/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill ssl-certificate-management -a cursor2Manually: put the files in place
.cursor/skills/ssl-certificate-management/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts ssl-certificate-management2Manually: put the files in place
.github/skills/ssl-certificate-management/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill ssl-certificate-management -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/ssl-certificate-managementManually: put the files in place
.devin/skills/ssl-certificate-management/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill ssl-certificate-management -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ssl-certificate-management
How do I install ssl-certificate-management in Claude Code?
Run npx skills add aj-geddes/useful-ai-prompts --skill ssl-certificate-management -a claude-code in your terminal. The skill file is placed at ~/.claude/skills/ssl-certificate-management/SKILL.md.
Which certificate authorities and tools does this skill cover?
It covers Let's Encrypt with cert-manager, AWS Certificate Manager (ACM), and HashiCorp Vault for internal PKI.
What key standards does the skill enforce?
It requires key lengths of at least 2048 bits for RSA or 256 bits for ECDSA, while blocking private key sharing and git commits.
Source text
SKILL.md · MIT
---
name: ssl-certificate-management
description: >
Manage SSL/TLS certificates with automated provisioning, renewal, and
monitoring using Let's Encrypt, ACM, or Vault.
---
# SSL Certificate Management
## Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
## Overview
Implement automated SSL/TLS certificate management across infrastructure, including provisioning, renewal, monitoring, and secure distribution to services.
## When to Use
- HTTPS/TLS enablement
- Certificate renewal automation
- Multi-domain certificate management
- Wildcard certificate handling
- Certificate monitoring and alerts
- Zero-downtime certificate rotation
- Internal PKI management
## Quick Start
Minimal working example:
```yaml
# cert-manager-setup.yaml
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: letsencrypt-prod
spec:
acme:
server: https://acme-v02.api.letsencrypt.org/directory
email: [email protected]
privateKeySecretRef:
name: letsencrypt-prod
solvers:
# HTTP-01 solver for standard domains
- http01:
ingress:
class: nginx
selector:
dnsNames:
- "myapp.com"
- "www.myapp.com"
# DNS-01 solver for wildcard domains
- dns01:
route53:
region: us-east-1
// ... (see reference guides for full implementation)
```
## Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents |
|---|---|
| [Let's Encrypt with Cert-Manager](references/lets-encrypt-with-cert-manager.md) | Let's Encrypt with Cert-Manager |
| [AWS ACM Certificate Management](references/aws-acm-certificate-management.md) | AWS ACM Certificate Management |
| [Certificate Monitoring and Renewal](references/certificate-monitoring-and-renewal.md) | Certificate Monitoring and Renewal |
| [Automated Certificate Renewal](references/automated-certificate-renewal.md) | Automated Certificate Renewal |
| [Certificate Pinning](references/certificate-pinning.md) | Certificate Pinning |
## Best Practices
### ✅ DO
- Automate certificate renewal
- Use Let's Encrypt for public certs
- Monitor certificate expiration
- Use wildcard certs strategically
- Implement certificate pinning
- Rotate certificates regularly
- Store keys securely
- Use strong key sizes (2048+ RSA, 256+ ECDSA)
### ❌ DON'T
- Manual certificate management
- Self-signed certs in production
- Share private keys
- Ignore expiration warnings
- Use weak key sizes
- Mix dev and prod certs
- Commit certs to git
- Disable certificate validation
© aj-geddes · MIT · aj-geddes/useful-ai-prompts