meeting-action-items

Parse the transcript to identify explicit commitments, then normalize each into structured fields: outcome, owner, due date, dependency, acceptance criteria, and source reference. Flag any field that cannot be confidently assigned as unresolved rather than inventing values.

Only assign owners when the transcript explicitly names a person responsible for the commitment. If no owner is stated, mark the field as unresolved and surface it for confirmation rather than defaulting to a team or role.

Yes, it searches the user's tracker connector such as Notion or GitHub Issues for matching open items before creating anything. Recurring meetings often produce duplicate tickets, so reconciliation distinguishes proposed creates from updates.

Inventing deadlines from urgency language like 'ASAP' or 'soon' is a common pitfall. The skill requires explicit dates from the transcript and marks missing deadlines as unresolved rather than guessing.

Do not use this skill to retrieve meeting recordings or transcripts from platforms like Microsoft Teams. Use a connector skill such as teams-meeting-pipeline first, then apply this skill once the transcript content is available.