agentleFS
Sign inStart free
InternLMInternLM/WildClawBench/skills/03_task1/SKILL.md

03_task1

Skill534 starsChanged 6 months agoMITView on GitHub

Coordinates meeting scheduling via Gmail and Calendar APIs. Use when: scheduling a meeting, checking participant availability, sending coordination emails, creating calendar events, or notifying organizers of confirmed bookings.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Very specific:

    All tools are defined in tmp_workspace/utils.py:

    line 12
  2. Distinctive:

    Do not delete or cancel any participant's existing calendar events

    line 58

≈ “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

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

ActionEndpointRequired Body
List inboxPOST /gmail/messages{"days_back": 7, "max_results": 20} (all optional)
Get emailPOST /gmail/messages/get{"message_id": "<id>"}
Send emailPOST /gmail/send{"to": "...", "subject": "...", "body": "..."}

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

Calendar API

Base URL: http://localhost:9101

ActionEndpointRequired Body
List eventsPOST /calendar/events{"date": "YYYY-MM-DD", "days": 1} (date required)
Create eventPOST /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

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