mtls-configuration — Claude Code skill: what it does, install
This skill configures mutual TLS for service-to-service communication. Use it for zero-trust networking, certificate management, or TLS debugging.
/plugin marketplace add wshobson/agents
/plugin install cloud-infrastructure@claude-code-workflowsWhat mtls-configuration does
The skill covers mTLS for protected communication between services. It explains the handshake through proxies or sidecars: both sides exchange certificates, verify them, and establish an encrypted channel. It also describes a certificate hierarchy with a Root CA, intermediate CAs, and workload certificates.
Its guidance includes moving from PERMISSIVE to STRICT, monitoring certificate expiry, rotating certificates and the CA, and logging TLS errors. Concrete templates and worked examples are kept in references/details.md. Multi-cluster communication is covered as well.
Install it when your project has service-to-service traffic that needs mTLS. It is a poor fit for an application without this communication model.
What it helps with
- configure mTLS between services
- design a CA hierarchy for workloads
- move a service mesh from PERMISSIVE to STRICT
- debug a TLS handshake failure
- plan certificate and CA rotation
Example prompts for the agent
- Configure mTLS for communication between services A and B through sidecar proxies.
- Show how to move from PERMISSIVE to STRICT and verify the full certificate chain.
- Investigate this TLS handshake error and suggest a certificate rotation plan.
How to install mtls-configuration
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install cloud-infrastructure@claude-code-workflowsThis installs the whole cloud-infrastructure plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill mtls-configuration -a claude-code3Manually: put the files in place
~/.claude/skills/mtls-configuration/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mtls-configuration/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill mtls-configuration -a codex2Manually: put the files in place
.agents/skills/mtls-configuration/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill mtls-configuration -a cursor2Manually: put the files in place
.cursor/skills/mtls-configuration/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents mtls-configuration2Manually: put the files in place
.github/skills/mtls-configuration/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/cloud-infrastructure/skills/mtls-configurationManually: put the files in place
.devin/skills/mtls-configuration/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about mtls-configuration
How do I install mtls-configuration in Claude Code?
Run npx skills add wshobson/agents --skill mtls-configuration -a claude-code. The skill file is placed at ~/.claude/skills/mtls-configuration/SKILL.md.
What does mtls-configuration do?
It guides mutual TLS setup for service-to-service communication, including the TLS handshake, certificate verification, CA hierarchy, and certificate rotation.
Which platforms support mtls-configuration?
The skill is listed for Claude Code, Codex, and Cursor. Templates and detailed worked examples are in references/details.md.
Source text
SKILL.md · MIT
---
name: mtls-configuration
description: Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.
---
# mTLS Configuration
Comprehensive guide to implementing mutual TLS for zero-trust service mesh communication.
## When to Use This Skill
- Implementing zero-trust networking
- Securing service-to-service communication
- Certificate rotation and management
- Debugging TLS handshake issues
- Compliance requirements (PCI-DSS, HIPAA)
- Multi-cluster secure communication
## Core Concepts
### 1. mTLS Flow
```
┌─────────┐ ┌─────────┐
│ Service │ │ Service │
│ A │ │ B │
└────┬────┘ └────┬────┘
│ │
┌────┴────┐ TLS Handshake ┌────┴────┐
│ Proxy │◄───────────────────────────►│ Proxy │
│(Sidecar)│ 1. ClientHello │(Sidecar)│
│ │ 2. ServerHello + Cert │ │
│ │ 3. Client Cert │ │
│ │ 4. Verify Both Certs │ │
│ │ 5. Encrypted Channel │ │
└─────────┘ └─────────┘
```
### 2. Certificate Hierarchy
```
Root CA (Self-signed, long-lived)
│
├── Intermediate CA (Cluster-level)
│ │
│ ├── Workload Cert (Service A)
│ └── Workload Cert (Service B)
│
└── Intermediate CA (Multi-cluster)
│
└── Cross-cluster certs
```
## Templates and detailed worked examples
Full template library and detailed worked examples live in `references/details.md`. Read that file when you need the concrete templates.
## Best Practices
### Do's
- **Start with PERMISSIVE** - Migrate gradually to STRICT
- **Monitor certificate expiry** - Set up alerts
- **Use short-lived certs** - 24h or less for workloads
- **Rotate CA periodically** - Plan for CA rotation
- **Log TLS errors** - For debugging and audit
### Don'ts
- **Don't disable mTLS** - For convenience in production
- **Don't ignore cert expiry** - Automate rotation
- **Don't use self-signed certs** - Use proper CA hierarchy
- **Don't skip verification** - Verify the full chain
© Seth Hobson · MIT · wshobson/agents