skills.rest
villadalmine
villadalmineCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ai-stack-analyzer

Diagnose AI agent stack outages and message-routing failures across Hermes, OpenClaw, LiteLLM, and Honcho.

1|Updated Apr 3, 2026
Search Tags:#troubleshooting#logs#ai#kubernetes#openclaw#hermes#litellm
One-click install
npx skills add https://github.com/villadalmine/infra --skill ai-stack-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-stack-analyzer
Source: https://github.com/villadalmine/infra/tree/main/.agents/skills/ai-stack-analyzer
Command: npx skills add https://github.com/villadalmine/infra --skill ai-stack-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps resolve AI agent stack failures that cause bots to stall, drop messages, or return 403 and 429 errors across the cluster.

Core Features & Use Cases

  • Proxy Health Checks: Verifies LiteLLM status and inspects logs for rate-limit, quota, and provider issues.
  • Agent Debugging: Checks Hermes processing flow to find retry loops, timeouts, or message delivery failures.
  • Gateway and Memory Validation: Confirms OpenClaw Telegram connectivity, MCP bridge readiness, and Honcho persistence when memory or routing breaks.

Quick Start

Ask the skill to diagnose the AI stack by checking LiteLLM, Hermes, OpenClaw, and Honcho for routing, rate-limit, token, and persistence issues.

Frequently Asked Questions about ai-stack-analyzer

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

FAQPage Schema
Why does my Hermes AI agent stop responding or drop messages?▼

LiteLLM proxy issues like rate-limit, quota, and provider conflicts cause 403 and 429 errors that break AI agent routing. This Skill verifies LiteLLM status and inspects logs to isolate proxy health problems.

How do I troubleshoot OpenClaw Telegram bot connectivity and routing failures?▼

Honcho memory persistence failures cause routing breaks and lost context in AI stacks. This Skill validates Honcho persistence to isolate whether memory issues are the root cause of agent outages.

How do I diagnose Kubernetes pod health for an AI agent stack outage?▼

Yes, you can diagnose the full AI stack by checking LiteLLM, Hermes, OpenClaw, and Honcho together for routing, rate-limit, token, and persistence issues to isolate the root cause of outages.

Does this approach work for isolating token conflicts between Telegram bots?▼

Yes, isolating Telegram token separation conflicts is a core diagnostic step. This Skill checks Telegram token separation within OpenClaw to ensure bot tokens are not overlapping or misconfigured.

Related Skills

Explore More Software Engineering Skills→
openshiftopenshift
71

pod-failure-diagnosis

Classify Kubernetes pod failure modes and output remediation commands.

Official
Intermediate
DevMHOneDevMHOne

omni-budget

Configure spending limits, token quotas, and rate-limit policies across API providers.

Community
Advanced
oci-ai-incubationsoci-ai-incubations
3

monitoring-deployment

Monitor Kubernetes cluster health and readiness across all namespaces every 30 seconds.

Official
Advanced
RHEcosystemAppEngRHEcosystemAppEng
48

debug-inference

Diagnose OpenShift AI InferenceService deployment issues via pod logs and GPU health.

Official
Advanced