slack-cronjob-delivery-debug

Name: slack-cronjob-delivery-debug
Availability: InStock
Author: shiftrepo

Diagnose Slack channel_not_found errors in Hermes cron jobs and implement send_message workarounds.

Updated Aug 27, 2026

Search Tags:#automation #workflow #debugging #slack #delivery #cron #send_message

Ready to run

npx skills add https://github.com/shiftrepo/aws --skill slack-cronjob-delivery-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slack-cronjob-delivery-debug
Source: https://github.com/shiftrepo/aws/tree/main/HermesAgent/skills/skills/devops/slack-cronjob-delivery-debug
Command: npx skills add https://github.com/shiftrepo/aws --skill slack-cronjob-delivery-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slack cron job deliveries can fail with channel_not_found or thread_id resolution errors even when the main gateway functions correctly. This skill captures the diagnosis and practical fixes to ensure cron-initiated Slack messages reach their targets reliably.

Core Features & Use Cases

Diagnose Slack delivery failures in Hermes cron workflows by inspecting error logs and cron prompts.
Apply a proven workaround that uses an explicit send_message call inside the cron prompt to guarantee delivery to thread- scoped targets.
Align cron delivery behavior with gateway delivery, and provide guidance for keeping both subsystems in sync during troubleshooting.

Quick Start

Inspect the cron delivery logs for channel_not_found errors, verify valid thread targets with send_message, and update the cron prompt to invoke send_message directly for reliable Slack delivery.

Frequently Asked Questions about slack-cronjob-delivery-debug

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

FAQPage Schema

Why do my Slack cron job deliveries fail with channel_not_found errors?▼

Slack cron job deliveries fail with channel_not_found errors when the separate cron client path cannot resolve the target channel. Diagnosing the delivery logs and validating targets ensures messages reach the intended destination.

How do I fix thread_id resolution issues in Slack cron workflows?▼

To fix thread_id resolution issues in Slack cron workflows, apply a workaround that invokes an explicit send_message call directly inside the cron prompt to guarantee delivery to thread-scoped targets.

How do I validate Slack delivery targets before running a cron job?▼

Validate Slack delivery targets by running send_message with the action parameter set to list. This verifies valid thread targets and confirms channel accessibility before executing the cron prompt.

How does Slack delivery behavior differ between cron jobs and the main gateway?▼

Slack delivery behavior differs because cron jobs use a separate client path that can fail on target resolution, while the main gateway functions correctly. Keeping both subsystems in sync during troubleshooting is essential.

What is the best way to automate reliable Slack messaging in Hermes cron jobs?▼

The best way to automate reliable Slack messaging in Hermes cron jobs is implementing a prompt-based solution that calls send_message directly, bypassing the separate client path to ensure messages reach intended channels.