{"id":89638,"plugin_id":"plugin_asdk_app_6ad17d6658108191abfcee31ff835807","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-10T18:08:38.342Z","digest":"4b7b6ae6d2aba07dd2d025c8076c59c174f4a54cd55744953ae3f4694b1ebd0a","against":null,"payload":{"description":"Build and keep a shared custody calendar with Kidtime — pick a custody pattern (2-2-3, alternating weeks, every other weekend and more), set and move hand-offs, add holidays, birthdays and school breaks, and see who has the kids on any date. Use when a separated or co-parenting parent wants to plan, check or change custody time.","included_files":[{"relative_path":"references/handoffs-and-events.md","size_in_bytes":2014},{"relative_path":"references/holidays-and-traditions.md","size_in_bytes":1341},{"relative_path":"references/patterns-and-schedules.md","size_in_bytes":2323},{"relative_path":"references/reading-the-calendar.md","size_in_bytes":1770},{"relative_path":"references/sharing-and-keeping.md","size_in_bytes":1172}],"name":"kidtime","skill_md_contents":"---\nname: kidtime\ndescription: Build and keep a shared custody calendar with Kidtime — pick a custody pattern (2-2-3, alternating weeks, every other weekend and more), set and move hand-offs, add holidays, birthdays and school breaks, and see who has the kids on any date. Use when a separated or co-parenting parent wants to plan, check or change custody time.\n---\n\n# Kidtime\n\nKidtime is a custody calendar for separated parents. Its tools run the same actions as the Kidtime\napp, so what you make here is a real Kidtime calendar the person can open on the web or keep in the\napp.\n\n## No account needed\n\nEvery tool works without signing in. A calendar made in chat belongs to the person, and nobody else\nsees it or is told about it until they share or claim it. Only a parent who already keeps their\nfamily in the Kidtime app needs to sign in, to reach that family.\n\n## Order of work\n\n1. **Look first.** Call `groups_list` before making anything: the person may already have a\n   calendar from an earlier chat. Make a new one with `groups_save` only when there is none, or when\n   they ask for another.\n2. **Let them choose the pattern.** If they have not named one, call `custody_patterns_list`: it\n   shows a picker. Wait for their choice. If they describe their schedule instead (\"every other\n   weekend, Friday to Monday\"), match it to a pattern and confirm it with them.\n3. **Set the schedule** with `custody_schedules_save`, then check the first hand-offs with\n   `events_list`. If they are wrong, call `custody_schedules_save` again (it replaces the schedule).\n   Do not patch single hand-offs to fix a wrong schedule.\n4. **Show it** with `events_list`: it draws the month, with each parent's colour.\n5. **Changes** — moving a hand-off, extra time with the kids, or a one-off event — go through\n   `events_save`; removing one through `events_delete`. Ask before deleting.\n6. **Holidays and breaks**: `traditions_list` to see what is on, `traditions_save` to add or remove,\n   `traditions_get` for who had the kids on a holiday in past years. A birthday is a person's: set\n   it with `members_save`.\n\n## More detail\n\nRead the file that matches the request before acting on it:\n\n- `references/patterns-and-schedules.md`: choosing and saving a pattern, start day, hand-off times\n- `references/handoffs-and-events.md`: moving a hand-off, extra time with the kids, one-off events,\n  deleting\n- `references/holidays-and-traditions.md`: holidays, birthdays, school breaks, past years\n- `references/reading-the-calendar.md`: who has the kids when, nights and splits, answering clearly\n- `references/sharing-and-keeping.md`: the calendar's link, PDF, keeping it, deleting it\n\n## Never\n\n- Never mention prices, plans, trials or upgrades, and never send the person to a payment page.\n- Never give legal advice or say who should have custody. Kidtime records and plans a schedule; for\n  what a court would decide, suggest a family law attorney or mediator.\n- Never invent a member id or a groupId. Take them from `groups_list`, `groups_save` and\n  `members_list`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}