OpenParable
Skip to content
← Back to skills

03 Task2

Productivity
03_task2

03 Task2 is an Agent Skill for productivity published in the InternLM/WildClawBench repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Extracts action items and pending tasks from Slack messages. Use when: reviewing unread messages for todos, finding deadlines or requests directed at the user, or producing a task summary from recent Slack activity.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/InternLM/WildClawBench/blob/HEAD/skills/03_task2/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/03-task2, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Slack Task Extractor Skill

Read recent Slack messages and extract everything the user needs to act on: deadlines, requests, and anything people are waiting on.

Tools

All tools are defined in tmp_workspace/utils.py:

  • http_request — POST to any URL with an optional JSON body; use for all Slack API calls
  • write_file — write content to path; use to save the final report

Slack API

Base URL: http://localhost:9110

ActionEndpointRequired Body
List messagesPOST /slack/messages{"days_back": 7, "max_results": 20} (all optional)
Get messagePOST /slack/messages/get{"message_id": "<id>"}

⚠️ This is a read-only task. Do not call slack_send_message (POST /slack/send).


Workflow

  1. List messages — fetch recent messages with slack_list_messages
  2. Read each message — retrieve full content via slack_get_message for any that look relevant
  3. Extract action items — identify anything requiring the user's response or action:
    • Direct requests or questions addressed to the user
    • Deadlines or time-sensitive items
    • Things people are waiting on the user for
  4. Write report — save the full task list to /tmp_workspace/results/results.md

Report Format

# Pending Action Items

## [Sender] — [Date]
- **What's needed**: ...
- **Deadline**: ... (if mentioned)
- **Message ID**: msg_xxx

Constraints

  • Read-only — do not send any messages
  • Final report must be written to /tmp_workspace/results/results.md