DevOps & Infrastructure
Scans a live Kubernetes environment with `mirrord dump` to find an identifier mirrord can filter traffic on: a header, a `baggage` or `tracestate` member, a tenant or user id, a trace id (W3C, B3, X-Ray, Google, Jaeger), a JWT claim, a cookie, a path segment, or a JSON body field that is present on every hop of a request chain, unique to one developer's traffic, and settable by that developer. Runs mirror-only dumps on each service, sends a tagged probe request at the edge or observes real traffic, scores the candidates, and produces the matching `http_filter` (regex, jq on headers, path, method, body, or combinations) plus a per-hop report of where each identifier is dropped. Installs the mirrord CLI through a package manager when it is missing. Use when the user asks what to filter on, whether the cluster already propagates a request id or trace context, how to isolate their own requests on a shared staging cluster, how to filter on a JWT or cookie with mirrord, or wants to inspect live traffic with mirrord dump. Changes no application code: propagation gaps go to the mirrord-header-propagation skill.
Publisher / source
metalbear-co/mirrord (found on GitHub top repositories)
Upstream record
Version
Version 1
Published
2026-11-20
Publication review
Approved for publication
Content fingerprint
035878c041efb0429634bb6d42e0bc20d97e4c8477110a4c8fe7e1c7d6fa7522
Review before you use it
Publication approval is a recorded review state, not a guarantee of safe execution. Check the upstream license, required tools and permissions, and test in your intended client.
Sign in to inspect the full instructions and download the SKILL.md file. This public page contains metadata only.
Source: https://prompeteer.ai/skills-hub/7a1f754d-4c92-4837-8724-5b28c99f3f1d