Menu
Use Mirra to google calendar event management and scheduling. Covers all Google Calendar SDK operations via REST API.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use Mirra to living dashboards — natively-rendered grids of typed widgets (stat, image_card, list, progress, sparkline) that flows keep current by pushing data into them..... Covers all Dashboards SDK operations via REST API.
Use Mirra to execute user-defined scripts in aws lambda. Covers all Scripts SDK operations via REST API.
Use Mirra to the places a space publishes to — its corporate x, blog, newsletter — and the drafted copy waiting to go out to them. use listchannels to see what this space.... Covers all Space Channels SDK operations via REST API.
Use Mirra to the space's shared work-ledger. items are agreed work with status (open/proposed/done), an owner, artifact links, and progress notes; every teammate's home f.... Covers all Work Items SDK operations via REST API.
The team work-ledger ritual for agents on a Mirra space: track agreed work, propose discoveries (then ask in chat), relay approvals, close what ships, and publish ONE narrated update card per work burst — revise, never stack. Rides the Mirra items adapter / MCP work-ledger tools.
START HERE for anything Mirra. Load this whenever the repo you're working in has a .mirra/ directory (it's linked to a Mirra team space), or your human mentions their Mirra space, teammates' updates, or the team ledger. Directs the ambient team rituals — record work in the shared ledger, publish update cards, ask the space before expanding scope — and indexes every detail-level mirra-* skill.
| name | mirra-google-calendar |
| description | Use Mirra to google calendar event management and scheduling. Covers all Google Calendar SDK operations via REST API. |
| allowed-tools | Read, Bash(curl:*, jq:*) |
Google Calendar event management and scheduling
You need the user's API key. Ask for these if not provided:
API_KEY: Mirra API key (generated in Mirra app > Settings > API Keys)API_URL: Defaults to https://api.fxn.world (only ask if they mention a custom server)Note: Google Calendar requires OAuth authentication. The user must have connected their Google Calendar account in the Mirra app before these operations will work.
All operations use a single POST endpoint with the resource ID and method in the body:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{
"resourceId": "google-calendar",
"method": "{operation}",
"params": { ...args }
}' | jq .
Replace {operation} with the operation name from the table below.
Legacy alternative:
POST ${API_URL}/api/sdk/v1/googleCalendar/{operation}with args as the request body also works but is not recommended for new integrations.
| Operation | Description |
|---|---|
createEvent | Create a new calendar event |
listEvents | List calendar events |
getEvents | Get calendar events (alias for listEvents) |
getEvent | Get a specific calendar event by ID |
updateEvent | Update an existing calendar event |
deleteEvent | Delete a calendar event |
searchEvents | Search calendar events by text query |
createEventCreate a new calendar event
Arguments:
summary (string, required): Event title/summarystart (object, required): Start time object with dateTime and optional timeZoneend (object, required): End time object with dateTime and optional timeZonedescription (string, optional): Event descriptionlocation (string, optional): Event locationattendees (array, optional): Array of attendee email addressesReturns:
AdapterOperationResult: Created event information
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"google-calendar","method":"createEvent","params":{"summary":"<value>","start":{},"end":{}}}' | jq .
Warning: This is a destructive operation. Confirm with the user before executing.
listEventsList calendar events
Arguments:
timeMin (string, optional): Start time for events to list (ISO 8601)timeMax (string, optional): End time for events to list (ISO 8601)maxResults (number, optional): Maximum number of events to return (default: 50, max: 100)query (string, optional): Search query to filter eventsReturns:
AdapterOperationResult: List of calendar events
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"google-calendar","method":"listEvents","params":{}}' | jq .
getEventsGet calendar events (alias for listEvents)
Arguments:
timeMin (string, optional): Start time for events to list (ISO 8601)timeMax (string, optional): End time for events to list (ISO 8601)maxResults (number, optional): Maximum number of events to return (default: 50, max: 100)query (string, optional): Search query to filter eventsReturns:
AdapterOperationResult: List of calendar events
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"google-calendar","method":"getEvents","params":{}}' | jq .
getEventGet a specific calendar event by ID
Arguments:
eventId (string, required): Calendar event IDReturns:
AdapterOperationResult: Calendar event details
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"google-calendar","method":"getEvent","params":{"eventId":"<ID>"}}' | jq .
updateEventUpdate an existing calendar event
Arguments:
eventId (string, required): Calendar event ID to updatesummary (string, optional): Updated event title/summarydescription (string, optional): Updated event descriptionlocation (string, optional): Updated event locationstart (object, optional): Updated start time object with dateTime and optional timeZoneend (object, optional): Updated end time object with dateTime and optional timeZoneReturns:
AdapterOperationResult: Updated event information
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"google-calendar","method":"updateEvent","params":{"eventId":"<ID>"}}' | jq .
Warning: This is a destructive operation. Confirm with the user before executing.
deleteEventDelete a calendar event
Arguments:
eventId (string, required): Calendar event ID to deleteReturns:
AdapterOperationResult: Deletion confirmation
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"google-calendar","method":"deleteEvent","params":{"eventId":"<ID>"}}' | jq .
Warning: This is a destructive operation. Confirm with the user before executing.
searchEventsSearch calendar events by text query
Arguments:
query (string, required): Search query to filter eventstimeMin (string, optional): Start time for events to search (ISO 8601)timeMax (string, optional): End time for events to search (ISO 8601)maxResults (number, optional): Maximum number of events to return (default: 50, max: 100)Returns:
AdapterOperationResult: List of matching calendar events
Example:
curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
-H "Content-Type: application/json" \
-H "x-api-key: ${API_KEY}" \
-d '{"resourceId":"google-calendar","method":"searchEvents","params":{"query":"search term"}}' | jq .
All SDK responses return the operation payload wrapped in a standard envelope:
{
"success": true,
"data": { ... }
}
The data field contains the operation result. Error responses include:
{
"success": false,
"error": {
"code": "ERROR_CODE",
"message": "Human-readable error message"
}
}
jq . to pretty-print responses, jq .data to extract just the payloaddata.results or directly in data (check examples)--fail-with-body to curl to see error details on HTTP failuresexport API_KEY="your-key"