debugging-hermes-tui-commands

Debug slash command registration, autocomplete and execution mismatches across Hermes TUI layers.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/kngender5/hermes --skill debugging-hermes-tui-commands-kngender5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-hermes-tui-commands
Source: https://github.com/kngender5/hermes/tree/main/skills/software-development/debugging-hermes-tui-commands
Command: npx skills add https://github.com/kngender5/hermes --skill debugging-hermes-tui-commands-kngender5

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users identify and resolve issues with slash commands in the Hermes TUI, ensuring commands work consistently across different layers of the system.

Core Features & Use Cases

  • Command Registration Check: Ensures commands are properly registered in both Python and TypeScript.
  • Autocomplete and Execution Verification: Verifies that commands show in autocomplete and execute correctly in the TUI.
  • Configuration and Live State Management: Helps manage command configurations and live UI states.
  • Use Case: When a slash command is missing from autocomplete or behaves differently in the TUI compared to the CLI.

Quick Start

Use the debugging-hermes-tui-commands skill to investigate why the 'commandname' slash command is not showing in autocomplete suggestions.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
Why is my slash command not showing in autocomplete in the TUI?

Slash commands missing from autocomplete often indicate a registration discrepancy. You must verify command registration across both the Python backend and the TypeScript frontend to ensure proper synchronization.

How do I debug slash commands that behave differently in the TUI compared to the CLI?

To debug slash command discrepancies between the TUI and CLI, verify command execution paths across multiple system layers. Check the TUI gateway configuration and live UI states to identify where the execution diverges.

How does command registration work across Python and TypeScript in a multi-layer architecture?

Command registration requires syncing definitions between the Python backend and the Ink/TypeScript frontend. A slash command must be properly registered in both layers to ensure it appears in autocomplete and executes correctly in the TUI.

What is the best way to verify slash command execution across a TUI gateway?

The best way to verify slash command execution is to trace the command through the TUI gateway, checking configuration and live UI states. This ensures the command passes correctly from the Python backend to the frontend.

Can I use this approach to fix slash commands that execute incorrectly in the TUI?

Yes, this approach resolves slash commands that execute incorrectly by analyzing multiple layers. It identifies and fixes issues within the Python backend, TUI gateway, and TypeScript frontend to ensure consistent execution.