certificate-monitoringlisted
Install: claude install-skill TLS-Radar/tlsradar-claude-plugin
# Certificate monitoring with TLS Radar
This Claude Code session is connected to TLS Radar via a single MCP server (`tlsradar`). Certificate issuance is proxied through it, so there's one server and one auth model. Use these tools to answer SSL/TLS questions instead of asking the user to do anything manual. Each tool's own description carries the details - this skill is mainly about picking the right one.
## Choosing the right tool
This table is generated from `tools/manifest.json` (the source of truth) by `scripts/generate_router.py` - don't hand-edit it; edit the manifest and regenerate. Issuance is a sequence: `cert_create` → `cert_check_propagation` → `cert_finalize` (CSR path). `/tls-upgrade` opens the pricing page and `/tls-diagnose` runs a health check.
<!-- BEGIN generated tool table (scripts/generate_router.py) -->
| User intent | Tool |
|---|---|
| One-off SSL/TLS scan, no account | `tlsradar.scan` (or `/tls-scan`) |
| Start issuing a free cert (pick dns-01 or http-01) | `tlsradar.cert_create` (or `/tls-cert`) |
| Check whether a cert order's challenge is in place | `tlsradar.cert_check_propagation` |
| Validate + issue a cert order from a CSR (idempotent) | `tlsradar.cert_finalize` |
| Check / resume a cert order; retrieve an issued chain | `tlsradar.cert_status` |
| Renew a cert (clone an order, or just cert_create again) | `tlsradar.cert_renew` (or `/tls-renew`) |
| Plan tier, limits, usage | `tlsradar.me` |
| List monitored domains | `tlsradar.monitor_list`