Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
ServiceProfile retry configuration
ServiceProfile API version
100%
100%
ServiceProfile naming
100%
100%
Route method condition
100%
100%
Route pathRegex condition
100%
100%
Failure response class
100%
100%
GET route retryable
100%
100%
POST route not retryable
100%
100%
Per-route timeout
100%
100%
Retry budget present
100%
100%
Retry budget fields
100%
100%
Namespace match
100%
100%
Without context: $0.2143 · 49s · 9 turns · 10 in / 2,987 out tokens
With context: $0.3531 · 50s · 18 turns · 15 in / 2,788 out tokens
Server authorization policies
Injection annotation
100%
100%
Server API version
100%
100%
ServerAuthorization API version
100%
100%
Server podSelector
100%
100%
meshTLS service accounts
100%
100%
Service account namespace
100%
100%
Unauthenticated ingress allowed
100%
100%
Network CIDR for ingress
100%
100%
Server reference in auth
100%
100%
Namespace consistency
100%
100%
Separate auth resources
100%
100%
Without context: $0.1776 · 45s · 8 turns · 8 in / 2,631 out tokens
With context: $0.3200 · 58s · 14 turns · 14 in / 3,269 out tokens
Canary traffic split and HTTPRoute
TrafficSplit API version
100%
100%
Millicores weight notation
100%
100%
Two backends defined
100%
100%
TrafficSplit service reference
100%
100%
HTTPRoute API version
0%
100%
HTTPRoute parentRefs kind
100%
100%
HTTPRoute parentRefs group
80%
100%
HTTPRoute parentRefs port
100%
100%
HTTPRoute match rules
100%
100%
HTTPRoute backendRefs
100%
100%
Namespace consistency
100%
100%
Without context: $0.3693 · 1m 55s · 11 turns · 11 in / 7,437 out tokens
With context: $0.2933 · 52s · 14 turns · 13 in / 2,878 out tokens
Table of Contents
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.