Update to Goodsend

{
  "description": "Use for Goodsend profiles, Circle members, collections, wishlists, saved items, owned items, gift ideas, reservations, or goodsend.it links.",
  "included_files": [],
  "name": "goodsend-workflows",
  "skill_md_contents": "---\nname: goodsend-workflows\ndescription: Use for Goodsend profiles, Circle members, collections, wishlists, saved items, owned items, gift ideas, reservations, or goodsend.it links.\n---\n\n# Goodsend workflows\n\nUse Goodsend as the source of truth for a connected account's saved products,\ncollections, wishlists, Circle, and visible profiles.\n\n## Present the final result\n\n- When the request resolves to exactly one profile, collection, wishlist, or\n  item, finish with the matching `render_user_profile`,\n  `render_collection_preview`, or `render_good_preview` tool. Do this even when\n  the user says “tell me about,” “what is in,” or otherwise omits words such as\n  “show,” “open,” “card,” or “preview.”\n- Do not mount a preview when the user explicitly asks for text only.\n- For broad or multi-result requests, return the data result without mounting\n  several previews.\n- For an ambiguous name, resolve it with the relevant list tool. Render only\n  after one clear match remains; otherwise ask the user which result they mean.\n- Render once, as the final presentation step, after gathering any context\n  needed to answer the request.\n\n## Resolve profiles, collections, and items\n\n- An exact Goodsend profile URL can go directly to `render_user_profile`.\n  A person's name or handle can go in its `person_query`; it resolves a unique\n  Circle match internally.\n- An exact collection ID or shared collection URL can go directly to\n  `render_collection_preview`. A connected account's collection title can go in\n  its `query`; it resolves a unique accessible collection internally.\n- An exact saved-item ID can go directly to `render_good_preview`. A saved-item\n  title or URL fragment can go in its `query`. Include `profile_url` when\n  resolving an item from another visible profile.\n- Use `list_circle`, `list_collections`, or `list_saved_items` when the user asks\n  for a list, when several matches may matter, or when a write needs exact IDs.\n- Treat `get_user_profile`, `get_collection`, and `get_shared_collection` as\n  data-oriented calls. For a conversational request about one exact object,\n  follow the data work with its render tool unless the user requested text only.\n\n## Find grounded gifts\n\n1. Resolve the recipient with `list_circle` or a supplied Goodsend profile URL.\n2. Call `get_user_items_from_profile_url`; its result already includes the\n   profile, so do not fetch the profile first merely to repeat that information.\n3. Use `list_owned_items` to avoid suggesting something the recipient already\n   owns.\n4. Use `get_public_wishlist` when availability matters. Never claim an item is\n   available unless this tool reports it as available.\n5. Explain whether a suggestion is an explicit available wishlist item or only\n   a taste signal. Render the chosen item, wishlist, or profile as the final\n   single-object presentation when appropriate.\n\n## Change data safely\n\n- Resolve collection and item IDs before writes. If a spoken name remains\n  ambiguous, ask which target the user means.\n- Use `add_links_to_collection` once for a multi-link request.\n- Removing an item from a collection keeps it saved. Archiving a saved item\n  removes it from collections owned by the connected account.\n- Do not infer a mutation from a request to inspect, browse, or preview data.\n- Respect the permission and reservation fields returned by collection tools.\n  Never identify another person who reserved a wishlist item.\n"
}