Name: service-mesh-expert
Rating: 52 (1 reviews)
Author: administrakt0r

service-mesh-expert

Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh con

Quality

58%

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/service-mesh-expert/SKILL.md

The canonical home for this skill is service-mesh-expert in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

50%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 well-structured and concise but lacks any executable artifacts (YAML/code/commands) for a domain that is fundamentally configuration-driven, and its single external reference points to a missing file. Validation is absent from the workflow despite security-policy operations.

Suggestions

Add executable examples: sample Istio VirtualService/DestinationRule YAML or kubectl/istioctl commands for the common tasks in Capabilities.

Add a validation checkpoint to the workflow (e.g., verify mTLS mode and policy enforcement with istioctl experimental authz before declaring done).

Create the referenced `references/implementation-playbook.md` and fix the path from `resources/` to `references/`, or remove the dangling reference.

Dimension	Reasoning	Score
Conciseness	The body is lean with terse bullet lists and no padding or explanation of concepts Claude already knows; not a 5 because generic boilerplate steps like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices' could be trimmed.	4 / 5
Actionability	Guidance is high-level and abstract ('Configure observability (metrics, traces, logs)') with no executable YAML, commands, or code examples, which for an Istio/Linkerd skill leaves the specific steps to execute missing; not a 3 because best-practice bullets add only minimal concrete direction.	2 / 5
Workflow Clarity	A seven-step sequence is present but contains no validation checkpoints or feedback loops, and for operations involving mTLS enforcement and security policies the rubric caps workflow clarity at 3 without validation; not a 4 because checkpoints are entirely absent.	3 / 5
Progressive Disclosure	Sections are well organized and a reference is signaled ('open `resources/implementation-playbook.md`'), but the referenced file does not exist (no references/resources/scripts/assets bundle present) and the path uses `resources/` rather than the conventional `references/`; not a 4 because the one-level reference is broken rather than merely having minor gaps.	3 / 5
	Total	12 / 20 Passed

Description

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

The description clearly establishes a focused service-mesh niche with good natural trigger terms, but it omits an explicit "Use when..." clause (capping completeness at 3) and appears truncated mid-word at "con", which weakens an otherwise strong description.

Suggestions

Add an explicit 'Use when...' clause naming concrete user triggers (e.g., 'Use when setting up Istio/Linkerd, configuring mTLS, or debugging service mesh connectivity').

Complete the truncated final word and verify the description string is not cut off.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete capability areas ("traffic management, security policies, observability integration, and multi-cluster mesh"), matching the anchor listing several specific actions with minor coverage gaps; not a 5 because it stops at capability categories rather than enumerating concrete actions.	4 / 5
Completeness	The description clearly states what the skill does but provides no explicit "Use when..." trigger guidance, which per the rubric caps completeness at 3; not a 4 because the when is absent rather than merely weakly implied.	3 / 5
Trigger Term Quality	Includes natural terms users would say ("service mesh", "Istio", "Linkerd", "zero-trust networking", "mTLS"), giving good keyword coverage; not a 5 because it lacks common synonyms and the description is truncated mid-word.	4 / 5
Distinctiveness Conflict Risk	Naming Istio and Linkerd carves a clear, mostly distinct niche with minor overlap risk against general Kubernetes skills; not a 5 because the missing explicit trigger phrase and truncated text leave it slightly less anchored than the 5 example.	4 / 5
	Total	15 / 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/service-mesh-expert/SKILL.md
Commit: 57c135b

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