agentleFS
Sign inStart free
OpenBMBOpenBMB/EC2-Bench/skills/task19/SKILL.md

task19

Skill19 starsChanged 5 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 8
  2. Very specific:

    All tools are defined in tmp_workspace/utils.py:

    line 12
  3. Distinctive:

    Read-only — do not send any messages

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free