Explain Hermes Agent architecture, memory stores, skills layout, cron scheduler behavior, and tool discovery.
npx skills add https://github.com/zot24/skills --skill hermes-zot24
Please help me install this Agent Skill. Skill: hermes Source: https://github.com/zot24/skills/tree/main/skills/hermes/skills/hermes Command: npx skills add https://github.com/zot24/skills --skill hermes-zot24
Helps developers and operators understand, configure, and troubleshoot the Hermes Agent so it runs reliably across CLI, gateway, and scheduled (cron) contexts. It converts scattered implementation details—memory layout, skill authoring rules, tool discovery, and scheduler behavior—into actionable guidance so issues are diagnosed and fixed faster.
Ask the hermes skill to explain why a cron job did not run and what files, scheduler settings, and gateway processes to inspect.
High-intent search queries and answers about installing and using this skill.
Hermes cron jobs fail when scheduler tick behavior, delivery targets, or job storage configurations are incorrect. Inspecting scheduler settings, gateway processes, and provider fallbacks helps diagnose missed ticks and verify scheduled execution across CLI and gateway contexts.
Hermes uses a dual-store memory model separating memory and user data, with files stored in specific locations. Honcho integration persists user profiles, requiring correct file paths and store configurations to ensure reliable agent memory across CLI and gateway sessions.
Hermes discovers tools and MCP servers through a registry system that filters availability based on session context. Tool registry semantics determine which tools appear in CLI versus gateway runs, affecting tool access for different execution environments.
Hermes skills require a specific SKILL.md structure and must be placed in designated loading locations where they auto-register as slash commands. Following skill authoring rules ensures proper registration and availability across agent sessions.
Tool unavailability in Hermes gateway sessions stems from tool discovery and filtering rules within the registry. Auditing tool registry semantics and provider availability across CLI and gateway runs identifies why specific tools are excluded from active sessions.
Common Hermes scheduler failure modes include missed ticks and provider fallback errors. Debugging requires inspecting scheduler tick expectations, job storage files, delivery targets, and running recommended diagnostic commands to trace execution failures.
quiznatConfigure Hermes Agent CLI setup, providers, models, and tools.
huidgeDiagnose cron job failures by analyzing status, logs, and gateway errors.
plastic-labsIntegrate Honcho memory and social cognition into Python or TypeScript projects.
lenadlmManually trigger stuck cron jobs and reset Hermes Agent scheduler state.
