slack-to-queue

Ingest Slack messages into a project queue to create projects or rounds.

8|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/eranto/understudy --skill slack-to-queue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack-to-queue
Source: https://github.com/eranto/understudy/tree/main/skills/slack-to-queue
Command: npx skills add https://github.com/eranto/understudy --skill slack-to-queue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ingest Slack activity from a dedicated channel into the project queue and create either new projects or rounds within existing projects, enabling you to automate intake and keep work organized.

Core Features & Use Cases

  • Two intake modes: post a top-level message in the channel to create a NEW project, or post a thread reply to add a NEW ROUND to an existing project summary.
  • Dedup and ownership checks: only your messages authored by your Slack user ID are ingested, and duplicates (marked with the ✅ reaction) are ignored.
  • Attachment handling and provenance: attachments can be noted for inclusion, and each ingested item includes provenance for traceability.
  • Environment-driven queue root: uses QUEUE_ROOT and helper scripts like create_queue_item.py to materialize new projects.

Quick Start

Post a top-level Slack message in your Slack channel to create a new project in the queue.

Frequently Asked Questions about slack-to-queue

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

FAQPage Schema
How do I automate Slack project intake into a project management queue?

To automate Slack intake, post top-level messages in a dedicated channel to create new projects, or reply to threads to add rounds. The system ingests your messages, checks for duplicates via the ✅ reaction, and uses helper scripts to materialize queue items.

How does Slack to queue deduplication work for ingested messages?

Deduplication for Slack queue ingestion works by checking for the ✅ reaction on messages. Messages with this reaction are ignored, ensuring only new, unprocessed Slack activity is turned into queued project work, preventing duplicate projects or rounds.

Do I need a specific Slack channel ID to automate message ingestion into a project queue?

Yes, a specific Slack channel ID is required to target the right messages. You also need a configured QUEUE_ROOT environment variable and helper scripts like create_queue_item.py to successfully ingest Slack activity and write queue instructions.

Can I add a new round to an existing project from a Slack thread reply?

Yes, you can add new rounds to existing projects by posting a thread reply in the Slack channel. The system ingests thread replies as new rounds within the existing project summary, keeping project updates organized and automated.

What are the limitations of ingesting Slack attachments into a project queue?

The main limitation is strict author ownership: only messages authored by your specific Slack user ID are ingested. Attachments are noted for inclusion and provenance is added, but messages from other users in the channel are ignored to ensure correct ownership.