morning-ritual
Skill2 starsChanged 8 months agoMITView on GitHub
Use when starting your workday with a structured Obsidian task briefing - automatically loads obsidian-cli and obsidian-markdown skills to parse vault tasks, surface urgent/due items, and identify 1-5 MIT focus tasks. Triggers on "Good morning", "Morning briefing", "Daily Kickoff", "What should I work on today
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- julweber/ai_agent_skillsword for word, first seen Mar 20, 2026
Other versions1 project uses a version of this.
Word for word · 1
- julweber/ai_agent_skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-agent-skills-assistantSkill
- ansibleSkill
- artificial-analysisSkill
- cavemanSkill
- claude-cliSkill
- code-doctorSkill
- code-summarizerSkill
- codex-cliSkill
- concourse-ciSkill
- dev-brainstormingSkill
- docker-cliSkill
- file-organizerSkill
- frontend-web-developerSkill
- github-actions-cicdSkill
- github-cliSkill
- gitlab-ci-cdSkill
- grill-meSkill
- gtd-assistantSkill
- herdr-cliSkill
- hf-cliSkill
- karpathy-guidelinesSkill
- kestraSkill
- list-large-filesSkill
- list-most-intensive-processesSkill
- llama-cppSkill
- llm-wikiSkill
- mermaidSkill
- obsidian-masterSkill
- obsidian-open-loops-collectorSkill
- opencode-agent-creatorSkill
- opencode-cliSkill
- pi-cliSkill
- pi-subagents-masterSkill
- planka-development-flowSkill
- plnk-cliSkill
- ponytailSkill
- product-prd-brainstormingSkill
- python-api-developerSkill
- ralph-prd-converterSkill
- ralph-prd-generatorSkill
- release-managementSkill
- rest-testsuite-skillSkill
- skill-loaderSkill
- design-taste-frontendSkill
- terraformSkill
- tmux-coderSkill
- tmux-specialistSkill
- trello-cliSkill
- tts-conversationSkill
- uvSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 15 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Run in this order. Be fast — use parallel reads where possible.
- Very specific: line 36
If you have the obsidian-cli agent skill: load the obsidian-cli skill
- Distinctive: line 49
Use the consolidated script to query both local vault calendars and external ICS/CalDAV feeds in one pass:
- Distinctive: line 102
Prefer tasks that are actionable (not vague ideas)
- Distinctive: line 115
If the user asks to save/log the briefing, create a note:
- Distinctive: line 121
Use today's date. Store in the vault root or wherever the user prefers.
- Distinctive: line 191
After presenting the briefing, offer these options:
- Distinctive: line 206
Always confirm before marking done.
- Distinctive: line 216
If the user asks for an evening review:
- Distinctive: line 221
Ask: "What's the one thing for tomorrow?"
- Distinctive: line 226
When a user needs more than just daily tasks — perhaps they feel overwhelmed, need to understand their full backlog, or want pattern …
- Very specific: line 237
When these triggers are detected, switch to the gtd-assistant workflow:
- Very specific: line 241
Follow Phase 1 → Phase 2 → Phase 3 as defined in gtd-assistant.
- Distinctive: line 244
All open tasks by domain
- Very specific: line 253
If you see [⚠️ Obsidian CLI not found — using file-based fallback]:
- Distinctive: line 259
Ensure Obsidian is running with the Full Calendar plugin loaded
- Distinctive: line 260
Check that ICS sources are configured in plugin settings
- Distinctive: line 261
Verify network connectivity to calendar URLs
- Very specific: line 270
Use today's date (date +%Y-%m-%d) to detect overdue tasks
- Distinctive: line 271
Keep the briefing scannable — no walls of text, max 5 items per group shown
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Morning Ritual Workflow
A daily work kickoff ritual that surfaces what matters most and helps the user start with intention and clarity — not chaos.
When to Use
Activate when the user says things like:
- "Good morning" / "Morning briefing"
- "What should I work on today?"
- "Start my day" / "Daily kickoff"
- "What's on my plate?"
- "Morning ritual"
Vault Configuration
| Setting | Value |
| Vault path | $HOME/main_vault |
| Obsidian CLI | obsidian |
Directory Structure
The vault should have:
00-Tasks/*.md— categorized task definitions01-Calendars/*.md— date-tagged calendar event files
The Morning Ritual Workflow
Run in this order. Be fast — use parallel reads where possible.
Step 0 - Load Obsidian CLI Skills first
- If you have the
obsidian-cliagent skill: load theobsidian-cliskill - If you have the
obsidian-masteragent skill: load theobsidian-masterskill
Note: This skill no longer requires the obsidian skill to be loaded — it includes a file-based fallback using grep/find when the obsidian CLI is unavailable.
Step 1 - Get current date
date +%Y-%m-%dStep 2 — Query Calendar Events
Use the consolidated script to query both local vault calendars and external ICS/CalDAV feeds in one pass:
# Run the consolidated calendar query script
python3 "$HOME/main_vault/.pi/skills/morning-ritual/scripts/query_calendars.py" --days 6Script features:
- Queries local vault calendars via obsidian CLI or file-based grep fallback
- Fetches external ICS URLs from Full Calendar plugin settings
- Parses and normalizes all events to Europe/Berlin timezone
- Separates into "today" vs "upcoming" sections
- Returns structured output ready for embedding
Modes:
# Auto-detect (try obsidian, fallback to file-based)
python3 query_calendars.py --mode auto
# Local-only (no obsidian required)
python3 query_calendars.py --mode local
# External-only (requires obsidian for plugin access)
python3 query_calendars.py --mode externalStep 3 — Collect Open Tasks
obsidian tasks todo verbose=false format=jsonParse the JSON output. Filter only incomplete tasks (lines starting with - [ ]).
Group them:
- 🔥 Urgent / High Priority: tasks with
⏫or🔺or#urgentor overdue dates - 💼 Work: tasks with
#work,#task/work, or from10 - Tasks - Beruflich.md - 🎵 Music & Creative: tasks with
#music, from07 - Tasks - Music.md - 🏠 Personal: tasks with
#privat,#haus,#task/haus, from06 - Tasks - Privat.md - 📥 Inbox: everything else from
01 - Tasks - Inbox.mdnot yet categorized
Step 4 — Check for Due Today / Overdue
Scan for tasks containing today's date (format: 📅 YYYY-MM-DD) or past dates that haven't been completed.
Flag these as ⚠️ Due Today or 🚨 Overdue.
Step 5 — Pick the MIT (Most Important Tasks)
Based on the collected tasks, suggest 1–5 MIT (Most Important Tasks) for today. Use this logic:
- Overdue items first
- Items marked
⏫(urgent) or with today's date - Work tasks over personal tasks (unless personal items are urgent)
- Prefer tasks that are actionable (not vague ideas)
Present these as the "Today's Focus" block — the 1–5 things the user should commit to finishing today.
Step 6 — Quick Stats
Show a brief summary:
- Total open tasks (across all files)
- How many are work vs personal vs creative
- Anything overdue
Step 7 — Optional: Save Daily Briefing
If the user asks to save/log the briefing, create a note:
obsidian create name="Daily Briefing YYYY-MM-DD" content="[full briefing content]"Use today's date. Store in the vault root or wherever the user prefers.
Output Format
## ☀️ Morning Briefing — [Day, Date]
### 📅 Today's Events ([n events])
- [⏰ HH:MM – HH:MM] **Event Title** — *location/notes*
- [all-day] **Event Title** — *location/notes*
---
### 🎯 Today's Focus (MIT)
1. [Most important task]
2. [Second task]
3. [Third task — optional]
---
### 🚨 Overdue / Due Today ([n items])
- [ ] task — *[file/domain]*
- ...
---
### 💼 Work ([n open])
Top items:
- [ ] task
- ...
### 🎵 Music & Creative ([n open])
Top items:
- [ ] task
- ...
### 🏠 House & Personal ([n open])
Top items:
- [ ] task
- ...
### 📥 Inbox ([n open])
Top items:
- [ ] task
- ...
---
### 🔜 Upcoming Events (Next 5 Days)
**[Day, Date]**
- [⏰ HH:MM – HH:MM] **Event Title** — *location/notes*
**[Day, Date]**
- [⏰ HH:MM – HH:MM] **Event Title** — *location/notes* (Google)
---
### 📊 Stats
- Total open: [n] tasks
- Work: [n] | Music: [n] | Personal: [n] | Inbox: [n]
- Overdue: [n]
- Events this week: [n] (local: [n], external: [n])
---
*Ready to go! Type "done [task]" to mark something complete, or "focus [area]" to dive into a domain.*Interaction After Briefing
After presenting the briefing, offer these options:
- "done [task name]" — mark a task complete via Obsidian CLI
- "focus work" / "focus music" / "focus inbox" — show full list for a domain
- "add task [text]" — add a new task to the inbox
- "save briefing" — save the briefing as a note
- "Evening review" — close the day (summarize what got done, what's still open)
- "Deeper analysis?" or "Full review" — call
gtd-assistantfor comprehensive view including dangling thoughts and stub notes
Marking Tasks Done
# Mark a specific task done in a file
obsidian tasks:update file="00-Tasks/01 - Tasks - Inbox.md" line=[LINE_NUMBER] status=xAlways confirm before marking done.
Adding a New Task
obsidian append file="00-Tasks/01 - Tasks - Inbox.md" content="\n- [ ] [new task text]"Evening Review (optional extension)
If the user asks for an evening review:
- Re-run task collection
- Compare with morning MIT — were they completed?
- Present "Wins today" (tasks completed since morning)
- Show what rolled over
- Ask: "What's the one thing for tomorrow?"
- Optionally save an evening note
Deeper Analysis: Calling gtd-assistant
When a user needs more than just daily tasks — perhaps they feel overwhelmed, need to understand their full backlog, or want pattern recognition across their vault:
Trigger Phrases
- "What's really blocking me?"
- "I need a full review of my vault"
- "Help me understand what's unfinished"
- "Open loops sweep" (or similar GTD terminology)
- "Deeper analysis" after morning briefing
- "Weekly/Monthly review"
Implementation
When these triggers are detected, switch to the gtd-assistant workflow:
"I'll now run a full GTD sweep using the gtd-assistant skill."
Follow Phase 1 → Phase 2 → Phase 3 as defined in gtd-assistant. The current conversation context carries over — no data needs to be passed explicitly.
The gtd-assistant will return a more detailed report including:
- All open tasks by domain
- Dangling thoughts from notes
- Stub notes requiring attention
- GTD analysis insights on consolidation opportunities
- Pattern recognition across the vault
Troubleshooting
Obsidian CLI Not Available
If you see [⚠️ Obsidian CLI not found — using file-based fallback]:
- The script will automatically use
grep/findto scan markdown files - Local calendar files must contain date strings like
2026-05-16 - External calendar queries require obsidian CLI for Full Calendar plugin access
External Calendar Events Not Showing
- Ensure Obsidian is running with the Full Calendar plugin loaded
- Check that ICS sources are configured in plugin settings
- Verify network connectivity to calendar URLs
Script Dependencies
icalendarpackage:pip install icalendar- Python 3.9+ required for
zoneinfomodule
Performance Notes
- Open task count is typically > 300 — always parse with regex
^- \[ \]for open items - Use today's date (
date +%Y-%m-%d) to detect overdue tasks - Keep the briefing scannable — no walls of text, max 5 items per group shown
- Suggest MIT based on signal (emoji priorities, dates, tags) — don't overthink it
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

