metalbear-co/mirrord / skills/skills/mirrord-header-propagation
mirrord-header-propagation
VerifiedMakes a codebase propagate W3C baggage (the `baggage` header carrying `mirrord-session=<key>`) end to end, so mirrord HTTP filters, preview environments, and queue splitting can route a whole request chain to one developer's session. Detects existing OpenTelemetry, Datadog, or other tracing that can already propagate baggage and enables it; otherwise adds a small propagation layer. Covers inbound/outbound HTTP and gRPC, publishing to and consuming from Kafka, RabbitMQ, SQS/SNS, GCP Pub/Sub, Azure Service Bus, NATS, Redis Pub/Sub, BullMQ and Temporal, per-message context restore in consumers, and storage hand-offs such as a GCS signed URL upload that triggers Pub/Sub or an S3 presigned upload that triggers SQS. Ends with a report of every flow found and which ones still drop the header. Use when the user asks to propagate headers, baggage, tracestate, the mirrord session key, or trace context across services or queues, or when a mirrord filter matches the first service but not downstream services or queue consumers.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 2.3 KB |
| SKILL.md | skill md | 18.3 KB |
| references/libraries.md | markdown | 6.3 KB |
| references/propagation-layer.md | markdown | 15.2 KB |
| references/storage-handoffs.md | markdown | 7.4 KB |
README.md
View on GitHub# mirrord-header-propagation
Make your services forward the W3C `baggage` header (carrying `mirrord-session=<key>`) across every hop: HTTP, gRPC, message queues, and object-storage uploads. mirrord HTTP filters, preview environments, and queue splitting can then route a whole request chain, not just the first service, to one developer's session.
## What it does
This skill helps AI agents:
- **Map** every flow in the codebase: HTTP/gRPC ingress and egress, producers and consumers for Kafka, RabbitMQ, SQS/SNS, GCP Pub/Sub, Azure Service Bus, NATS, Redis Pub/Sub, BullMQ and Temporal, and storage-triggered flows
- **Detect** OpenTelemetry, Datadog, Micrometer/Spring, or other tracing that can already propagate baggage, and find the hops it misses (propagator list, uninstrumented messaging clients, prefixed attribute names)
- **Enable** propagation in that existing stack, or **add** a minimal OpenTelemetry baggage-only layer where there isn't one
- **Restore** context per message in consumers, so downstream calls and publishes carry the session on
- **Carry** baggage through storage hand-offs: GCS signed URL → Pub/Sub and S3 presigned URL → SQS, via signed object metadata
- **Report** every flow as already covered, fixed, or not covered, with what it would take to close each remaining gap. When propagation already works end to end, the report says so and the skill changes nothing.
## Example prompts
```
"Make our services propagate the mirrord session baggage header across Kafka and HTTP"
"Our mirrord filter matches the API but not the worker that consumes from SQS — fix propagation"
"Check whether our OpenTelemetry setup already forwards baggage to Pub/Sub consumers"
"Uploads go through a GCS signed URL and a Pub/Sub notification — keep the session through that"
"Which flows in this repo would drop the baggage header?"
```
## Prerequisites
- Source access to the services in the request path
- Nothing mirrord-specific to install. Verification with a live session uses mirrord, and queue splitting needs the mirrord Operator (Team / Enterprise)
## Learn more
- [Queue splitting](https://metalbear.com/mirrord/docs/sharing-the-cluster/queue-splitting)
- [HTTP filtering](https://metalbear.com/mirrord/docs/using-mirrord/incoming-traffic/filter-incoming-traffic)
- [OpenTelemetry baggage](https://opentelemetry.io/docs/concepts/signals/baggage/)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |