From devboy
Searches meeting notes by keyword, participant, host, or date range to surface a short, rankable hit list of matches for quick selection before transcript or task extraction.
npx claudepluginhub meteora-pro/devboy-tools --plugin devboyThis skill uses the workspace's default tool permissions.
Answer "which meeting did we talk about X?" without making the user scroll through a calendar. The skill narrows a corpus of meeting notes down to a short hit list the user can act on — drill-down into a single meeting's metadata is a follow-up step, and pulling the full transcript is the job of `meeting-transcript`.
Queries Fireflies.ai for meeting transcripts from Zoom, Teams, Google Meet; searches by keyword/date, extracts action items, and retrieves summaries.
Uses Glean's meeting_lookup tool to retrieve decisions, action items, attendees, transcripts from past meetings. For queries like 'what was decided' or 'meeting notes'.
Searches meeting transcripts and voice memos in Markdown files for topics, people, decisions, or ideas. Filters by type, date range, limits; JSON output with snippets and paths; optional QMD semantic search.
Share bugs, ideas, or general feedback.
Answer "which meeting did we talk about X?" without making the user scroll through a calendar. The skill narrows a corpus of meeting notes down to a short hit list the user can act on — drill-down into a single meeting's metadata is a follow-up step, and pulling the full transcript is the job of meeting-transcript.
meeting-to-tasks or meeting-transcript, confirm the target meeting id.If no search term is given — just a window or a participant — skip the keyword search and go straight to get_meeting_notes with the filter.
Use search_meeting_notes when the user supplied a topic. All filters (date range, participants, host) combine with the keyword on the provider side — there is no client-side filter.
devboy tools call search_meeting_notes '{
"query": "migration",
"from_date": "2026-03-01T00:00:00Z",
"to_date": "2026-04-17T00:00:00Z",
"limit": 20
}'
Dates are ISO 8601. The tool caps limit at 50 per call; paginate with offset if you need a deeper sweep.
devboy tools call get_meeting_notes '{
"from_date": "2026-04-10T00:00:00Z",
"participants": ["alice@example.com"],
"limit": 20
}'
Use this for "last N days" or "calls with Alice" — no keyword means do not invent one.
The provider returns meetings newest-first but is not topic-ranked. When several hits look plausible, resolve ties by:
summary, keywords, or topics_discussed, a meeting that hits multiple of them is a stronger match than one that mentions the term in passing.Present at most 5–10 candidates. If more exist, say so and offer to narrow by date or participant rather than dumping them all.
Once the user picks a hit, fetch its metadata for a short card — title, date, duration, participants, action-items count, a one-line summary:
devboy tools call get_meeting_notes '{
"from_date": "<date of the hit>",
"to_date": "<+1 day>",
"limit": 5
}'
(There is no single-meeting "get by id" helper — narrow the date window and match on id.)
meeting-transcript.