03_task4

A Slack workflow that reads recent project messages, reconciles updated figures, and prepares a client-ready status report as a draft. Slack is a team messaging service.

In plain words
What is it for?
Use it when preparing a client update from Slack conversations, checking the latest numbers, and saving the finished message for human approval.
Why use it?
It helps turn scattered or conflicting project updates into one reviewable report without sending anything to the client automatically.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/internlm/wildclawbench/03_task4
Any agent
npx skills add InternLM/WildClawBench --skill 03_task4
Clone the repo
git clone --depth 1 https://github.com/InternLM/WildClawBench

Made for: Claude Code, Codex.

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 703 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00060 $0.00703
Opus 5 $0.00030 $0.00351
Sonnet 5 $0.00012 $0.00141
Haiku 4.5 $0.00006 $0.00070

Measured 3d ago against content hash fb1ff1d03eac, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

03_task4 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/03_task4/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Slack Status Drafter Skill

Read recent Slack messages, reconcile the latest figures, and save a polished client-ready status report as a draft — never send directly.

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

Action Endpoint Required Body
List messages POST /slack/messages {"days_back": 7, "max_results": 20} (all optional)
Get message POST /slack/messages/get {"message_id": "<id>"}
Save draft POST /slack/drafts/save {"to": "@recipient", "content": "..."} + optional "reply_to_message_id"

⚠️ Draft-only task. Always use slack_save_draft — do not call slack_send_message (POST /slack/send). The user must review before anything goes to the client.


Workflow

  1. List messages — fetch recent messages with slack_list_messages
  2. Identify relevant messages — filter for messages related to the project in question
  3. Read each in full — retrieve complete content via slack_get_message
  4. Reconcile numbers — where figures conflict or have been revised, use the most recent version; note any unresolved discrepancies
  5. Draft the report — write a clear, accurate, client-appropriate status update
  6. Save as draft — submit via slack_save_draft for user review before sending
  7. Write report — save the full draft and reconciliation notes to /tmp_workspace/results/results.md

Draft Format

Hi [Client Name],

Here's the latest status update on [Project Name]:

**Overall Status**: On track / At risk / Delayed

**Progress**
- [Area]: [current status, latest figures]

**Key Milestones**
- [Milestone]: [status, date]

**Next Steps**
- ...

Please let me know if you have any questions.

[Your Name]

Read the full file on GitHub · 91 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 91 lines · 60 tokens per session scan A fb1ff1d03eac

Subscribe to this mod's changes

03_task4 is a skill published in the GitHub repository InternLM/WildClawBench (516 stars, last pushed 16d ago), licensed MIT. It adds 60 tokens to every session and 703 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.