{"id":47399,"plugin_id":"plugin_asdk_app_6a6a03d6ef6c819189d3c338a3e97e8c","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:33:16.221Z","digest":"1352f7a9e700e17d2d200177607d3454bfb3b23e0a450e8cf99c7f40f4da8fbb","against":null,"payload":{"description":"Extract one calendar event from a visible flyer, poster, screenshot, or photographed notice and create an editable Event Creator card. Use when the user asks to turn event artwork or an image-based announcement into an event. Require the image to be visible and readable; do not invent text, decode an unreadable QR destination, or create multiple events.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":227}],"name":"flyer-to-calendar-event","skill_md_contents":"---\nname: flyer-to-calendar-event\ndescription: Extract one calendar event from a visible flyer, poster, screenshot, or photographed notice and create an editable Event Creator card. Use when the user asks to turn event artwork or an image-based announcement into an event. Require the image to be visible and readable; do not invent text, decode an unreadable QR destination, or create multiple events.\n---\n\n# Flyer To Calendar Event\n\nTurn one visible event flyer into one accurate, editable event.\n\n## Inputs\n\nUse the attached or otherwise visible flyer, poster, screenshot, or photographed\nnotice together with any corrections the user provides.\n\n## Workflow\n\n1. Confirm that the image is available and readable enough to identify an\n   event. If it is missing or unreadable, ask the user to attach a clearer image\n   or paste the relevant text.\n2. Identify the single event the user wants.\n   - If the image advertises several sessions, dates, or performances and the\n     user did not choose one, ask which one to create.\n   - Distinguish event facts from decorative, sponsor, and promotional text.\n3. Extract only supported event facts:\n   - a concise title;\n   - start and end information or an explicit duration;\n   - an IANA time zone when the flyer or conversation establishes one;\n   - an optional venue or address, description, and clearly readable HTTP(S)\n     event URL.\n4. Check visually ambiguous details before scheduling.\n   - Ask one concise clarification when a numeric date, missing year, time,\n     duration, timing mode, or time zone has more than one material\n     interpretation.\n   - Do not infer a URL from a QR code whose destination is not visibly decoded.\n   - Do not invent obscured or cropped text.\n5. Choose the timing mode.\n   - Use timed timing when the flyer specifies or clearly intends a time of day.\n   - Use all-day timing only for a genuinely date-based event, not merely\n     because the time is unreadable. 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.\n6. Invoke `display-event` once with the normalized event and only supported\n   optional details.\n7. 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 based on the readable event facts in\nthe image.\n\n## Boundaries\n\n- Do not claim to use an OCR, QR-decoding, browsing, or image-retrieval service\n  that is not available in the conversation.\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":{}}