Index of every page on this site: llms.txt
All skills
wshobson avatar

/mtls-configuration

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.

Use this Skill: https://skilld.dev/gh/wshobson/agents/mtls-configuration

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈52 tokens for metadata: the name and description. ≈615 when used: this file. ≈1.5k more on demand in 1 file.

Description uses 2.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈210 characters, or 2.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides configuration templates and documentation for implementing mutual TLS (mTLS) in zero-trust service mesh environments. It contains no executable scripts or dangerous code.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    2 findings · Score: 80/100

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 6 months ago
  • Security
  • mtls
  • zero-trust
  • tls
  • certificate-management
  • service-mesh
  • kubernetes
  • networking
  • pki

README badge

README badge for wshobson/agents/mtls-configuration

Configures mutual TLS for zero-trust service-to-service communication using sidecar proxies and certificate hierarchies. Covers TLS handshakes, certificate rotation, multi-cluster setups, and debugging strategies for services behind proxies.

Generated from the current SKILL.md.

Does this skill cover certificate rotation and expiry management?
Yes. It includes monitoring certificate expiry, setting up alerts, and automating rotation with short-lived certs (24h or less for workloads) and periodic CA rotation.
What service mesh platforms does this skill target?
The skill provides general mTLS concepts and best practices applicable across service mesh implementations, with references to sidecar proxy patterns and workload certificates, but does not specify a particular platform like Istio or Linkerd.
Does this include multi-cluster mTLS setup?
Yes. The certificate hierarchy covers multi-cluster intermediate CAs and cross-cluster certificate configuration for securing communication across clusters.
What's the recommended approach for enabling mTLS in existing systems?
The skill recommends starting with PERMISSIVE mode and migrating gradually to STRICT, rather than enabling strict mTLS immediately in production.

Generated from the current SKILL.md. These answers refresh after source changes.