← Eventful: Make Calendar EventsCONTENT HISTORY

Update to Eventful: Make Calendar Events

Snapshot Oct 24, 2026 · 13:33 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Eventful: Make Calendar Events and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Turn one action item from visible meeting notes into a scheduled, editable Event Creator focus block. Use when the user asks to reserve time for a follow-up, deliverable, or preparation task identified in notes. Require one concrete action and an exact schedulable slot; do not create tasks, reminders, attendees, recurrence, or multiple blocks.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 252
    }
  ],
  "name": "meeting-notes-to-focus-block",
  "skill_md_contents": "---\nname: meeting-notes-to-focus-block\ndescription: Turn one action item from visible meeting notes into a scheduled, editable Event Creator focus block. Use when the user asks to reserve time for a follow-up, deliverable, or preparation task identified in notes. Require one concrete action and an exact schedulable slot; do not create tasks, reminders, attendees, recurrence, or multiple blocks.\n---\n\n# Meeting Notes To Focus Block\n\nTurn one meeting follow-up into one focused calendar block.\n\n## Inputs\n\nUse meeting notes visible in the conversation plus the user's chosen action,\nduration, scheduling window, and time-zone context.\n\n## Workflow\n\n1. Identify the single follow-up to schedule.\n   - Prefer the action the user names or an action clearly assigned to the user.\n   - If several plausible actions remain, ask which one to schedule.\n   - Do not schedule actions owned by someone else without the user's explicit\n     request.\n2. Define a concrete outcome for the block.\n   - Write a short action-oriented title.\n   - Distill two to five useful steps, acceptance criteria, or preparation notes\n     into the description.\n   - Include a relevant HTTP(S) source or meeting URL only when it is present in\n     the notes or supplied by the user.\n3. Resolve an exact timed schedule.\n   - Use the start and end the user provides, or calculate the end from an\n     explicit duration.\n   - If only a broad window such as \"Tuesday afternoon\" is given, ask for an\n     exact start time rather than choosing one silently.\n   - Include an explicit IANA time zone when known. Otherwise allow\n     `display-event` to use its client time-zone hint; if the tool cannot resolve\n     one, ask the user for it and retry.\n   - Confirm that the end is after the start and that the chosen time is not a\n     nonexistent DST wall time.\n4. Invoke `display-event` once with timed timing and the focused title,\n   description, and any supported URL or location.\n5. Present the resulting editable card. Keep the response centered on the\n   scheduled block rather than re-summarizing the entire meeting.\n\n## Output\n\nDeliver one editable Event Creator card for a concrete follow-up focus block,\nwith a concise outcome and actionable description.\n\n## Boundaries\n\n- Do not create a task-system entry or mark an action item complete.\n- Do not create multiple focus blocks from one invocation.\n- Do not add attendees, recurrence, reminders, or calendar-account writes.\n- Do not claim the block was added to a calendar. The user exports it from the\n  widget.\n"
}

SHA-256 of public snapshot: 33cd61ca5a6884795f8c27e5ec50036263683da17d5f5c6933f65c52a121427a