Update to Be Well Packed

{
  "description": "Build or revise a Be Well Packed visual outfit plan from clothing photos or descriptions for a trip, wedding weekend, busy week, or event.",
  "included_files": [],
  "name": "plan-outfits",
  "skill_md_contents": "---\nname: plan-outfits\ndescription: \"Build or revise a Be Well Packed visual outfit plan from clothing photos or descriptions for a trip, wedding weekend, busy week, or event.\"\n---\n\nUse the connected Be Well Packed tool schemas and server instructions as the source for valid inputs. Understand dates, destination, activities, clothing preferences and pieces already provided. Ask the smallest useful follow-up when needed. Use get_trip_weather when destination and dates are known; describe unavailable weather honestly rather than inventing a forecast.\nCompose outfits using the person's supplied clothes first. Use one stable piece id across every look that rewears it. Pass every user-supplied clothing photo using the tool's declared file mechanism and photoIndex; do not fabricate image URLs. Distinguish owned pieces from suggestions. Explain a few meaningful gaps instead of adding unnecessary shopping.\nCall plan_trip_outfits to render the lookbook. For revisions, keep the returned draftId, pass the full revised plan, and reuse retained photoIds. Preserve unrelated outfits and user choices. Summarize the change briefly rather than repeating the whole board.\nWhen they ask to save, call save_trip_to_well_packed and show the returned link. Explain that Keep this trip on the website saves into their account. Do not say a Plan or Closet pieces are already in their account before that claim succeeds. Do not promise photo polishing for every save. These tools do not book travel, purchase clothes, read an existing Closet, or delete saved Plans.\n"
}