debug

Diagnose Luke issues by collecting logs, inspecting environment, and validating connectivity.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/fpl0/luke --skill debug-fpl0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/fpl0/luke/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/fpl0/luke --skill debug-fpl0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug Luke issues. Use when things aren't working, Telegram not connecting, agent not responding, memory problems, or to understand how the system works. Covers logs, environment, common issues.

Core Features & Use Cases

  • Diagnostic workflow to collect and inspect logs from standard locations (luke.log, luke.err, luke.db)
  • Environment validation and service health checks to identify misconfigurations
  • Guided troubleshooting steps for common failures (connectivity, authentication, memory indexing)

Quick Start

Run the built-in debug workflow to collect logs, inspect environment variables, and review the Luke service status.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug Telegram connectivity problems with an AI agent?

To debug Telegram connectivity problems, you inspect agent environment variables and review luke.log for service errors. This diagnostic workflow validates connectivity and identifies misconfigurations preventing the AI agent from responding.

Why is my AI agent not responding and how do I check the logs?

Your AI agent may not be responding due to startup failures or connectivity issues. You can check luke.log, luke.err, and luke.db files in your LUKE_DIR directory to surface actionable checks and diagnose service health.

What is the best way to troubleshoot memory indexing issues in my agent?

The best way to troubleshoot memory indexing issues is to run a diagnostic workflow that validates the service environment and inspects luke.db. This helps identify memory problems by examining the running service and database logs.

Can I run diagnostics for agent startup failures on macOS?

Yes, you can run diagnostics for agent startup failures on macOS. The troubleshooting workflow collects logs from standard locations and performs environment validation to identify misconfigurations causing the startup failure.

What environment variables do I need to check when troubleshooting agent connectivity?

When troubleshooting agent connectivity, you need to check environment variables within your LUKE_DIR configuration. Validating these variables against the running service helps identify authentication and network misconfigurations.