tls-certificate-diagnosis

Diagnose TLS/SSL handshake failures and certificate chain issues with OpenSSL.

3|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill tls-certificate-diagnosis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tls-certificate-diagnosis
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/tls-certificate-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill tls-certificate-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openssl, bash, bc, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill resolves complex TLS/SSL connectivity issues by automating the identification of certificate expirations, chain incompleteness, and handshake failures, eliminating the need for manual OpenSSL debugging.

Core Features & Use Cases

  • Automated Symptom Analysis: Instantly maps error messages like certificate verify failed or no shared cipher to specific root causes.
  • Multi-Scenario Diagnosis: Covers certificate expiry, chain validation, CA trust issues, SNI configuration, and mTLS authentication.
  • Use Case: When a production service reports an SSL handshake failure, use this Skill to pinpoint whether the issue is a missing intermediate certificate or a cipher suite mismatch without manual command-line trial and error.

Quick Start

Use the tls-certificate-diagnosis skill to analyze the TLS handshake failure for the domain example.com on port 443.

Frequently Asked Questions about tls-certificate-diagnosis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a TLS handshake failure without manually running OpenSSL commands?

To diagnose a TLS handshake failure, this Skill automates OpenSSL connectivity tests to analyze server responses and pinpoint root causes like missing intermediate certificates or cipher suite mismatches. It eliminates manual command-line trial and error for production services.

Why does my SSL certificate verify failed error occur on port 443?

An SSL certificate verify failed error occurs due to certificate expiration, incomplete certificate chains, or CA trust issues. This Skill maps the specific error message to root causes by validating the certificate chain against the target endpoint.

Can I use OpenSSL to troubleshoot mTLS authentication and SNI configuration issues?

You can use this Skill to troubleshoot mTLS authentication and SNI configuration issues by performing comprehensive OpenSSL validation checks. It covers multi-scenario diagnosis including mutual TLS authentication and server name indication configuration analysis.

What is the best way to identify an incomplete TLS certificate chain during security auditing?

The best way to identify an incomplete TLS certificate chain during security auditing is to automate chain validation checks. This Skill analyzes server responses and certificate chains to detect missing intermediate certificates and configuration issues.

Do I need bash and bc installed to run automated TLS certificate diagnosis?

Yes, you need bash, bc, and OpenSSL installed to run automated TLS certificate diagnosis. These dependencies are required to execute the connectivity tests and validation checks against your target endpoints.

What limitations exist when diagnosing no shared cipher errors with automated scripts?

When diagnosing no shared cipher errors with automated scripts, the analysis depends entirely on the target server's response to the OpenSSL connectivity test. The Skill maps the error to a cipher suite mismatch but requires network access to the endpoint.