Update to Albo

{
  "description": "Build an itinerary or plan from the user's saved Albo places — day plans, trip itineraries, date nights, food crawls. Use when the user asks to plan something using their saves.",
  "included_files": [],
  "name": "plan",
  "skill_md_contents": "---\nname: plan\ndescription: Build an itinerary or plan from the user's saved Albo places — day plans, trip itineraries, date nights, food crawls. Use when the user asks to plan something using their saves.\n---\n\n# Plan with Albo\n\nTurn the user's saved places into a concrete plan or itinerary.\n\n## Steps\n\n1. Clarify the basics if missing: where, when/how long, and any constraints (budget, dietary, with kids, etc.). One short question max — otherwise make sensible assumptions and state them.\n2. Gather candidates:\n   - `geocodeLocation` for the destination, then `searchPlacesNearby` for saved places in the area.\n   - `searchExtracts` (query, `isWishlisted: true`, relevant `extractTypes`/`tagNames`) for wishlist items that fit.\n   - `listCollections` if the user names a collection (e.g. \"my Tokyo list\").\n3. Build the plan: group by day and neighbourhood to minimise back-and-forth travel, alternate meals/activities sensibly, and note opening-hours caveats as assumptions to verify.\n4. Offer to save the finished plan back into Albo with `createDocument` so it shows up in the user's app.\n5. If a collection for the trip exists, offer to add any newly relevant items with `addCollectionItems`.\n\n## Notes\n\n- Prefer the user's own saves over generic suggestions; only suggest non-saved fillers when there's an obvious gap, and label them clearly.\n- Use `readCollectionMemory` for existing trip constraints. Use `saveCollectionMemory` only when the user states a durable collection-specific preference worth retaining (e.g. \"vegetarian\", \"no museums\").\n"
}