{"id":47398,"plugin_id":"plugin_asdk_app_6a6a03d6ef6c819189d3c338a3e97e8c","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:33:16.204Z","digest":"d30eedb596e0d0901875f49d3279c0883623e4e57b559e92c255c633539d794f","against":null,"payload":{"description":"Extract one calendar event from pasted or visible message text and create an editable Event Creator card. Use when the user asks to turn an email, chat, invitation, announcement, or copied notice into one event. Require the source text to be available in the conversation; do not retrieve mail or create multiple events.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":220}],"name":"event-from-message","skill_md_contents":"---\nname: event-from-message\ndescription: Extract one calendar event from pasted or visible message text and create an editable Event Creator card. Use when the user asks to turn an email, chat, invitation, announcement, or copied notice into one event. Require the source text to be available in the conversation; do not retrieve mail or create multiple events.\n---\n\n# Event From Message\n\nTurn one message into one accurate, editable event.\n\n## Inputs\n\nUse message text that is visible in the conversation and any corrections or\npreferences the user provides. Accept copied email, chat, invitation,\nannouncement, or notice text.\n\n## Workflow\n\n1. Identify the single event the user wants.\n   - If the message contains several distinct events and the user did not choose\n     one, ask which event to create.\n   - Ignore signatures, quoted reply history, tracking text, and unrelated\n     promotional copy.\n2. Extract only supported event facts:\n   - a concise title;\n   - the start and end, or a start plus an explicit duration;\n   - an IANA time zone when the source or conversation establishes one;\n   - an optional description, location, and HTTP(S) event URL.\n3. Separate source facts from assumptions.\n   - Resolve relative dates against the conversation date.\n   - Ask one concise clarification when ambiguity could change the scheduled\n     date, time, duration, timing mode, or time zone.\n   - Do not ask about missing optional details.\n   - Do not invent a location, URL, end time, or time zone.\n4. Choose the timing mode.\n   - Use timed timing when a time of day is intended.\n   - Use all-day timing only when the message describes a date-based event with\n     no intended time of day. Treat its end date as inclusive.\n   - For a timed event, include an explicit IANA time zone when known. Otherwise\n     allow `display-event` to use its client time-zone hint; if the tool cannot\n     resolve one, ask the user for it and retry.\n5. Invoke `display-event` once with the normalized event. Include optional\n   fields only when supported by the source or the user's instructions.\n6. Present the resulting editable card. Briefly disclose any non-obvious\n   interpretation that remained necessary.\n\n## Output\n\nDeliver one editable Event Creator card whose title, timing, time zone, and\noptional details match the source.\n\n## Boundaries\n\n- Do not retrieve email, messages, or attachments from another service.\n- Do not create multiple events from one invocation.\n- Do not add attendees, recurrence, reminders, or calendar-account writes.\n- Do not claim the event was added to a calendar. The user exports it from the\n  widget.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}