diagnostico-agentes-mudos-slack

Diagnoses why Hermes Slack agents are not responding and isolates the root cause.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill diagnostico-agentes-mudos-slack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostico-agentes-mudos-slack
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/skills/diagnostico-agentes-mudos-slack
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill diagnostico-agentes-mudos-slack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose why Hermes agents stop responding in Slack, separating real connectivity failures from token, configuration, mention-filter, and channel-delivery issues.

Core Features & Use Cases

  • Gateway Health Checks: Verify whether the agent process, launchctl service, and Slack Socket Mode connection are actually running.
  • Token and Identity Validation: Confirm bot identity with Slack auth.test and detect app token failures that cause zero inbound messages.
  • Log-Based Root Cause Analysis: Interpret gateway.log, agent.log, out.log, err.log, and state files to distinguish zombie processes, invalid_auth, DNS/timeouts, and mention-filter mistakes.
  • Use Case: An operator notices an agent is silent in #operacao and uses this Skill to determine whether the fix is a restart, a new app token, a config correction, or a Slack workspace/dashboard change.

Quick Start

Ask the agent to diagnose the Hermes Slack profile, inspect the relevant logs and config, validate the Slack bot identity, and tell you the most likely root cause and next repair step.

Frequently Asked Questions about diagnostico-agentes-mudos-slack

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

FAQPage Schema
Why is my Slack bot connected but not receiving any inbound messages?

Slack bots may appear connected but receive no inbound messages due to invalid app tokens, Socket Mode delivery failures, or mention-filter mistakes. Diagnosing the issue requires validating bot_token and app_token behavior alongside reviewing gateway and agent logs.

How do I diagnose a silent Hermes Slack agent on macOS?

To diagnose a silent Hermes Slack agent on macOS, verify process health and launchctl service status, inspect gateway.log and agent.log, and run Slack auth.test to confirm bot identity and isolate whether the root cause is a zombie process or a configuration error.

What is the best way to troubleshoot Slack Socket Mode connectivity issues?

Troubleshooting Slack Socket Mode connectivity involves checking gateway health, reviewing out.log and err.log for DNS or timeout errors, and interpreting state files to distinguish real connectivity failures from token identity issues.

Does this troubleshooting process work for remote Hermes profiles?

Yes, this troubleshooting process applies to remote Hermes profiles as well as macOS, validating bot identity, interpreting launchctl and state files, and reviewing Slack API signals to isolate root causes across different deployment environments.

How can I tell if my Slack agent is a zombie process?

You can detect a zombie process by reviewing gateway.log and agent.log alongside launchctl service status, checking if the agent process is running while failing to deliver inbound Slack events through Socket Mode.

What Slack API signals indicate an invalid auth token?

Invalid auth tokens typically surface as invalid_auth errors in agent logs, causing zero inbound messages, which you can confirm by running Slack auth.test to validate bot identity and detect app token failures.