Skip to content

metalbear-co/mirrord / skills/skills/mirrord-temporal

mirrord-temporal

Verified

Helps DevOps engineers configure mirrord Operator's Temporal task queue splitting feature end-to-end. Generates the MirrordSplitConfig and MirrordPropertyList Kubernetes CRD YAMLs, the matching mirrord.json split_queues section with message_filter and jq_filter, and Helm value guidance. Use this skill whenever the user mentions Temporal splitting with mirrord, Temporal task queue splitting, splitting a Temporal worker, configuring mirrord with Temporal or Temporal Cloud, routing Temporal workflow or activity tasks to a local worker, or troubleshooting Temporal splitting sessions. Also trigger on split_queues with queue_type Temporal, or connecting mirrord to a Temporal frontend. This is an alpha Team/Enterprise feature of mirrord.

FileKindSize
README.mdmarkdown2.2 KB
SKILL.mdskill md21.3 KB
references/temporal-property-list.mdmarkdown5.0 KB
references/temporal-split-config.mdmarkdown8.2 KB
# mirrord-temporal

Configure mirrord Operator's Temporal task queue splitting: route only the workflow and activity tasks that match your filter to your local worker, while the deployed worker keeps everything else. (Alpha, Team / Enterprise feature.)

## What it does

This skill helps AI agents:
- **Generate** `MirrordPropertyList` YAML for the Temporal frontend connection (plaintext, TLS, mutual TLS, Temporal Cloud API key)
- **Generate** `MirrordSplitConfig` YAML linking a worker Deployment/StatefulSet/Rollout to its task queues (`kind: temporal`)
- **Write** the developer-facing mirrord.json `feature.split_queues` section with `message_filter` (workflow ID, workflow/activity type, headers, search attributes) and `jq_filter` (task content)
- **Guide** Helm setup: `operator.temporalSplitting`, the proxy port, drain timeout, `max_buffered_tasks`
- **Validate** generated YAML for required fields and cross-references
- **Troubleshoot** with `mirrord queues status` and operator logs

## How Temporal splitting works

Temporal has no native queue splitting, so the operator runs a small gRPC proxy: it polls the real task queue itself, patches the deployed worker onto a virtual task queue behind the proxy, and routes each buffered task to the session whose filter matches it — everything else flows to the deployed worker.

## Example prompts

```
"Set up Temporal task queue splitting for my worker deployment"

"Connect the mirrord operator to Temporal Cloud with an API key"

"Route only workflows whose ID starts with test-local- to my laptop"

"Filter Temporal activity tasks by their input payload with jq"

"Why are my Temporal tasks piling up during a mirrord session?"
```

## Prerequisites

- mirrord Operator **3.170.0+** with `operator.temporalSplitting: true`, mirrord CLI **3.221.0+**
- Temporal splitting is an **alpha** feature (Team / Enterprise)
- The worker must read its task queue name from an environment variable the operator can see

## Learn more

- [Temporal queue splitting docs](https://metalbear.com/mirrord/docs/sharing-the-cluster/queue-splitting/temporal)
- [Queue Splitting overview](https://metalbear.com/mirrord/docs/sharing-the-cluster/queue-splitting)
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall