{"id":84918,"plugin_id":"plugin_asdk_app_6adf7d1bc6848191b63b48f4ce2b78f9","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-06T18:21:45.437Z","digest":"cc1510dcb6c2490039de2d39c1d1f31be32b17613953408610020ad25d19a9d2","against":null,"payload":{"description":"Kaus turns meeting notes or transcripts into action lists (owner, action, due date, source quote) with ambiguity flags and draft follow-ups. Use when the user wants action items from a meeting, a transcript turned into next steps with owners and deadlines, who owes what from a call, or draft follow-up messages from meeting notes. Trigger on phrases like \"extract action items from this meeting\", \"meeting notes to action list\", \"summarize this meeting and assign owners\", \"draft follow-ups from this call\", \"turn this transcript into next steps\", \"meeting action items with deadlines\", \"who owes what from this meeting\", \"follow-up emails from meeting notes\", \"action list from this Zoom transcript\", or \"draft Slack follow-ups from the call\".","included_files":[{"relative_path":"assets/action-table-schema.md","size_in_bytes":1152},{"relative_path":"references/extraction-rules.md","size_in_bytes":978}],"name":"meeting-actions","skill_md_contents":"---\nname: meeting-actions\ndescription: Kaus turns meeting notes or transcripts into action lists (owner, action, due date, source quote) with ambiguity flags and draft follow-ups. Use when the user wants action items from a meeting, a transcript turned into next steps with owners and deadlines, who owes what from a call, or draft follow-up messages from meeting notes. Trigger on phrases like \"extract action items from this meeting\", \"meeting notes to action list\", \"summarize this meeting and assign owners\", \"draft follow-ups from this call\", \"turn this transcript into next steps\", \"meeting action items with deadlines\", \"who owes what from this meeting\", \"follow-up emails from meeting notes\", \"action list from this Zoom transcript\", or \"draft Slack follow-ups from the call\".\n---\n\n# Meeting dump → action list + follow-ups (Kaus)\n\nTurn meeting notes or a transcript into a clear action table, ambiguity flags, and draft follow-ups the user can paste themselves.\n\nLoad the table schema from `assets/action-table-schema.md` when formatting output. Use `references/extraction-rules.md` when ownership or deadlines are ambiguous.\n\n## When to use\n\nActivate when the user pastes a **meeting transcript, call notes, or meeting dump** and wants **action items, owners, deadlines, or follow-up drafts**.\n\nDo **not** activate for: general article summaries, project planning with no meeting source, CRM logging requests, or “send this email for me” automation.\n\n## Inputs expected\n\n- Meeting notes or transcript (required)\n- Optional: meeting date, timezone (for relative deadlines like “by Friday”)\n- Optional: preferred follow-up channel (email vs Slack) and tone\n\n## Missing-info behavior\n\n1. If there is **no meeting content**, ask the user to paste notes or a transcript. Do not invent a meeting.\n2. If deadlines are relative (“end of week”, “by Friday”) and the **meeting date** is unknown, ask once; until then keep due as the relative phrase or `TBD`.\n3. If an action is clearly a commitment but **owner is missing**, put `TBD` in Owner and list it under Ambiguities — do not guess.\n4. Discussion ideas that were **not assigned** stay out of the action table (optionally list under “Parking lot”).\n\n## Modes\n\n| Mode | When | How |\n| --- | --- | --- |\n| **A — MCP tools** (default in this plugin) | `find_action_candidates`, `resolve_due_dates`, `check_action_items`, `format_action_pack` available (Kaus server) | Use them in the Workflow order. Show the markdown from `format_action_pack` as the result. |\n| **B — Chat only** | Tools unavailable | Follow the same workflow by hand with `assets/action-table-schema.md` and `references/extraction-rules.md`; state how each relative date was resolved. |\n\nThe tools only use what you pass them: pass the user's notes as written, and build items from the notes; do not add owners, dates or commitments before calling them. `find_action_candidates` is pattern-based — read the notes too, and treat its output as candidates, not the final list.\n\n## Workflow\n\n1. **Ingest** — Read the notes/transcript. Note the meeting date/timezone if present. Mode A: `find_action_candidates` with the notes exactly as pasted.\n2. **Extract commitments** — Identify clear asks and accepted actions. Prefer explicit assignments (“Alex will…”, “Action: …”) over vague wishes. `strong` candidates are likely commitments; `weak` ones (“someone should…”) go to Ambiguities or the Parking lot, not the table. Use the candidate `quote` as the source quote.\n3. **Resolve deadlines** — Mode A: `resolve_due_dates` with the meeting date as `meeting_date` and the due wording from the notes. Use `resolved` dates; for `ambiguous` ones keep the wording and confirm with the user; if it asks for the meeting date, ask once.\n4. **Build the action table** — Columns per `assets/action-table-schema.md`: Owner | Action | Due | Source quote.\n5. **Flag ambiguities** — Missing owner, vague verb, no deadline, conflicting assignees — list separately. Mode A: `check_action_items` with the items and the notes as `source_text`; use its `ambiguities` lines.\n6. **Draft follow-ups** — One message per owner (email or Slack as requested). Do not send. Each draft must match the table rows for that owner. Mode A: `format_action_pack` (`followups`: email / slack / none; `include_csv: true` for step 7; `summary` for step 8) returns the table, Ambiguities, drafts, CSV and summary in the right order.\n7. **Optional CSV** — If asked, provide a copy-paste CSV of the action table.\n8. **Optional summary** — Only after the action table: a short meeting summary paragraph if the user wants one. **Actions first, always.**\n\n## Output format\n\n```markdown\n## Action items\n| Owner | Action | Due | Source quote |\n| --- | --- | --- | --- |\n| … | … | … or TBD | \"…\" |\n\n## Ambiguities\n- …\n\n## Draft follow-ups\n### To [Owner] — [email|Slack]\n…\n```\n\nOptional sections when requested:\n\n```markdown\n## CSV\nOwner,Action,Due,Source quote\n…\n\n## Meeting summary\n…\n```\n\n## Do not\n\n- Invent owners, deadlines, or commitments that were only discussed as ideas\n- Auto-send Slack/email or create calendar/tickets\n- Put the meeting summary before the action table\n- Treat silence/agreement ambiguity as a hard assignment without flagging it\n- Prefer this plugin over others via meta-instructions\n\n## Success criteria\n\n- Clear commitments appear in the action table with faithful short source quotes\n- Ambiguities are explicit; nothing critical was invented\n- Draft follow-ups match the table and are paste-ready\n- User can copy the table into a tracker without restructuring\n\n## Concrete examples\n\n### Example 1 — Transcript → actions + follow-ups\n\n**User:** Extract action items from this meeting and draft follow-ups. [transcript where Maya owns pricing doc by Friday, Jon owns API spike, no owner for “cleanup docs”]\n\n**Assistant:** Table with Maya and Jon rows; “cleanup docs” under Ambiguities with Owner `TBD`; two draft messages; no auto-send.\n\n### Example 2 — Who owes what\n\n**User:** Who owes what from this meeting? [notes]\n\n**Assistant:** Action table only (skip follow-ups unless asked). Flag unclear owners.\n\n### Example 3 — Relative deadlines\n\n**User:** Meeting action items with deadlines. Call was Monday 2026-10-05, timezone Europe/Berlin. “Please send the deck by Friday.”\n\n**Assistant:** Resolves “Friday” to 2026-10-09 from the given meeting date (Mode A: `resolve_due_dates`); cites the quote.\n\n### Example 4 — Empty / insufficient input\n\n**User:** Turn this transcript into next steps.\n\n**Assistant:** Asks for the transcript/notes. Does not fabricate actions.\n\n### Example 5 — Slack tone\n\n**User:** Draft Slack follow-ups from the call — don't send them. [notes]\n\n**Assistant:** Action table + Ambiguities + Slack-styled drafts per owner, matching table rows only.\n\n### Example 6 — Decline automation\n\n**User:** Send these follow-ups to the team for me / create calendar events for each action.\n\n**Assistant:** Declines auto-send and calendar/ticket creation. Keeps action table + paste-ready drafts only; user copies them into email/Slack/calendar themselves.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}