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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

The skill uses good progressive disclosure, keeping the body as an overview and pushing templates into a clearly signaled one-level-deep reference. It is weaker on conciseness (restated description, conceptual diagrams), actionability (no inline executable code), and workflow clarity (no sequenced validated procedure).

Suggestions

Remove the redundant opening sentence and "When to Use This Skill" list, which restate the frontmatter description, or fold them into a single concise trigger section.

Add a short sequenced workflow with validation checkpoints for the riskiest operations — e.g. PERMISSIVE→STRICT migration and CA rotation — including a verify step before declaring strict mode enforced.

Inline one or two copy-paste-ready commands (e.g. an `istioctl authn tls-check` verification snippet) so the body is actionable without requiring a jump to details.md for common tasks.

Dimension	Reasoning	Score
Conciseness	The opening line ("Comprehensive guide to implementing mutual TLS...") and the "When to Use This Skill" list restate the frontmatter description, and the ASCII diagrams explain handshake/CA-hierarchy concepts Claude already knows, so it is mostly efficient but could be tightened below anchor 3.	2 / 3
Actionability	The Do's/Don'ts give concrete tactical advice ("Start with PERMISSIVE", "24h or less") but the body itself contains no executable commands or code, delegating all of that to references/details.md, which is incomplete-but-present guidance at anchor 2 rather than copy-paste-ready anchor 3.	2 / 3
Workflow Clarity	A conceptual handshake-flow diagram and best-practice lists provide some structure, but there is no sequenced operational workflow with explicit validation checkpoints for risky tasks like cert rotation or PERMISSIVE-to-STRICT migration, capping it at anchor 2.	2 / 3
Progressive Disclosure	The body stays an overview (concepts, when-to-use, best practices) and clearly signals a single one-level-deep reference — "Full template library and detailed worked examples live in `references/details.md`" — which is a real file, matching the well-signaled one-level-deep anchor 3.	3 / 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.

A strong, third-person description that answers both what and when with an explicit "Use when" clause and natural trigger terms. The only weakness is that it lists a single action rather than multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	"Configure mutual TLS (mTLS) for zero-trust service-to-service communication" names the domain and a single concrete action (configure mTLS) but does not enumerate multiple specific actions, so it stops short of the comprehensive anchor 3.	2 / 3
Completeness	It states the what ("Configure mutual TLS...") and an explicit when ("Use when implementing zero-trust networking, certificate management, or securing internal service communication"), satisfying both halves at anchor 3.	3 / 3
Trigger Term Quality	"zero-trust networking, certificate management, or securing internal service communication" are natural terms a practitioner would actually say, giving good coverage rather than the single-phrase anchor 2.	3 / 3
Distinctiveness Conflict Risk	The mTLS-for-zero-trust niche is narrow with distinct triggers unlikely to collide with other skills, matching the clear-niche anchor 3.	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: wshobson/agents
Commit: 5cc2549

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