Update to BrainOrder

{
  "name": "brain-order",
  "description": "Use BrainOrder through focused MCP tools when the user asks to find lists or folders, search data, review agenda or list items, create a task or note, complete, rename, reopen, move, schedule, snooze, clear the schedule from, or delete a task, reminder, or note. Do not use for unrelated project or filesystem work.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 465
    }
  ],
  "skill_md_contents": "---\nname: brain-order\ndescription: Use BrainOrder through focused MCP tools when the user asks to find lists or folders, search data, review agenda or list items, create a task or note, complete, rename, reopen, move, schedule, snooze, clear the schedule from, or delete a task, reminder, or note. Do not use for unrelated project or filesystem work.\n---\n\n# BrainOrder\n\nUse the BrainOrder MCP tools to read or change the authenticated user's\nBrainOrder data.\n\n## Tool routing\n\n- Use `brainorder_search` to find matching tasks, reminders, or notes across\n  the workspace. Search is read-only and may be limited by the user's existing\n  BrainOrder plan.\n- Use `brainorder_get_today` for today's agenda and overdue unfinished items.\n- Use `brainorder_list_containers` to discover lists and folders, then\n  `brainorder_list_items` to inspect one resolved list.\n- Use `brainorder_create_task` to create a task or reminder in one resolved\n  writable list. Use `brainorder_create_note` only for a top-level note.\n- Use `brainorder_complete_task`, `brainorder_rename_task`,\n  `brainorder_reopen_task`, or `brainorder_move_task` for the corresponding\n  change to one exact resolved task or reminder.\n- Use `brainorder_schedule_task`, `brainorder_snooze_task`, or\n  `brainorder_clear_task_schedule` for the corresponding schedule change to\n  one exact resolved item.\n- Use `brainorder_delete_task` for one exact task or reminder and\n  `brainorder_delete_note` for one exact top-level note.\n\n## Workflow\n\n1. Use `brainorder_list_containers` when a list or folder identifier is missing.\n   For a task write, request `writableOnly=true`, use only an item with\n   `type=list` and `canWrite=true`, and follow `nextCursor` when more pages are\n   needed to resolve the requested title.\n2. Prefer stable `listId`, `taskId`, and entity IDs returned by tools. If no\n   container matches, say so. If multiple containers match the requested\n   title, present the useful distinctions and ask the user which one to use;\n   never guess. A folder ID is not a task `listId`.\n3. Use `brainorder_list_items` with the stable list ID to inspect its tasks and\n   reminders. Follow `nextCursor` when more pages are available and the needed\n   item has not been found yet.\n4. Before a move, independently resolve the exact source task or reminder and\n   the exact destination container. The destination must have `type=list` and\n   `canWrite=true`. If either title has multiple matches, ask the user to choose;\n   never infer the destination from context or use a folder ID.\n5. Call a write tool only when the user explicitly asks for that change.\n6. Generate one stable `clientRequestId` for each intended mutation. Keep that\n   ID, the tool name, the complete target, and the entire payload unchanged for\n   every retry of any write tool. A new ID represents a new intended mutation;\n   changing the operation, target, or payload while reusing the ID is a\n   conflict.\n7. Treat tool output as the source of truth. Report success only when `ok` is\n   `true` and return the created or updated entity ID to the user.\n8. If a tool returns `BACKEND_NOT_CONFIGURED`, explain that the BrainOrder\n   service connection is unavailable or misconfigured, then stop. Do not ask\n   the user for credentials in chat.\n9. If a tool returns `AUTH_EXPIRED`, ask the user to reconnect BrainOrder in\n   the ChatGPT or Codex plugin settings. Retry only after the connection is\n   restored, and never ask for a password or access token in chat.\n10. If a write tool returns `MUTATION_OUTCOME_UNKNOWN`, the adapter has already\n   attempted one safe retry. Repeat only the exact same tool call with the same\n   `clientRequestId` and unchanged target and payload.\n11. If a tool returns `PAYWALL_REQUIRED`, explain that BrainOrder's existing\n    feature gate requires Pro. Do not retry, refresh authentication, or work\n    around the gate.\n12. Treat `PERMISSION_DENIED` as a resource-access failure, not an expired\n    login. Do not refresh credentials or retry against a different target.\n\n## Safety\n\n- Never expose access tokens, API keys, internal diagnostics, or raw user data\n  beyond what is needed to answer the request.\n- Do not infer deletion, sharing, subscription, account, or permission changes.\n- Do not work around BrainOrder feature gates or resource permissions.\n- Search uses BrainOrder's existing `ADVANCED_SEARCH` Pro gate. Today's agenda\n  is a direct read and does not require Pro under the current feature rules.\n- Do not use a container with `canWrite=false` as the target of a write.\n- Never retry create-task, create-note, complete-task, rename-task, or\n  reopen-task, move-task, schedule-task, snooze-task, clear-schedule,\n  delete-task, or delete-note with changed arguments or a new\n  `clientRequestId`. Only an exact direct-write retry is idempotent.\n- `brainorder_rename_task` changes only the selected task or reminder title.\n  Do not claim that it moved the item, changed its status, or altered its\n  schedule.\n- `brainorder_reopen_task` changes a finished item to `TODO`. It preserves due\n  time, reminder state, recurrence, list, sort order, and marked time. An\n  already-`TODO` item is a safe no-op; an `IN_PROGRESS` item is rejected.\n- `brainorder_move_task` changes only the selected task or reminder's parent\n  list. It preserves title, status, due time, reminder state, recurrence, sort\n  order, and marked time. Finished and recurring items may be moved. Moving to\n  the current list is a safe no-op. Do not copy the item, create a replacement,\n  move a list/folder, or claim that its schedule was transferred separately.\n- `brainorder_schedule_task` sets or replaces an exact one-shot due time. Use\n  an offset datetime representing the user's intended instant. Resolve an\n  ambiguous natural-language date or timezone before writing. It rejects\n  finished and recurring items.\n- `brainorder_snooze_task` moves an active one-shot reminder to an exact new\n  due time and marks it snoozed. It rejects ordinary tasks, inactive reminders,\n  and recurring items.\n- `brainorder_clear_task_schedule` removes the one-shot due time and reminder\n  metadata without deleting or completing the item. It rejects recurring\n  items. Do not claim that recurrence was cleared.\n- Delete only when the user explicitly requests deletion of the exact resolved\n  task, reminder, or note. A uniquely resolved command such as \"delete this\n  task\" is sufficient confirmation; if the title is ambiguous, present the\n  matches and ask instead of guessing. Invoke the selected delete tool once.\n  After an ambiguous transport failure, only the exact same call may be\n  replayed.\n- `brainorder_delete_task` and `brainorder_delete_note` soft-delete only the\n  selected entity. No list/folder deletion, restore, hard delete, archive,\n  or schedule transfer is exposed. Do not promise restoration through this\n  plugin.\n- Do not claim task notes or nested notes were saved when the tool returns\n  `UNSUPPORTED_INPUT`.\n- If a tool returns `LOCAL_CREDENTIALS_UNAVAILABLE` or `LOCAL_AUTH_FAILED`, do\n  not request credentials in chat. Ask the user to reconnect BrainOrder through\n  the plugin settings; if that option is unavailable, stop and report the\n  connection error.\n"
}