mirrord-chaos
78Test Mirrord Sessions Under Chaos
Teams need realistic failure tests without changing shared workloads or application code. This skill creates session-scoped mirrord rules for latency and connection failures in local and CI tests.
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.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "mirrord-temporal" from https://skillstore.io/skills/metalbear-co-mirrord-temporal.md and its manifest at https://skillstore.io/api/skills/metalbear-co-mirrord-temporal/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "mirrord-temporal". Route workflows beginning with test-local- to my laptop.
Expected outcome:
A review-ready split configuration plan with a Temporal queue filter on workflow ID, a matching local target, namespace checks, and a warning that matching tasks are stolen from the deployed worker.
Using "mirrord-temporal". Connect my self-hosted Temporal frontend with private CA and mTLS.
Expected outcome:
A secret-backed connection plan requiring the CA certificate, client certificate, and client key together. It explains that TLS protects the operator connection to the frontend.
Using "mirrord-temporal". Tasks accumulate while I debug at a breakpoint.
Expected outcome:
A troubleshooting checklist covering max buffered tasks, filter overlap, drain timeout, worker visibility, and the operator and CLI version requirements.
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.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/metalbear-co-mirrord-temporal/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/metalbear-co-mirrord-temporal?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/metalbear-co-mirrord-temporal?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/metalbear-co-mirrord-temporal/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/metalbear-co-mirrord-temporal.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>metalbear-co. (2026). mirrord-temporal security audit report (audit version 1) [Author version 1.2]. Skillstore. https://skillstore.io/skills/metalbear-co-mirrord-temporal/audits/1@techreport{metalbear-co-metalbear-co-mirrord-temporal-2026,
author = {metalbear-co},
title = {mirrord-temporal security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/metalbear-co-mirrord-temporal/audits/1},
note = {Author version 1.2}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "mirrord-temporal security audit report (audit version 1)"
version: "1.2"
type: report
authors:
- name: "metalbear-co"
date-released: "2026-09-29"
url: "https://skillstore.io/skills/metalbear-co-mirrord-temporal/audits/1"
identifiers:
- type: other
value: "skillstore:metalbear-co-mirrord-temporal:audit:1"
description: "Skillstore immutable audit report identifier"
Generate the resources and filters needed to route selected Temporal workflows or activities to a developer workstation.
Plan operator settings, workload references, namespaces, secrets, and queue limits for a controlled team environment.
Review versions, filters, environment sources, buffering, TLS settings, and queue status when a split behaves unexpectedly.
Set up Temporal task queue splitting for my worker. Ask only for the required workload, namespace, queue, and frontend details.
Route only Temporal workflows whose IDs start with test-local- to my local worker. Explain the filter and required resource references.
Configure Temporal Cloud with TLS and a Kubernetes Secret for the API key. Check namespaces, versions, and secret references before presenting the resources.
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.
Author
metalbear-coLicense
MIT
Author version
v1.2
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Ref
bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
Maintenance freshness
9/30/2026
Usage
0 downloads ยท 0 views
File structure
Test Mirrord Sessions Under Chaos
Teams need realistic failure tests without changing shared workloads or application code. This skill creates session-scoped mirrord rules for latency and connection failures in local and CI tests.
Debug Multiple Microservices with mirrord up
Debugging related microservices requires coordinating local processes, cluster targets, and traffic filters. This skill guides shared YAML configuration and concurrent mirrord session management.
Build Safer mirrord Configurations
Kubernetes configuration files can be difficult to write and easy to misconfigure. This skill creates, validates, and explains focused mirrord configurations.
Start Your First mirrord Kubernetes Session
Starting local development against Kubernetes requires working cluster access, suitable tooling, and a target pod. This skill guides installation, first-session setup, and connection verification.
Configure mirrord Operator for Kubernetes Teams
Team deployments require coordinated licensing, Kubernetes permissions, and feature configuration. This skill guides mirrord Operator setup and troubleshooting with Helm references and approval checkpoints.
Configure Isolated Database Branches with mirrord
Shared databases make migration testing and development experiments difficult to isolate. This skill helps configure mirrord branches with separate connections, controlled data copying, and validation guidance.
Coordinate Cloud DevOps Workflows
by sickn33
Cloud delivery work often spans many tools and phases. This skill organizes infrastructure, CI/CD, Kubernetes, monitoring, security, costs, and recovery work into clear prompts.
Design Production Helm Chart Architecture
by 92Bilal26
Teams often copy Helm examples that do not match their operational constraints. This skill guides chart architecture through dependencies, hooks, values, environments, and operator needs.
Deploy Kubernetes Workloads With Guided Steps
by sickn33
Kubernetes releases require many coordinated artifacts and checks. This skill guides container preparation, manifests, Helm charts, service mesh, security, observability, and deployment validation.
Generate Kubernetes Manifests Safely
by sickn33
Kubernetes manifests are easy to misconfigure when teams write them from memory. This skill turns requirements into structured YAML guidance with security, probes, resources, and service patterns.
Troubleshoot DevOps Incidents Systematically
by sickn33
Complex incidents often produce scattered signals across applications, infrastructure, and cloud services. This skill organizes evidence, tests hypotheses, and recommends immediate and preventive actions.
Deploy Guts Node Infrastructure
by AbdelStark
Deploying Guts nodes requires consistent Terraform, Docker, and Kubernetes patterns. This skill provides reusable infrastructure examples for local, test, and production environments.