Update to Odyssey365

{
  "description": "Turn a conversation, plan, meeting notes, or brainstorm into a laid-out Odyssey project board — task lists for things to do, note cards for things to read, grouped into sections. Use when the user says \"put this on a board\", \"make a project for this\", \"organize this into Odyssey\", \"save these ideas to my board\", or asks to add a batch of tasks and notes to an existing board.",
  "included_files": [],
  "name": "board-builder",
  "skill_md_contents": "---\nname: board-builder\ndescription: Turn a conversation, plan, meeting notes, or brainstorm into a laid-out Odyssey project board — task lists for things to do, note cards for things to read, grouped into sections. Use when the user says \"put this on a board\", \"make a project for this\", \"organize this into Odyssey\", \"save these ideas to my board\", or asks to add a batch of tasks and notes to an existing board.\n---\n\n# Build an Odyssey board\n\nA board is a canvas of components. Items (tasks, notes) live in their own documents and a board only\n**references** them from `itemTile` components. Creating an item does not put it on a board, and\nremoving it from a board does not delete it.\n\n## Layout rule: the container follows the item\n\n| Item | How to place it | Why |\n|---|---|---|\n| **Task** | Many tasks inside **one** `itemTile` list | Tasks are scanned and moved through states |\n| **Note** | **One** note per `itemTile` card, laid out as a grid | Notes are opened and read one at a time |\n\nA list of twenty notes shows only titles; a grid of twenty task cards is noise. Keep to the table above\nunless the user asks for something else.\n\n## Steps\n\n1. **Pick the board.** If the user named one, find it with `list_projects` (or `search`). Otherwise ask\n   whether to create a new board; create it with `create_project` only after they agree to a name.\n2. **Read before writing.** For an existing board call `get_project` with `includeComponents: true`.\n   Reuse its sections and lists (see `structure.sections` and each component's `text`) instead of\n   creating duplicates. Never move or restyle components the user arranged by hand.\n3. **Draft the outline in chat first** when you will create more than about five items: sections,\n   lists, and which items go where. Wait for a go-ahead, then build.\n4. **Create containers.**\n   - Section (optional grouping frame): `add_project_component` with `type: \"section\"` and `text`.\n   - Task list: `add_project_component` with `type: \"itemTile\"`, `text` = list title, and `sectionId`\n     when it belongs to a section. The section positions it; do not compute coordinates.\n5. **Create items straight into their container** — one call each, no separate attach step:\n   - Task: `create_todo` with `projectUid` = board id and `attachToComponentId` = the list's id.\n   - Note: first create an empty `itemTile` card for it at its grid position (step 6), then\n     `create_memo` with `text` (the body), `projectUid`, and `attachToComponentId` = that card's id.\n   Existing items are added with `update_project_component` using `mode: \"append\"` and `containItems`.\n6. **Place note cards as a grid** by giving each card `size: {width: 400, height: 220}` and an explicit\n   `offset`: 5 columns, gap 40, starting below the lists (for example `dy` 560). Card `i` goes to\n   `dx = (i % 5) * 440`, `dy = 560 + floor(i / 5) * 260`. Cards cannot be narrower than 400.\n7. **Tidy only boards you just made.** If the board was new and has no note grid, call `tidy_board`\n   once at the end. Do not call it after placing a grid (it re-flows the grid) or on a board the user\n   arranged by hand.\n8. **Report back** in chat: the board name, each section/list with item counts, and anything you\n   skipped. Do not paste raw tool output.\n\n## Guardrails\n\n- A call that names a missing component or item fails and creates nothing; fix the id and retry\n  rather than re-creating items (an `attachError` in a success response means the item exists — do\n  not create it again).\n- On a board shared with the user (`shared: true`), you can add only the user's own items, and a list\n  can be edited only with `mode: \"append\"` or `\"remove\"`.\n- Deleting components (`delete_project_component`) or items needs an explicit yes from the user.\n- Write item titles in the user's language, short and actionable (\"Draft landing copy\", not\n  \"Landing copy things\").\n"
}