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.

1.02x

Quality

75%

Does it follow best practices?

Impact

97%

1.02x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/mtls-configuration/SKILL.md

The canonical home for this skill is mtls-configuration in wshobson/agents

Quality

Content

72%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.

A comprehensive, highly actionable mTLS reference rich in executable templates, but it is a flat inline catalog rather than a sequenced workflow, and lacks validation checkpoints around its destructive operations.

Suggestions

Add explicit validation checkpoints after risky steps (e.g. 'After applying STRICT: run `istioctl authn tls-check` to verify; only then proceed') to lift workflow clarity past the destructive-operation cap.

Split the per-tool templates (Istio, cert-manager, SPIFFE, Linkerd) into separate reference files linked from SKILL.md so the overview stays lean and references are one level deep.

Remove the redundant opening line that restates the description, and consider trimming the ASCII diagrams to recover tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code blocks with terse comments and little concept over-explanation, though the redundant intro line and sizable ASCII diagrams are tokens that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready YAML manifests and bash commands across Istio, cert-manager, SPIFFE/SPIRE, and Linkerd that cover the common mTLS cases, with any abbreviation explicitly signaled.	5 / 5
Workflow Clarity	Destructive/risky operations like mesh-wide STRICT mTLS and rollout-restart certificate rotation lack integrated validate-after-apply feedback loops, so the destructive-cap guideline caps this at 3.	3 / 5
Progressive Disclosure	The ~345-line skill has clear section headers but is entirely monolithic with no bundle files or one-level-deep references, so content that belongs in separate reference files is inlined.	3 / 5
	Total	15 / 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 well-formed description that clearly answers both what it does and when to use it with natural trigger phrases. Its main weakness is that it foregrounds a single action rather than enumerating several concrete capabilities.

Suggestions

Expand the 'what' clause to list several concrete actions (e.g. 'Enable strict mTLS, rotate certificates, debug TLS handshakes') instead of the single verb 'Configure'.

Add common synonyms like 'TLS', 'service mesh', or 'sidecar' to broaden trigger coverage.

Tighten the broad 'certificate management' trigger to scope it to mTLS/zero-trust specifically to reduce overlap with general certificate skills.

Dimension	Reasoning	Score
Specificity	It names the domain (mTLS, zero-trust) and one concrete action ('Configure mutual TLS'), but does not list several specific actions as the 4-5 anchors require.	3 / 5
Completeness	It explicitly states what ('Configure mutual TLS for zero-trust service-to-service communication') and when ('Use when implementing zero-trust networking, certificate management, or securing internal service communication') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Natural domain terms appear ('zero-trust networking', 'certificate management', 'securing internal service communication', 'mTLS') giving good coverage, though a few synonyms (e.g. 'TLS', 'service mesh') are missing.	4 / 5
Distinctiveness Conflict Risk	The mTLS/zero-trust niche is distinct with clear triggers, but the 'certificate management' trigger is broad enough to overlap with a general certificate-management skill, keeping it just below 5.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/mtls-configuration/SKILL.md
Commit: 6453c0b

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.