skills.rest
X-McKay
X-McKayCOMMUNITY
Explore all skills by this author →
GitHub

check-workflow-health

Detects operational problems in Temporal deployments by analyzing worker statuses and connectivity metrics.

3|Updated Dec 2, 2025
Search Tags:#workflow#monitoring#kubernetes#health check#temporal#diagnostic
One-click install
npx skills add https://github.com/X-McKay/kubani --skill check-workflow-health
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-workflow-health
Source: https://github.com/X-McKay/kubani/tree/main/kubani/skills/k8s/diagnostic/check-workflow-health
Command: npx skills add https://github.com/X-McKay/kubani --skill check-workflow-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill proactively monitors the health of your Temporal workflow orchestration, ensuring that your background jobs and complex processes are running smoothly and without errors.

Core Features & Use Cases

  • Temporal Pod Status: Verifies that all essential Temporal server components are operational.
  • Worker Connectivity: Checks if your application workers are successfully connected to the Temporal cluster.
  • Error Detection: Scans logs and events for signs of workflow failures or stuck processes.
  • Use Case: If your AI agents rely on Temporal for task management, this skill will alert you if the Temporal cluster experiences issues, preventing cascading failures in your AI system.

Quick Start

Use the check-workflow-health skill to verify the status of your Temporal deployment.

Frequently Asked Questions about check-workflow-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Temporal workflow health in a Kubernetes cluster?▼

Checking Temporal workflow health involves verifying the operational status of Temporal server and worker pods, and analyzing logs for errors. This diagnostic process ensures your orchestration services are running reliably without stuck processes.

Why does my Temporal workflow orchestration experience cascading failures?▼

Cascading failures in Temporal workflow orchestration often occur when essential server components are down or application workers lose connectivity. Proactively monitoring pod statuses and scanning logs for errors prevents these workflow failures.

Can I monitor worker connectivity to the Temporal cluster using Kubernetes events?▼

Yes, you can monitor worker connectivity by retrieving pod and event data through the Kubernetes API. This requires an mcp-server connection to access the Kubernetes API for verifying if application workers are successfully connected.

What is the best way to detect stuck Temporal processes in a Kubernetes environment?▼

The best way to detect stuck Temporal processes is by scanning logs and Kubernetes events for signs of workflow failures. This diagnostic approach identifies operational issues within your Temporal server and worker pods.

Do I need mcp-server to diagnose Temporal server pod statuses?▼

Yes, you need mcp-server to diagnose Temporal server pod statuses because it provides access to the Kubernetes API. This access is required for retrieving essential pod and event data for health monitoring.

Related Skills

Explore More Software Engineering Skills→
X-McKayX-McKay
3

investigate-pod-failure

Retrieve Kubernetes pod status, logs, and events to diagnose failures.

Community
Intermediate
X-McKayX-McKay
3

restart-crashloop

Restart Kubernetes pods in CrashLoopBackOff after verifying status and OOMKilled events.

Community
Intermediate
ionfuryionfury
24

loki

Query Loki endpoints to analyze Kubernetes logs and troubleshoot cluster issues.

Community
Intermediate
eveldeveld
10

k8s-query

Query Kubernetes resources to determine cluster state and resource health.

Community
Intermediate