Name: mtls-configuration
Rating: 60.8 (1 reviews)
Author: administrakt0r

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/AI-Agents-Safe-Coding-Skills-claude/skills/mtls-configuration/SKILL.md

The canonical home for this skill is mtls-configuration in administrakt0r/AI-Agents-Safe-Coding-Skills

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 body is highly actionable thanks to comprehensive copy-paste templates and commands, but it is padded with concept diagrams Claude already knows, lacks a real sequenced workflow with validation checkpoints, and inlines content that belongs in separate reference files (one of which is referenced but missing).

Suggestions

Remove or trim the 'Core Concepts' ASCII diagrams and the generic 'Instructions' boilerplate; assume Claude knows the mTLS handshake and CA hierarchy and keep only non-obvious guidance.

Replace the generic Instructions with a concrete sequenced workflow (e.g. install CA → issue workload certs → enable PERMISSIVE → verify traffic → switch to STRICT) with explicit validation checkpoints, especially a validate-then-proceed loop around certificate rotation.

Move the full templates into one-level-deep reference files (e.g. references/istio-mtls.md, references/spire.md) and either create the referenced resources/implementation-playbook.md or fix the path so the signaled reference actually exists.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with dense, useful templates, but the ASCII 'Core Concepts' diagrams re-explain the mTLS handshake and CA hierarchy Claude already knows and the 'Instructions' section is generic boilerplate ('Clarify goals...', 'Apply relevant best practices and validate outcomes').	3 / 5
Actionability	Five copy-paste-ready YAML templates (Istio PeerAuthentication/DestinationRule, cert-manager, SPIRE, Linkerd) plus concrete bash debugging/rotation commands cover the common cases fully.	5 / 5
Workflow Clarity	There is no genuine sequenced implementation workflow — the 'Instructions' are generic and unsequenced — and the certificate-rotation step (kubectl rollout restart) is a batch operation with no validation feedback loop, capping this dimension at 3.	3 / 5
Progressive Disclosure	Section structure exists and one reference is signaled ('open resources/implementation-playbook.md'), but that file does not exist in the bundle and the bulk of the content (five full templates, diagrams) is inlined rather than split into one-level-deep reference files.	3 / 5
	Total	14 / 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-constructed description that clearly answers both what the skill does and when to use it, with natural trigger terms and a distinct zero-trust/mTLS niche. Its only weakness is that the 'what' names a single action rather than enumerating several concrete capabilities.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action ('Configure mutual TLS (mTLS) for zero-trust service-to-service communication'), but does not enumerate multiple specific actions, so it sits at the 1-2-concrete-actions anchor rather than the comprehensive level above.	3 / 5
Completeness	It explicitly states 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, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger terms are present ('mTLS', 'zero-trust networking', 'certificate management', 'securing internal service communication'), giving good coverage; it falls short of 5 because synonyms/variants like 'TLS', 'service mesh', or 'certificates' are absent.	4 / 5
Distinctiveness Conflict Risk	The mTLS / zero-trust service-to-service framing is a clear niche with distinct triggers, but the 'certificate management' trigger introduces minor overlap risk with a generic certificate-management skill, keeping it just below 5.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/mtls-configuration/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.