[omh] Morning brief SETUP (one-time) - connects mail and calendar MCP with read-and-draft-only scope and diff approval; produces the configuration, not the daily brief itself.
SkillScore73Maintained
Automatic
◆Personal Assistant pack
Last verified 8/18/2026
What it changes
Passed 15 of 21 test cases with the skill, and 6 of 21 without it.
Without skill27%
With skill73%
Checks it passed that the model alone missed
Routes the request to a mail-reading task
Confirms that draft creation is permitted
Asks the user to provide updated credentials
and 11 more in the full report
10 fixed6 passed either way6 still failing0 broke
Pass-rate lift
+45 pp
Tokens
+85%
Agent turns
0%
Response time
-43%
Model gemini-3.6-flashMeasured 8/18/2026v216 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
I'm in the middle of my workday and need to check my inbox right now to see if there are any urgent emails from my manager. Can you scan my unread messages immediately?
What was checked, without and with the skill
Checked
Without skill
With skill
Does not initiate the morning brief integration setup walkthrough
Passed
Passed
Routes the request to a mail-reading task
Missed
Passed
case-04 · 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
Morning Brief
This is a Hermes-native morning-brief workflow skill.
Why This Exists
morning-brief exists to connect mail and calendar access for an on-demand brief while keeping the connection strictly read and draft-only and the user's credentials unstored.
Do Not Use When
The user wants Hermes to check their email or calendar right now rather than set up the connection.
The connection is already configured and the user only wants today's brief, not a setup walkthrough.
The request needs a repository code change rather than a local MCP config edit.
Examples
Good example:
Prompt: connect my email for a morning brief — I want a daily summary of mail and calendar.
Expected behavior: Check the MCP prerequisite, diagnose the current connection, guide OAuth/token issuance, show the read/draft-only diff, and apply only after approval.
Why: The request is a mail/calendar integration setup and needs the shared setup contract plus the Send-permission guardrail.
Bad example:
Prompt: morning-brief: check my email for anything urgent.
Expected behavior: Route to a mail-reading task instead of starting a connection setup walkthrough.
Why: A one-off email check is a task request, not an integration setup request.
Completion Checklist
If a prerequisite is unmet, mark that item "not applicable" and continue with the rest of the guide instead of blocking or guessing.
Success is applicable-only: verification passes when every applicable item is confirmed complete, not when every possible item exists.
The connection is confirmed read and draft-only, with Send permission never enabled, before the brief is reported ready.
Recovery Notes
If the mail or calendar prerequisite is unmet, mark that surface "not applicable" and offer the brief scoped to whichever surface is connected.
If a pasted token fails validation, ask the user to reissue it rather than storing or retrying the same value silently.