diagnose

Name: diagnose
Availability: InStock
Author: kbanc

Diagnose Claudia memory system health and MCP tool connectivity.

283|44|Updated Jan 23, 2026

Search Tags:#troubleshoot #mcp #memory #diagnose #health #daemon

Ready to run

npx skills add https://github.com/kbanc85/claudia --skill diagnose-kbanc85

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/kbanc85/claudia/tree/main/template-v2/.claude/skills/diagnose
Command: npx skills add https://github.com/kbanc85/claudia --skill diagnose-kbanc85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

System health checks for Claudia's memory infrastructure. Run this when memory tools are unavailable, session context isn't loading, or memory-related issues are suspected.

Core Features & Use Cases

Verifies the availability of memory tools (MCP tools) and checks connectivity
Validates memory daemon status, platform compatibility, health endpoint responsiveness, and memory database integrity
Provides a guided remediation path and structured results for quick troubleshooting

Quick Start

Run this skill at session start when memory tools fail or context won't load to quickly assess the memory subsystem.

Frequently Asked Questions about diagnose

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

FAQPage Schema

How do I troubleshoot MCP memory tools when they become unavailable?▼

Troubleshoot MCP memory tools by running a diagnostic health check that verifies MCP tool availability, daemon process status, health endpoint responsiveness, and database integrity to pinpoint failures.

Why does my session context fail to load from the memory database?▼

Session context fails to load when the memory daemon is unhealthy or the database integrity is compromised. Run a diagnostic check to validate daemon status and database health for remediation steps.

How do I check the health of a memory daemon and its endpoint?▼

Check memory daemon health by validating the daemon process, testing the health endpoint's responsiveness, and verifying the memory database. The diagnostic outputs a structured report with remediation guidance.

What steps are involved in diagnosing memory persistence issues?▼

Diagnosing memory persistence issues involves a defined set of MCP tool checks, platform detection, daemon process validation, and health endpoint and database verifications, concluding with a formatted report and remediation steps.

Can I run memory health diagnostics across different platforms?▼

Yes, the diagnostic process includes platform detection to validate compatibility before checking MCP tool connectivity, daemon status, and health endpoints, ensuring accurate troubleshooting across different environments.