debug-renfield

Diagnose Renfield runtime failures across intents, WebSocket, voice, Home Assistant, satellites, and MCP servers.

34|5|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/ebongard/renfield --skill debug-renfield
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-renfield
Source: https://github.com/ebongard/renfield/tree/main/.claude/skills/debug-renfield
Command: npx skills add https://github.com/ebongard/renfield --skill debug-renfield

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured troubleshooting guide to identify and resolve common Renfield failures such as incorrect intent classification, WebSocket connectivity errors, voice/STT/TTS problems, Home Assistant integration faults, satellite discovery issues, and MCP server connection failures.

Core Features & Use Cases

  • Intent diagnostics: Validate intent extraction and ranked intents, and refresh Home Assistant keywords to improve accuracy.
  • Connectivity and logs: Inspect backend and Ollama logs, verify WebSocket/CORS configuration, and diagnose Docker service issues for satellites and MCP servers.
  • Operational fixes: Re-embed vectors after model changes, check Prometheus metrics, and follow hardware and configuration checks for ReSpeaker and zeroconf problems.

Quick Start

Ask the assistant to run an intent test and collect backend logs to pinpoint WebSocket, satellite, or intent-recognition issues.

Frequently Asked Questions about debug-renfield

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

FAQPage Schema
How do I troubleshoot incorrect intent recognition in my Renfield deployment?

To troubleshoot incorrect intent recognition, validate ranked intent extraction and refresh Home Assistant keywords to improve accuracy. You can trigger an intent test and inspect backend logs to pinpoint specific classification failures.

Why does my WebSocket connection fail during Renfield satellite discovery?

WebSocket connection failures during satellite discovery often stem from backend configuration issues. Inspect Docker service logs, verify WebSocket and CORS configuration, and check zeroconf settings to diagnose and resolve broken satellite connections.

What do I need to diagnose Renfield runtime failures in a local Docker environment?

Diagnosing Renfield runtime failures in a Docker environment requires access to debug endpoints, Docker log inspection, Ollama CLI access, and permissions to trigger re-embedding and keyword refresh operations for accurate fault isolation.

How do I fix Home Assistant integration faults and voice input problems?

Fix Home Assistant integration faults and voice issues by inspecting backend logs for TTS and STT errors. Verify Home Assistant keyword synchronization and check hardware configurations like ReSpeaker to resolve voice input failures.

What is the best way to resolve MCP server connection issues in Renfield?

The best way to resolve MCP server connection issues is to inspect Docker service logs and verify backend connectivity. Check Prometheus metrics and run configuration checks to isolate the failing server components.

When should I re-embed vectors after changing Ollama models in Renfield?

You should re-embed vectors immediately after changing Ollama models to prevent intent recognition degradation. Use the Ollama CLI to verify the model switch, then trigger the re-embedding operation through the admin endpoints.