Update to AI Board Lite

{
  "description": "Turns a meeting transcript into decisions, action items with an owner, a due date and the quote behind each one, and per-person follow-up drafts. Marks owners and dates nobody said as missing, and drafts follow-ups without sending them. Use when the user shares a transcript and asks \"what are the action items\", \"what did we agree\", \"wat zijn de actionables\", \"wat waren mijn acties\".",
  "included_files": [],
  "name": "actionables",
  "skill_md_contents": "---\nname: actionables\ndescription: Turns a meeting transcript into decisions, action items with an owner, a due date and the quote behind each one, and per-person follow-up drafts. Marks owners and dates nobody said as missing, and drafts follow-ups without sending them. Use when the user shares a transcript and asks \"what are the action items\", \"what did we agree\", \"wat zijn de actionables\", \"wat waren mijn acties\".\n---\n\n# Actionables\n\nNobody leaves a meeting knowing who owes what. That is the problem this solves.\nThe classic way to get it wrong is to invent owners and dates the room never\nsaid. So every action item traces back to a line in the transcript. Ownership\nthat was not said out loud becomes `UNASSIGNED`. It is never inferred from\nwhoever spoke last. The same goes for dates. You draft follow-ups. You never\nsend them.\n\n## Ground rules\n\n- Work only from the transcript the user provides. Nothing else counts as a\n  source.\n- Every decision and every action item carries the quote it came from.\n- No stated owner means `UNASSIGNED`. No stated date means \"no date agreed\".\n  Never infer either.\n- Answer in the language the user writes in. Draft each follow-up in the\n  language of the person it is for, if the transcript makes that clear.\n  The example below is in English; translate its headings too.\n\n## When to use\n\nThe user shares a meeting transcript, or points at one, and asks \"what are the\naction items\", \"what did we agree\", \"who owes what\", \"wat zijn de actionables\",\n\"wat waren mijn acties\".\n\n## Steps\n\n1. **Get the text.** Accept a pasted transcript, or a `.txt`, `.vtt`, `.srt`,\n   `.md` or `.docx` file. Read the file with whatever this environment offers.\n   For `.docx`, a converter such as `markitdown` works if it is installed. If\n   there is no way to read the file, ask the user to paste the text or export\n   it as `.txt`. Audio is out of scope: ask for the transcript the meeting\n   platform produced.\n2. **Find out who the user is** in the transcript, if it is not obvious. Ask\n   once. Their own items get pulled out at the end.\n3. **Read for four things:** decisions taken, action items, open questions and\n   things explicitly deferred. Extract every action item as owner, task, due\n   date and source quote.\n4. **Check speaker labels.** If the transcript has no speaker names, say so at\n   the top: owners can then only come from what was said (\"Marieke, can you…\"),\n   never from who was talking.\n5. **Draft one follow-up per person**, containing only their own items, short\n   enough to send as a chat message. Present them in the chat for the user to\n   copy.\n6. **Offer to keep it for next time.** If this environment can write files,\n   offer to save the result as `Meetings/<YYYY-MM-DD> · <meeting name>.md` in a\n   folder the user chooses. Explain the reason in one sentence: next time,\n   meeting prep can read this note instead of the user pasting it again. Do\n   not write anything without the user saying yes.\n\n## Output format\n\n```markdown\n## Decisions (2)\n- The pilot runs in Service, not Sales. · \"let's do service, that's where the volume is\"\n- Budget waits until the pilot shows numbers. · \"no budget before we see data\"\n\n## Action items (5)\n| # | Owner | Action | Due | Source |\n|---|---|---|---|---|\n| 1 | You | Confirm the pilot team to everyone | 2026-08-07 | \"I'll confirm it Friday\" |\n| 2 | Marieke | Budget frame for the pilot | 2026-08-14 | \"give me two weeks\" |\n| 3 | UNASSIGNED | Review data access before go-live | no date agreed | nobody claimed this |\n\n**Yours: 1 item, due Friday 2026-08-07.**\n\n## Open questions\n- Who signs off on go-live? Raised, not answered.\n\n## Follow-up drafts · copy and send yourself\n**To Marieke:** Hi Marieke, from today's meeting: the budget frame for the\nService pilot. You said two weeks, so 14 August. Let me know if that moves.\n```\n\n## Limits\n\n- Text in, text out. No audio transcription.\n- This skill never sends email, chat messages or invites. If the user asks\n  whether the follow-ups went out, the honest answer is that only they know.\n- A transcript without speaker labels gives weaker owners. Flag it, do not\n  guess.\n- Relative dates (\"next Friday\") are resolved against the meeting date. If the\n  meeting date is unknown, ask for it or keep the words as spoken.\n"
}