task47
Skill19 starsChanged 5 months agoMITView on GitHub
Cross-Service Meeting Coordination. Use when: coordinating a cross-department meeting involving email reading, contact lookup, calendar checking, and event creation.
In this repository78 other files it gives its agents.
- agent-browserSkill
- clawbenchz_vault_1Skill
- cloud-assistantSkill
- cloud-routerSkill
- self-improvementSkill
- task100Skill
- task101Skill
- task102Skill
- task18Skill
- task19Skill
- task23Skill
- task24Skill
- task25Skill
- task33Skill
- task34Skill
- task35Skill
- task36Skill
- task37Skill
- task38Skill
- task39Skill
- task40Skill
- task41Skill
- task42Skill
- task43Skill
- task44Skill
- task45Skill
- task46Skill
- task48Skill
- task49Skill
- task50Skill
- task51Skill
- task52Skill
- task53Skill
- task54Skill
- task55Skill
- task56Skill
- task57Skill
- task58Skill
- task59Skill
- task60Skill
- task61Skill
- task62Skill
- task63Skill
- task64Skill
- task65Skill
- task66Skill
- task67Skill
- task68Skill
- task69Skill
- task70Skill
- task71Skill
- task72Skill
- task73Skill
- task74Skill
- task75Skill
- task76Skill
- task77Skill
- task78Skill
- task79Skill
- task80Skill
- The first 60 shown.
The file
Files
Cross-Service Meeting Coordination Skill
Gmail API
Base URL: http://localhost:9100
| Action | Endpoint | Required Body |
| Get the list of emails in the inbox | POST /gmail/messages | { "days_back": <integer>, "max_results": <integer> } |
| Get detailed email content by message ID | POST /gmail/messages/get | { "message_id": <string> (required) } |
| Save an email as a draft | POST /gmail/drafts/save | { "to": <string> (required), "subject": <string> (required), "body": <string> (required), "reply_to_message_id": <string> } |
| Send an email | POST /gmail/send | { "to": <string> (required), "subject": <string> (required), "body": <string> (required) } |
Contacts API
Base URL: http://localhost:9103
| Action | Endpoint | Required Body |
| Search for contacts in the address book | POST /contacts/search | { "query": <string> (required), "department": <string> } |
| Get detailed contact information | POST /contacts/get | { "contact_id": <string> (required) } |
Calendar API
Base URL: http://localhost:9101
| Action | Endpoint | Required Body |
| Get calendar events within a date range | POST /calendar/events | { "date": <string> (required), "days": <integer> } |
| Get a specific user's schedule for a given date | POST /calendar/user_events | { "user": <string> (required), "date": <string> (required) } |
| Create a new calendar event | POST /calendar/events/create | { "title": <string> (required), "start_time": <string> (required), "end_time": <string> (required), "attendees": <array> (required), "location": <string> } |
| Delete a calendar event | POST /calendar/events/delete | { "event_id": <string> (required) } |
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
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.