03_task1

A meeting-scheduling assistant that reads email, checks calendars, coordinates available times, and creates confirmed calendar events.

In plain words
What is it for?
Use it to review scheduling requests, suggest times, send coordination emails, confirm bookings, create calendar events, and notify organizers.
Why use it?
It removes the repeated back-and-forth of finding a time, confirming participants, and updating the organizer.

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_task1
Any agent
npx skills add InternLM/WildClawBench --skill 03_task1
Clone the repo
git clone --depth 1 https://github.com/InternLM/WildClawBench

Made for: Claude Code, Codex.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 541 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.00039 $0.00541
Opus 5 $0.00019 $0.00270
Sonnet 5 $0.00008 $0.00108
Haiku 4.5 $0.00004 $0.00054

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

Security

Grade A, and why

03_task1 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_task1/SKILL.md · 59 lines

What it actually says

Scheduling Assistant Skill

Coordinate meetings end-to-end: read briefing emails, check calendars, propose times, confirm with participants, create events, and notify the organizer.

Tools

All tools are defined in tmp_workspace/utils.py:

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

Gmail API

Base URL: http://localhost:9100

Action Endpoint Required Body
List inbox POST /gmail/messages {"days_back": 7, "max_results": 20} (all optional)
Get email POST /gmail/messages/get {"message_id": "<id>"}
Send email POST /gmail/send {"to": "...", "subject": "...", "body": "..."}

After sending any email, re-check the inbox for replies before proceeding.


Calendar API

Base URL: http://localhost:9101

Action Endpoint Required Body
List events POST /calendar/events {"date": "YYYY-MM-DD", "days": 1} (date required)
Create event POST /calendar/events/create {"title": "...", "start_time": "...", "end_time": "...", "attendees": [...]} + optional "location"

Workflow

  1. Read briefing — check inbox for the organizer's original request email
  2. Check calendars — list each participant's events for the candidate date range
  3. Propose a time — email participants with an available slot matching the required duration
  4. Collect replies — re-check inbox after each send to gather confirmations
  5. Create event — once confirmed, create the calendar event with all attendees
  6. Notify organizer — send a confirmation email to the original requester
  7. Write report — save summary to /tmp_workspace/results/results.md

Constraints

  • Do not delete or cancel any participant's existing calendar events
  • Final report must be written to /tmp_workspace/results/results.md
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 · 59 lines · 39 tokens per session scan A bbddf0211702

Subscribe to this mod's changes

03_task1 is a skill published in the GitHub repository InternLM/WildClawBench (516 stars, last pushed 16d ago), licensed MIT. It adds 39 tokens to every session and 541 once invoked, about $0.0002 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.