I built tlsctl, a small CLI for inspecting, testing, and debugging TLS connections:

https://github.com/catay/tlsctl

It aims to make TLS diagnostics more readable and structured than stitching together `openssl` and other ad-hoc commands. You can inspect certificates and chains, check protocol support, and output in different formats.

Part of the motivation was practical (I got tired of parsing `openssl s_client` output), and part was educational. I wanted to build more hands-on experience with agentic engineering workflows. Shout out to https://ampcode.com/ for their coding agent.

I’d love feedback on usefulness, missing features, and whether this fits into real-world TLS troubleshooting workflows.

Thanks!

Steven