InternLMInternLM/WildClawBench/skills/03_task5/SKILL.md

03_task5

Skill534 starsChanged 6 months agoMITView on GitHub

Triages a support inbox, prioritizes urgent issues, routes each to the right internal team member, and drafts any customer-facing replies for review. Use when: catching up on a backlog of support messages, producing an escalation report, or routing issues to appropriate owners.

In this repository26 other files it gives its agents.
- 03_task1Skill
- 03_task2Skill
- 03_task3Skill
- 03_task4Skill
- 03_task6Skill
- agentic-paper-digest-skillSkill
- arxiv-summarizer-orchestratorSkill
- calendar-remindersSkill
- ArchitectureSkill
- arxiv-agentic-verifierSkill
- geepers-dataSkill
- agenticmailSkill
- ai-meeting-schedulingSkill
- meeting-to-actionSkill
- academic-literature-searchSkill
- ddgs-searchSkill
- cross-validated-searchSkill
- video-watcherSkill
- eachlabs-voice-audioSkill
- loopwindSkill
- aegis-shieldSkill
- canarySkill
- skill-trust-auditorSkill
- agent-browserSkill
- self-improvementSkill
- video-framesSkill

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

Distinctive:
Read support messages, assess urgency, look up contacts to route issues internally, draft any customer replies for review, and produce an …
line 8
Very specific:
All tools are defined in tmp_workspace/utils.py:
line 12
Distinctive:
Use the Contacts API to identify whether a sender is a customer or internal team member, and to find the right internal owner to route each …
line 43

≈ “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 Support Triage Skill

Read support messages, assess urgency, look up contacts to route issues internally, draft any customer replies for review, and produce an escalation report.

Tools

All tools are defined in tmp_workspace/utils.py:

http_request — POST/GET to any URL with an optional JSON body; use for all 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>"}`
Send message	`POST /slack/send`	`{"to": "@user", "content": "..."}` — internal team only
Save draft	`POST /slack/drafts/save`	`{"to": "@user", "content": "..."}`

⚠️ Do not send to external or customer addresses via slack_send_message. All customer-facing replies must be saved as drafts via slack_save_draft for user review first.

Contacts API

Base URL: http://localhost:9103

Action	Endpoint	Required Body
Search contacts	`POST /contacts/search`	`{"query": "keyword"}`
Get contact	`POST /contacts/get`	`{"contact_id": "CT-501"}`

Use the Contacts API to identify whether a sender is a customer or internal team member, and to find the right internal owner to route each issue to.

Workflow

List messages — fetch recent messages with slack_list_messages
Read each in full — retrieve complete content via slack_get_message
Classify sender — use contacts_search / contacts_get to determine if internal or external/customer
Assess urgency — flag as Critical / High / Medium / Low based on impact and time-sensitivity
Route internally — identify the right team member for each issue; send routing notes via slack_send_message (internal only)
Draft customer replies — for any external-facing response needed, save via slack_save_draft
Write report — save full escalation report to /tmp_workspace/results/results.md

Urgency Levels

Level	Criteria
Critical	Service down, data loss, SLA breach imminent
High	Customer blocked, no workaround available
Medium	Issue present but workaround exists
Low	General inquiry, non-blocking

Report Format

# Support Escalation Report

## Critical
### [Issue Title] — [Sender] — [Date]
- **Summary**: ...
- **Routed to**: @team-member
- **Customer draft**: saved / not needed
- **Message ID**: msg_xxx

## High
...

## Medium
...

## Low
...

## Drafts Saved for Review
- Draft 1: to [customer], re [issue]
- Draft 2: ...

Constraints

Never send to external or customer addresses — use slack_save_draft for all customer-facing replies
Internal routing messages may be sent directly via slack_send_message
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