{"id":81725,"plugin_id":"plugin_asdk_app_6ac20eabe68881919821c728fdfd58fa","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-05T01:16:48.380Z","digest":"8fd94907b11e00cd4814b1c157aeffe24565725413372b75cd621d6d28eb0de5","against":null,"payload":{"description":"Work out what to do and when before a wedding, invitation and RSVP dates, and when vendor payments fall due. Use when someone asks for a wedding checklist or timeline, when to send invitations, or what is due when.","included_files":[],"name":"wedding-timeline","skill_md_contents":"---\nname: wedding-timeline\ndescription: Work out what to do and when before a wedding, invitation and RSVP dates, and when vendor payments fall due. Use when someone asks for a wedding checklist or timeline, when to send invitations, or what is due when.\n---\n\nRun the tool for this and answer from its result: its amounts add up exactly and its dates count back from their day.\n\nUse this for anything about dates before the wedding.\n\n- **What to do and when:** run `build_wedding_checklist` with the wedding date, what is already\n  booked (`venue`, `catering`, `photographer`), and `destination: true` for a destination\n  wedding. Name the next two or three tasks and when; the view lists the rest by month. If the\n  date is close, say that overdue tasks have been spread from today.\n- **Invitations and RSVPs:** run `rsvp_dates` with the wedding date, and the caterer's headcount\n  date if they know it. Give the send date, the RSVP date to print, and the headcount date.\n- **Payments:** run `plan_vendor_payments` with each vendor's total, deposit and due dates. Point\n  out the heaviest month and anything overdue.\n\nDates are worked out from typical lead times, not their contracts. When a contract says\notherwise, the contract wins; tell them so if it matters.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}