Summary
extract_next_meeting falls back to matching any ISO-like date after explicit next meeting markers fail. This causes current meeting dates, such as Meeting date: 2024-01-01, to be reported as the next meeting.
Tested on OpenBMB/PilotDeck main at 0907c5c9ae66cc155f36775fc8472b3ea621880d.
Code path
skills/meeting-recorder-assistant/scripts/meeting_minutes.py:171 defines extract_next_meeting.
skills/meeting-recorder-assistant/scripts/meeting_minutes.py:174-176 first matches explicit next-meeting labels, then falls back to any ISO-like date.
skills/meeting-recorder-assistant/scripts/meeting_minutes.py:45 stores the result as next_meeting.
skills/meeting-recorder-assistant/scripts/meeting_minutes.py:218 renders a Next Meeting section when this value is present.
skills/meeting-recorder-assistant/SKILL.md:39-42 shows the public skill flow calling generate_minutes.
Steps to reproduce
Call:
extract_next_meeting("Meeting date: 2024-01-01\nAgenda: weekly review.\n")
Observed dynamic repro:
actual: "2024-01-01"
expected: None
Positive control:
extract_next_meeting("Next meeting: 2024-01-01\n")
returns "2024-01-01" as expected.
Expected behavior
A current meeting date should not be rendered as next_meeting unless the transcript explicitly labels it as a next/follow-up meeting.
Actual behavior
Any ISO-like date can populate next_meeting, which then appears under the generated ## Next Meeting section.
Existing coverage
I searched current issues and PRs for extract_next_meeting, next meeting, Meeting date, and meeting_minutes, and did not find an existing issue or PR covering this root cause. Open PRs do not modify skills/meeting-recorder-assistant/scripts/meeting_minutes.py.
Suggested fix
Remove the generic any-date fallback, or restrict extraction to explicit next/follow-up labels such as next meeting, follow-up meeting, and 下次会议. If fuzzy extraction is desired, return confidence or field provenance rather than directly rendering the value as Next Meeting.
Suggested tests
Meeting date: YYYY-MM-DD should return None.
会议日期:YYYY-MM-DD should return None.
Next meeting: YYYY-MM-DD should return the date.
下次会议:YYYY-MM-DD should return the date.
Submitted with Codex.
Summary
extract_next_meetingfalls back to matching any ISO-like date after explicitnext meetingmarkers fail. This causes current meeting dates, such asMeeting date: 2024-01-01, to be reported as the next meeting.Tested on
OpenBMB/PilotDeckmain at0907c5c9ae66cc155f36775fc8472b3ea621880d.Code path
skills/meeting-recorder-assistant/scripts/meeting_minutes.py:171definesextract_next_meeting.skills/meeting-recorder-assistant/scripts/meeting_minutes.py:174-176first matches explicit next-meeting labels, then falls back to any ISO-like date.skills/meeting-recorder-assistant/scripts/meeting_minutes.py:45stores the result asnext_meeting.skills/meeting-recorder-assistant/scripts/meeting_minutes.py:218renders aNext Meetingsection when this value is present.skills/meeting-recorder-assistant/SKILL.md:39-42shows the public skill flow callinggenerate_minutes.Steps to reproduce
Call:
Observed dynamic repro:
Positive control:
returns
"2024-01-01"as expected.Expected behavior
A current meeting date should not be rendered as
next_meetingunless the transcript explicitly labels it as a next/follow-up meeting.Actual behavior
Any ISO-like date can populate
next_meeting, which then appears under the generated## Next Meetingsection.Existing coverage
I searched current issues and PRs for
extract_next_meeting,next meeting,Meeting date, andmeeting_minutes, and did not find an existing issue or PR covering this root cause. Open PRs do not modifyskills/meeting-recorder-assistant/scripts/meeting_minutes.py.Suggested fix
Remove the generic any-date fallback, or restrict extraction to explicit next/follow-up labels such as
next meeting,follow-up meeting, and下次会议. If fuzzy extraction is desired, return confidence or field provenance rather than directly rendering the value asNext Meeting.Suggested tests
Meeting date: YYYY-MM-DDshould returnNone.会议日期:YYYY-MM-DDshould returnNone.Next meeting: YYYY-MM-DDshould return the date.下次会议:YYYY-MM-DDshould return the date.Submitted with Codex.