Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dicklesworthstone/mtls-configuration
Configure mutual TLS (mTLS) for zero-trust service-to-service communication.
Passed 21 of 23 test cases with the skill, and 18 of 23 without it.
and 1 more in the full report
3 fixed18 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are creating a cert-manager Certificate manifest to issue workload mTLS certificates for my-service in namespace my-namespace using an internal Istio CA ClusterIssuer. To align with zero-trust security best practices for internal workloads, what duration and renewal window should we set in the manifest?
| Checked | Without skill | With skill |
|---|---|---|
| The Certificate duration is configured as 24h. | Passed | Passed |
| The Certificate renewBefore is configured as 8h. | Missed | Passed |
The instructions your model reads when the skill loads.
Comprehensive guide to implementing mutual TLS for zero-trust service mesh communication.
┌─────────┐ ┌─────────┐
│ 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 │ │
└─────────┘ └─────────┘
Root CA (Self-signed, long-lived)
│
├── Intermediate CA (Cluster-level)
│ │
test cases passed, vs 18 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.