03_task2

Extract action items and deadlines from Slack messages into a markdown report.

1|Updated May 20, 2026
One-click install
npx skills add https://github.com/Wanli-Lee/CUA-Claw-Harness --skill 03-task2-wanli-lee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 03_task2
Source: https://github.com/Wanli-Lee/CUA-Claw-Harness/tree/main/skills/03_task2
Command: npx skills add https://github.com/Wanli-Lee/CUA-Claw-Harness --skill 03-task2-wanli-lee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents you from missing important requests and deadlines hidden across recent Slack messages by turning unread chatter into a structured to-do list.

Core Features & Use Cases

  • Action-item extraction: Identifies direct requests, questions addressed to you, and anything that is waiting on your response.
  • Deadline detection: Pulls out time-sensitive items such as due dates mentioned in messages.
  • Slack activity summarization: Produces a consolidated report from recent Slack history you can immediately act on.
  • Use case: After returning from a break, you can summarize the last week of Slack activity into pending items with senders, dates, deadlines, and message IDs.

Quick Start

Use the 03_task2 skill to scan your last 7 days of Slack messages and write a report of pending action items to /tmp_workspace/results/results.md.

Frequently Asked Questions about 03_task2

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

FAQPage Schema
How do I extract action items from Slack messages automatically?

Extracting action items from Slack messages is done by scanning recent unread activity via the local Slack API, identifying requests addressed to you, and compiling a consolidated markdown report with senders, dates, deadlines, and message IDs.

Can I summarize Slack threads into a to-do list after returning from vacation?

Summarizing Slack threads into a to-do list is supported by scanning your last 7 days of unread messages, detecting pending requests and deadlines, and compiling them into a structured actionable report.

Do I need read-only Slack API access to detect deadlines in messages?

Read-only Slack API access is required to detect deadlines, as the Skill uses message listing and per-message retrieval over the local Slack API to identify time-sensitive items and pending requests.

What is the best way to pull pending tasks from Slack history into a markdown file?

Pulling pending tasks from Slack history into a markdown file is achieved by scanning unread messages, extracting action items with deadlines and senders, and writing the final report to /tmp_workspace/results/results.md.