CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mtls-configuration

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/cloud-infrastructure/skills/mtls-configuration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill bundles well — a lean overview body with an honest, verified pointer to a real one-level-deep reference file full of executable templates. The body's weaknesses are the absence of any sequenced migration workflow with validation checkpoints, and the ASCII diagrams that re-explain TLS fundamentals Claude already knows.

Suggestions

Replace the TLS-handshake ASCII diagram with a short ordered migration workflow (e.g., 1. deploy PERMISSIVE PeerAuthentication, 2. verify all workloads receive mTLS certs via istioctl, 3. only then switch to STRICT), adding the validation checkpoint the risky policy-migration step currently lacks.

Trim or shrink the certificate-hierarchy diagram to the mesh-specific parts only (cluster-level vs multi-cluster intermediates), dropping the generic Root CA → Intermediate → Workload explanation Claude already knows.

Pull one copy-paste-ready snippet (e.g., the mesh-wide STRICT PeerAuthentication) inline into the body so the most common action is executable without opening the reference file.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the two ASCII diagrams re-explain concepts Claude already knows — the standard TLS handshake sequence ('1. ClientHello ... 5. Encrypted Channel') and the conventional Root CA → Intermediate → Workload hierarchy — with only mild mesh-specific framing, so it 'could be tightened'. It is not a 2 because there is no padded prose or library-comparison filler beyond the diagrams, and not a 4 because the diagrams are genuine trimmable content.

3 / 5

Actionability

There is specific, non-generic guidance ('Start with PERMISSIVE - Migrate gradually to STRICT', 'Use short-lived certs - 24h or less for workloads') plus a working pointer to the template library in references/details.md, but the body itself contains no executable config or commands — everything concrete is deferred to the reference file. This sits at 'some concrete guidance but incomplete' rather than 'mostly executable'.

3 / 5

Workflow Clarity

No step sequence is listed anywhere; the only ordering is the implied 'Start with PERMISSIVE - Migrate gradually to STRICT' hint, and there are no validation checkpoints (e.g., verifying mTLS traffic with istioctl before switching a namespace to STRICT). This matches 'rough sequence present but many gaps; steps poorly defined; validation absent' — it is above a 1 because the migration direction and expiry monitoring give a coherent rough order, but below a 3 because no actual steps are enumerated. Since mesh-wide policy migration is a risky operation, the validation-missing cap of 3 applies regardless.

2 / 5

Progressive Disclosure

The body is a lean overview and clearly signals a single one-level-deep reference — 'Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates' — and that file exists and delivers exactly what is promised (Istio/cert-manager/SPIFFE/Linkerd templates, rotation and debugging commands). This matches the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

13

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'what' and 'Use when' trigger clause in the exact recommended pattern. Its only weaknesses are modest action coverage (just 'Configure') and a few missing natural trigger terms like 'service mesh', 'Istio', 'Linkerd', and 'TLS'.

Suggestions

Add 1-2 more concrete actions to the what-clause, e.g., 'Configure mutual TLS (mTLS) ... rotate certificates, and debug TLS handshake failures' to lift specificity from one action to several.

Include natural trigger synonyms and platform names users would say, such as 'service mesh', 'Istio', 'Linkerd', or 'cert rotation', to improve trigger-term coverage and reduce misses.

DimensionReasoningScore

Specificity

The description names a concrete domain ('mutual TLS (mTLS)', 'zero-trust service-to-service communication') and one concrete action ('Configure'), matching the '1-2 concrete actions, not comprehensive' anchor. It does not list several actions (e.g., rotation, debugging, policy migration), so it falls short of a 4.

3 / 5

Completeness

It explicitly answers both questions: 'Configure mutual TLS (mTLS) for zero-trust service-to-service communication' (what) and 'Use when implementing zero-trust networking, certificate management, or securing internal service communication' (when, with concrete trigger phrases). This mirrors the anchor-5 good example pattern.

5 / 5

Trigger Term Quality

Natural phrases like 'mutual TLS', 'mTLS', 'zero-trust', and 'certificate management' cover what users would actually say, but common synonyms and platform names (TLS, Istio, Linkerd, service mesh, cert rotation) are missing, which is exactly the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

'mutual TLS (mTLS)' and 'zero-trust' define a fairly clear niche with distinct triggers, but the broad 'certificate management' and generic TLS/security wording create minor overlap risk with general certificate or security-hardening skills, matching 'mostly distinct; minor overlap risk' rather than the clear-niche anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/cloud-infrastructure/skills/mtls-configuration/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.