# Configure Temporal Queue Splitting with mirrord

Temporal workers need precise task routing during local debugging, but manual Kubernetes configuration is easy to misconfigure. This skill generates resource guidance, filters, validation checks, and troubleshooting steps for mirrord Temporal splitting.

## Install

```bash
npx skillstore add metalbear-co/mirrord-temporal
```

## Metadata

- Status: approved
- Slug: metalbear-co-mirrord-temporal
- Version: 1.2
- Author version: 1.2
- Skillstore revision: r1
- Version status: invalid
- Tree hash: 183a575ea156425185d3bbb74b4d76be23d7ea4c7eb14eadb02d50ebeab950ad
- Author: metalbear-co
- GitHub username: metalbear-co
- License: MIT
- Repository: https://github.com/metalbear-co/skills/tree/a0ad7ca50ffb241a1c4f9c6a05d17661d5d658a5/skills/mirrord-temporal
- Ref: bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/metalbear-co-mirrord-temporal
- Manifest: https://skillstore.pages.dev/api/skills/metalbear-co-mirrord-temporal/manifest

## Capabilities

- Generate MirrordPropertyList guidance for Temporal frontend connections.
- Generate MirrordSplitConfig guidance for Temporal worker workloads.
- Create message\_filter and jq\_filter examples for selected tasks.
- Explain Helm values, drain timeouts, and buffered task limits.
- Validate required fields, namespaces, references, and filter settings.
- Troubleshoot operator versions, queue status, and common routing issues.

## Use Cases

- Prepare a local worker session: Generate the resources and filters needed to route selected Temporal workflows or activities to a developer workstation.
- Configure a shared cluster: Plan operator settings, workload references, namespaces, secrets, and queue limits for a controlled team environment.
- Diagnose task routing: Review versions, filters, environment sources, buffering, TLS settings, and queue status when a split behaves unexpectedly.

## Prompt Templates

### Start a basic split

```
Set up Temporal task queue splitting for my worker. Ask only for the required workload, namespace, queue, and frontend details.
```

### Use a workflow filter

```
Route only Temporal workflows whose IDs start with test-local- to my local worker. Explain the filter and required resource references.
```

### Connect Temporal Cloud

```
Configure Temporal Cloud with TLS and a Kubernetes Secret for the API key. Check namespaces, versions, and secret references before presenting the resources.
```

### Diagnose advanced routing

```
Review this Temporal splitting design for filter overlap, jq payload matching, task buffering, drain behavior, TLS configuration, and operator compatibility. Identify risks and propose corrected resources.
```

## Limitations

- It does not apply Kubernetes resources or install Helm releases.
- It cannot verify cluster state without authorized kubectl access.
- It supports an alpha Team or Enterprise mirrord feature.
- It cannot recover work lost through immediate teardown or invalid filters.

## Best Practices

- Use Kubernetes Secret references for API keys and certificate material.
- Test filters and generated resources in a non-production namespace first.
- Review task ownership, buffering limits, drain behavior, and operator versions before starting a session.

## Anti Patterns

- Do not place API keys, certificates, or private keys directly in generated YAML.
- Do not use mirror mode or Kafka fields in a Temporal queue configuration.
- Do not apply cluster changes automatically without explicit review and authorization.

## Security Audit

- Audited at: 2026-09-29T22:08:36.088\+00:00
- Summary: The static matches are mostly false positives caused by Markdown backticks, shell examples, placeholder certificate names, and secret-reference documentation. The skill still presents operational risk because it permits broad cluster discovery and mentions agent-directed operator installation, which require explicit authorization and least-privilege controls.

## Stats

- Views: 0
- Downloads: 4
- Favorites: 0
- Popularity score: 0