Automated summary
Service mesh architecture skill covering Istio and Linkerd: traffic management, mTLS, authorization policies, observability, and multi-cluster federation.
Strengths
- Spans the full lifecycle: topology design, traffic policies, security, then observability
- Ships concrete best practices such as gradually moving from permissive mode to strict mTLS
- Addresses routing, circuit breaking, cross-cluster discovery, and progressive delivery (canary, blue-green)
- Seven-step workflow that ends with operational runbooks
Limitations
- The SKILL.md itself contains no YAML manifests or CLI commands
- Detailed examples are deferred to resources/implementation-playbook.md, which is not included
- Does not substitute for validation on a real cluster (sidecar latency, resource overhead)
Use it to design, secure, or debug a service mesh architecture on Kubernetes.
Avoid it for out-of-scope work such as non-Kubernetes networking, general application code, or plain deployments with no mesh involved.
Security analysis
SafeThe skill contains only advisory guidance about service mesh architecture and operations. It does not instruct destructive commands, secret exfiltration, network calls, or any executable behavior, and declares no tools.
No concerns found
How this analysis is madeExamples
Configure an Istio VirtualService and DestinationRule to send 10% of traffic to the v2 canary of my checkout service, with retries and a circuit breaker on the v1 route.Design a plan to move my Linkerd/Istio namespace from permissive to strict mTLS with AuthorizationPolicies, including how to verify nothing breaks.Services in my mesh intermittently fail with 503s after I added a new namespace — help me trace the issue through sidecar config, destination rules, and mTLS state.name: service-mesh-expert description: "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" risk: safe source: community date_added: "2026-02-27"
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 configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication patterns.
Do not use this skill when
- The task is unrelated to service mesh expert
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Capabilities
- Istio and Linkerd installation, configuration, and optimization
- Traffic management: routing, load balancing, circuit breaking, retries
- mTLS configuration and certificate management
- Service mesh observability with distributed tracing
- Multi-cluster and multi-cloud mesh federation
- Progressive delivery with canary and blue-green deployments
- Security policies and authorization rules
Use this skill when
- Implementing service-to-service communication in Kubernetes
- Setting up zero-trust networking with mTLS
- Configuring traffic splitting for canary deployments
- Debugging service mesh connectivity issues
- Implementing rate limiting and circuit breakers
- Setting up cross-cluster service discovery
Workflow
- Assess current infrastructure and requirements
- Design mesh topology and traffic policies
- Implement security policies (mTLS, AuthorizationPolicy)
- Configure observability (metrics, traces, logs)
- Set up traffic management rules
- Test failover and resilience patterns
- Document operational runbooks
Best Practices
- Start with permissive mode, gradually enforce strict mTLS
- Use namespaces for policy isolation
- Implement circuit breakers before they're needed
- Monitor mesh overhead (latency, resource usage)
- Keep sidecar resources appropriately sized
- Use destination rules for consistent load balancing
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/service-mesh-expert-mrx3xyyx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/service-mesh-expert-mrx3xyyx/download' --output '.skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md.part' && mv '.skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md.part' '.skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md' && test -s '.skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/service-mesh-expert' && cp -R '.skill-downloads/service-mesh-expert-mrx3xyyx' '.claude/skills/service-mesh-expert'Cursor
test -f '.skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md' && test -s '.skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/service-mesh-expert' && cp -R '.skill-downloads/service-mesh-expert-mrx3xyyx' '.cursor/skills/service-mesh-expert'Codex
test -f '.skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md' && test -s '.skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/service-mesh-expert' && cp -R '.skill-downloads/service-mesh-expert-mrx3xyyx' '.agents/skills/service-mesh-expert'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/service-mesh-expert-mrx3xyyx'openskills read 'service-mesh-expert-mrx3xyyx'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/service-mesh-expert-mrx3xyyx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.