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

Securityby

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

Quality

Content

65%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 is well-structured with good progressive disclosure, deferring concrete templates to references/details.md. Its weakness is that the body is more conceptual than executable and lacks a sequenced workflow with validation checkpoints for destructive operations like cert rotation.

Suggestions

Add a short numbered implementation workflow with explicit validation checkpoints (e.g., verify peer authentication before moving PERMISSIVE to STRICT) to raise workflow clarity.

Inline at least one minimal executable snippet in the body (e.g., a PeerAuthentication STRICT example) so the skill is actionable without opening references/details.md.

Remove the redundant opening sentence ('Comprehensive guide to implementing mutual TLS...') that restates the H1 and description.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized, mostly assuming Claude's knowledge of TLS; the ASCII diagrams and concise Do/Don't lists earn their place, with only minor padding (e.g., the 'Comprehensive guide...' lead sentence restating the title).	4 / 5
Actionability	The body itself offers conceptual diagrams and Do/Don't bullets rather than executable commands; concrete, copy-paste-ready code and commands live in references/details.md, so the inline guidance is incomplete without that file.	3 / 5
Workflow Clarity	There is no sequenced implementation workflow in the body — it lists concepts and best practices but lacks ordered steps with validation checkpoints for risky operations like cert rotation or mTLS mode migration, which warrants a cap.	3 / 5
Progressive Disclosure	Clear overview structure with templates and worked examples cleanly deferred to a real, one-level-deep references/details.md file that is explicitly signaled; navigation is easy and appropriately split.	5 / 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 solid description that clearly states both capability and usage triggers in third person with natural keywords. It could list more granular concrete actions (rotation, policy authoring, handshake debugging) to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (mTLS, zero-trust) with one concrete action ('Configure mutual TLS') but does not enumerate multiple specific concrete actions like cert rotation, policy authoring, or debugging — coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers both 'what' ('Configure mutual TLS (mTLS) 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.	5 / 5
Trigger Term Quality	Includes natural user-facing phrases ('zero-trust networking', 'certificate management', 'securing internal service communication') that users would plausibly say, though it omits synonyms like 'cert rotation' or file/protocol extensions.	4 / 5
Distinctiveness Conflict Risk	The mTLS/zero-trust niche is fairly distinct from other skills, with specific triggers reducing conflict risk, though 'certificate management' broadly could overlap with a general cert/PKI skill.	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: wshobson/agents
Path: plugins/cloud-infrastructure/skills/mtls-configuration/SKILL.md
Commit: d6837ae

Reviewed: about 12 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.