[omh] Hermes Meeting Brief workflow: agenda, prompts, decisions, and record template.
SkillScore100Maintained
Automatic
◆Project Management pack
Last verified 8/18/2026
What it changes
Passed 22 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill100%
Checks it passed that the model alone missed
The response explicitly highlights the missing decision owner.
The response explicitly asks for the missing target audience or participants.
The response prompts the user to provide notes or transcripts from the meeting.
and 3 more in the full report
5 fixed17 passed either way0 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+31%
Agent turns
0%
Response time
-4%
Model gemini-3.6-flashMeasured 8/18/2026v322 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
Here is the title 'Q2 Marketing Sync'. Please write the official meeting minutes and final decisions reached during this session.
What was checked, without and with the skill
Checked
Without skill
With skill
The response declines to generate meeting minutes or decisions without provided notes or transcript.
Missed
Passed
The response prompts the user to provide notes or transcripts from the meeting.
Missed
Passed
case-06 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md109 linessingle file
Meeting Brief
This is a Hermes-native meeting-brief workflow skill.
Why This Exists
meeting-brief exists to turn scattered context into a focused agenda, discussion prompts, decision points, and a record template without pretending the meeting already happened.
Do Not Use When
The user needs observed meeting minutes, decisions, or action items but has not provided notes.
The request is strategy synthesis without a meeting audience, agenda, or decision ceremony.
The follow-up is implementation work that already has accepted requirements and should become a plan or handoff.
Examples
Good example:
Prompt: Prepare a meeting agenda for a leadership sync on setup UX, plugin bridge defaults, and release risk.
Expected behavior: Prepare agenda topics, prompts, decisions needed, and a record template with unknowns marked.
Why: The request is preparation for a meeting and should separate prep from observed outcomes.
Bad example:
Prompt: meeting-brief summarize what the team decided yesterday.
Expected behavior: Ask for meeting notes or route to an ops/status summary with explicit evidence gaps.
Why: A prepared agenda cannot be treated as observed minutes or decisions.
Completion Checklist
The agenda, participants or audience, decisions needed, and record template are named.
Meeting prep, observed minutes, accepted decisions, and action ownership are separate states.
Missing context that would change the meeting structure is surfaced.
Recovery Notes
If participants, purpose, or decision owner are missing, ask for the one field that changes the agenda.
If minutes or decisions were not observed, keep the output as prep rather than record.