Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

03 Task5

skill · InternLM/WildClawBenchMIT licenceAudited 15 Oct 2026 · source a79d9cd3663a

★ 533pushed 27 days ago
✓SAFEGrade B · 89/100 · 15 Oct 2026 · a79d9cd
533repo stars · whole InternLM/WildClawBench

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit a79d9cd3663a and found no filesystem, network or shell access and no hard-coded secrets. What it does: 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…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “03 Task5 (InternLM/WildClawBench)”. Retrieved 15 Oct 2026. https://modelsatlas.com/skills/internlm/03-task5

Trust audit

Audit 0.4.1 · source read 15 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha a79d9cd3663a · 15 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • PublisherInternLM GitHub organizationOwner of the repository this skill is read from
  • Source folderInternLM/WildClawBench/skills/03_task5The exact folder we audited
  • LicenceMITAs the repository states it
  • Commit pinned for this verdicta79d9cd3663aA new audit runs when the source changes
  • Repository statusNot archivedLast push 27 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: 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…

---
name: 03_task5
description: "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."
---

# 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

1. **List messages** — fetch recent messages with `slack_list_messages`
2. **Read each in full** — retrieve complete content via `slack_get_message`
3. **Classify sender** — use `contacts_search` / `contacts_get` to determine if internal or external/customer
4. **Assess urgency** — flag as Critical / High / Medium / Low based on impact and time-sensitivity
5. **Route internally** — identify the right team member for each issue; send routing notes via `slack_send_message` (internal only)
6. **Draft customer replies** — for any external-facing response needed, save via `slack_save_draft`
7. **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

```markdown
# 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`

Excerpt, first 3,429 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit a79d9cd

Download folder ↗
git clone https://github.com/InternLM/WildClawBench
git -C WildClawBench checkout a79d9cd3663a

The author documents no install command, so this uses the repository directly. Our verdict covers commit a79d9cd3663a only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source a79d9cd3663a

Similar skills

Questions about 03 Task5

What does the 03 Task5 skill do?
An in-the-wild benchmark for AI agents in the production harness.
Is 03 Task5 safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can 03 Task5 access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (a79d9cd3663a), read on 2026-10-15. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.