omh-agent-debug

# Agent Debug This is a Hermes-native `agent-debug` workflow skill. ## Why This Exists `agent-debug` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration. ## Do Not Use When - The request is already handled by a narrower explicit skill with stronger evidence. - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. ## Examples Good example: - Prompt: agent-debug capture why this agent is looping on the same tool and prepare the smallest safe recovery action. - Expected behavior: Produce `prepare_agent_debug` with required context, wrapper actions, and not-evidence boundaries. - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. Bad example: - Prompt: agent-debug silently reset the executor, patch the environment, and claim the future loop is fixed. - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. ## Completion Checklist - Failure state, intended goal, recent tool sequence, and context pressure are captured. - Diagnosis distinguishes repeated command/tool loops, context drift, environment mismat...