Contract
- Input: service inventory, traffic topology, security requirements, and observability needs.
- Output: mesh architecture with trust model, traffic policies, and observability configuration.
- Scope: stay within the skill's declared boundaries; do not broaden without explicit direction.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.
Provenance
| Question |
Answer |
| What is the source of truth? |
The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? |
Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? |
Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? |
The next skill in the workflow or the user |
| What evidence proves it is done? |
Completion criteria met, artifact saved, validation passed |
| What risk remains? |
Subjective judgment calls, missing context, or external dependency failures |
Artifact
Emit ServiceMeshArtifact as both:
- JSON:
.agents/skills/platform/artifacts/service-mesh/{identifier}.json
- Markdown view: same filename with
.md extension
Service Mesh
Use this skill when designing or reviewing a service mesh — Istio, Linkerd, Cilium, or similar — for mTLS, traffic management, observability, and zero-trust networking.
Process
1. Map service topology
- Inventory all services, their namespaces, communication patterns, and dependencies.
- Identify critical paths, latency-sensitive services, and blast-radius concerns.
- Define namespace and mesh boundary strategy.
Completion criterion: service topology documented with critical paths and mesh boundary.
2. Design zero-trust security
- Define mTLS policy: permissive, strict, or per-service migration strategy.
- Plan authorization policies: which services can call which, with what method/path constraints.
- Define certificate rotation and external CA integration if needed.
Completion criterion: mTLS and authorization policy documented with migration strategy.
3. Configure traffic management
- Define routing rules, retries, timeouts, and circuit breakers per service.
- Plan canary releases, A/B testing, and traffic splitting via header or weight routing.
- Design fault injection rules for resilience testing in staging.
Completion criterion: traffic management rules documented with rollout and rollback behavior.
4. Plan observability
- Configure automatic metric emission: request rate, error rate, latency (RED metrics).
- Enable distributed tracing with W3C TraceContext propagation.
- Define access logging policy and sampling rate.
Completion criterion: RED metrics, tracing, and access log policy documented.
5. Design ingress and egress
- Configure ingress gateway for north-south traffic with TLS termination.
- Define egress policy: which services may call external endpoints and through which egress gateway.
- Plan DNS resolution and service entry configuration for external services.
Completion criterion: ingress/egress policy documented with TLS and access control.
6. Plan operations and rollout
- Define sidecar injection strategy (automatic namespace-wide or manual per pod).
- Plan mesh upgrade procedure with canary control plane and data plane validation.
- Document rollback triggers and mesh-aware debugging procedures.
Completion criterion: rollout and rollback procedure documented.
Rules
- Rule: never disable mTLS in production without an explicit, time-boxed exception.
- Rule: keep mesh configuration in Git; use progressive rollout for policy changes.
- Rule: define retry budgets; unlimited retries amplify failures.
- Rule: scope authorization policies to least privilege; default deny.
- Rule: instrument mesh metadata carefully; avoid logging request/response bodies in production.
- Rule: validate mesh config in staging with production traffic mirrors before promoting.
Completion
- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
@include .agents/skills/platform/contract-base.xml
1---2name: "service-mesh"3category: "backend"4maturity: "stable"5version: "1"6description: "Service mesh (Istio, Linkerd, Cilium, mTLS, traffic splitting, observability)."7license: "MIT"8capabilities:9 - apply service mesh methods within explicit backend boundaries10 - analyze service mesh (istio, linkerd, cilium, mtls, traffic splitting, observability) with assumptions, constraints, and failure modes11 - produce and validate a backend artifact with evidence, decisions, and next steps12outputs: "mesh architecture with trust model, traffic policies, and observability configuration."13sideEffects: []14dependencies: []15stopCondition: "Service mesh design complete; artifact saved; completion criteria checked."16risk: "medium"17trustTier: "3"18maxIterations: "6"19promptVersion: "2.0"20artifactType: "backend"21modelTier: "reasoning"22evaluators: ["behavioral", "regression"]23fixturesPath: .agents/skills/platform/fixtures/behavioral/service-mesh.json24diataxis: "how-to"25tags: ["backend"]26compatibility: []27approvalRequired: "true"28approvalFor: []29metadata:30 source: https://skillmd.com/skills/quantumquirkxyz/service-mesh31---3233## Contract3435- Input: service inventory, traffic topology, security requirements, and observability needs.36- Output: mesh architecture with trust model, traffic policies, and observability configuration.37- Scope: stay within the skill's declared boundaries; do not broaden without explicit direction.38- Rule: documented standards override defaults; explicit project rules take precedence.39- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4041## Provenance4243| Question | Answer |44|---|---|45| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |46| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |47| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |48| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |49| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |50| What risk remains? | Subjective judgment calls, missing context, or external dependency failures515253## Artifact5455Emit `ServiceMeshArtifact` as both:56- JSON: `.agents/skills/platform/artifacts/service-mesh/{identifier}.json`57- Markdown view: same filename with `.md` extension585960# 61# 62# Service Mesh6364Use this skill when designing or reviewing a service mesh — Istio, Linkerd, Cilium, or similar — for mTLS, traffic management, observability, and zero-trust networking.656667## Process6869### 1. Map service topology70- Inventory all services, their namespaces, communication patterns, and dependencies.71- Identify critical paths, latency-sensitive services, and blast-radius concerns.72- Define namespace and mesh boundary strategy.7374**Completion criterion:** service topology documented with critical paths and mesh boundary.7576### 2. Design zero-trust security77- Define mTLS policy: permissive, strict, or per-service migration strategy.78- Plan authorization policies: which services can call which, with what method/path constraints.79- Define certificate rotation and external CA integration if needed.8081**Completion criterion:** mTLS and authorization policy documented with migration strategy.8283### 3. Configure traffic management84- Define routing rules, retries, timeouts, and circuit breakers per service.85- Plan canary releases, A/B testing, and traffic splitting via header or weight routing.86- Design fault injection rules for resilience testing in staging.8788**Completion criterion:** traffic management rules documented with rollout and rollback behavior.8990### 4. Plan observability91- Configure automatic metric emission: request rate, error rate, latency (RED metrics).92- Enable distributed tracing with W3C TraceContext propagation.93- Define access logging policy and sampling rate.9495**Completion criterion:** RED metrics, tracing, and access log policy documented.9697### 5. Design ingress and egress98- Configure ingress gateway for north-south traffic with TLS termination.99- Define egress policy: which services may call external endpoints and through which egress gateway.100- Plan DNS resolution and service entry configuration for external services.101102**Completion criterion:** ingress/egress policy documented with TLS and access control.103104### 6. Plan operations and rollout105- Define sidecar injection strategy (automatic namespace-wide or manual per pod).106- Plan mesh upgrade procedure with canary control plane and data plane validation.107- Document rollback triggers and mesh-aware debugging procedures.108109**Completion criterion:** rollout and rollback procedure documented.110111## Rules112113- Rule: never disable mTLS in production without an explicit, time-boxed exception.114- Rule: keep mesh configuration in Git; use progressive rollout for policy changes.115- Rule: define retry budgets; unlimited retries amplify failures.116- Rule: scope authorization policies to least privilege; default deny.117- Rule: instrument mesh metadata carefully; avoid logging request/response bodies in production.118- Rule: validate mesh config in staging with production traffic mirrors before promoting.119120## Completion121122- the skill's completion criteria are explicitly checked123- the artifact is saved and validated124- any blockers or skipped validations are documented125- the next consumer is identified or the work is handed off126---127@include .agents/skills/platform/contract-base.xml