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

—

Does it follow best practices?

Impact

97%

1.02x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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 with executable templates and commands but is a token-heavy monolith that explains concepts Claude already knows and lacks sequenced validation workflows. Splitting platform-specific templates into one-level-deep reference files and trimming the concept diagrams would lift the weaker dimensions.

Suggestions

Remove the ASCII mTLS-flow and certificate-hierarchy diagrams and the redundant 'When to Use This Skill' list; Claude already knows these concepts and they restate the description.

Restructure certificate rotation and debugging as numbered workflows with explicit validation checkpoints (e.g., verify cert expiry before and after `kubectl rollout restart`).

Move the per-platform templates (Istio, cert-manager, SPIRE, Linkerd) into separate reference files linked one level deep from a concise overview in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly executable templates and commands, but it spends tokens on ASCII diagrams explaining the mTLS handshake flow and certificate hierarchy (concepts Claude already knows) and a redundant "When to Use This Skill" list that restates the description.	2 / 3
Actionability	It provides numerous copy-paste-ready, executable YAML manifests (Istio, cert-manager, SPIRE, Linkerd) and concrete bash debugging commands with specific flags and paths.	3 / 3
Workflow Clarity	Certificate rotation and debugging are presented as command catalogs rather than a sequenced workflow with validation checkpoints, and the destructive rollout-restart step lacks a verify-before-proceed feedback loop.	2 / 3
Progressive Disclosure	At ~350 lines with no bundle files or references, the skill is a monolithic document; content such as per-platform templates and debugging could be split into separate referenced files, though sections are reasonably organized.	2 / 3
	Total	9 / 12 Passed

Description

90%

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

The description is concise, uses third-person voice, and clearly answers both what and when with a strong explicit trigger. Its only gap is listing a single action rather than multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete action ("Configure mutual TLS (mTLS) for zero-trust service-to-service communication") but offers only a single primary action rather than the multiple specific concrete actions the level-3 anchor requires.	2 / 3
Completeness	It explicitly states what the skill does ("Configure mutual TLS...") and when to use it via an explicit "Use when..." trigger clause, satisfying both the what and the when.	3 / 3
Trigger Term Quality	"Use when implementing zero-trust networking, certificate management, or securing internal service communication" covers natural terms a user would say (zero-trust networking, certificate management, securing internal communication), with mTLS as a recognizable keyword.	3 / 3
Distinctiveness Conflict Risk	mTLS for zero-trust service-to-service communication is a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: abece4a

Reviewed: 4 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.