morning-routine
Skill22 starsChanged 3 months agoMITView on GitHub
Run the complete start-of-day setup in one pass: roll over unfinished Obsidian tasks to today's daily note, sync open GitHub PRs that need your attention, and sweep Dependabot/Renovate PRs to clear safe patch bumps. Use when the user says "start my day", "morning routine", "set up my day", or when a scheduled morning job fires.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- antoniolg/agent-kittheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- antoniolg/agent-kit★ 100same name
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 repository194 other files it gives its agents.
- 0-templateSkill
- ab-test-analyzerSkill
- academy-guideSkill
- add-to-my-skillsSkill
- adr-authorSkill
- ai-tools-setupSkill
- algorithmic-artSkill
- api-and-interface-designSkill
- api-designerSkill
- api-docs-writerSkill
- apple-store-submitSkill
- aws-cost-optimizerSkill
- bash-script-hardeningSkill
- blog-post-writerSkill
- book-summarizerSkill
- branch-cleanupSkill
- brand-copy-landingSkill
- brand-copySkill
- brand-designSkill
- brand-guidelinesSkill
- browser-testing-with-devtoolsSkill
- canvas-designSkill
- changelog-generatorSkill
- changelog-keeperSkill
- chart-chooserSkill
- ci-cd-and-automationSkill
- ci-fix-loopSkill
- claude-apiSkill
- cloudflare-block-countriesSkill
- coderabbitloopSkill
- code-review-and-qualitySkill
- code-reviewerSkill
- code-simplificationSkill
- codexloopSkill
- comms-notionSkill
- comms-slackSkill
- comms-whatsappSkill
- competitive-analysisSkill
- concept-explainerSkill
- constraint-driven-developmentSkill
- context-engineeringSkill
- context-repoSkill
- cover-letter-writerSkill
- crash-courseSkill
- cron-schedulerSkill
- data-digestSkill
- data-pipeline-architectSkill
- debug-detectiveSkill
- debugging-and-error-recoverySkill
- decision-matrixSkill
- dependabot-triageSkill
- dependency-upgraderSkill
- deprecation-and-migrationSkill
- dev-instantdbSkill
- discernment-nudgeSkill
- doc-coauthoringSkill
- dockerfile-proSkill
- docs-index-keeperSkill
- documentation-and-adrsSkill
- docxSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Run the three start-of-day workflows in sequence, then summarize what needs your attention today.
- Distinctive: line 44
If any required config is missing, ask once before starting.
- Very specific: line 54
Run olko:obsidian-task-rollover on the previous workday's note.
- Distinctive: line 65
After this phase, confirm:
- Distinctive: line 83
After this phase, count PRs written:
- Very specific: line 90
Run olko:dependabot-triage with patch-only auto-merge policy.
- Distinctive: line 106
If the count is 0, skip phase 3 and note it in the report.
- Distinctive: line 127
If a phase failed (auth expired, vault not found, network error), surface the error clearly rather than silently skipping that phase.
- Distinctive: line 134
Run the full flow and show the final report.
- Distinctive: line 137
No user prompt needed. Run all three phases silently and emit the report as the run's output.
- Very specific: line 141
If the user wants to re-sync only PRs mid-day: --skip-rollover --skip-dependabot.
≈ “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
🤖 Auto-generated by weekly-pattern-learner · obsidian-task-rollover, obsidian-pr-sync, and dependabot-triage all describe themselves as morning-routine steps but no meta-skill chains them into a single first-thing-of-day pass
Morning Routine
Run the three start-of-day workflows in sequence, then summarize what needs your attention today. Each phase is idempotent: re-running is safe.
Inputs
- VAULT_DAILY (required): absolute path to the Obsidian daily notes folder
- GH_USERNAME (required): GitHub login for PR filtering
- ORG_PREFIX (optional): org name to group as "Work" in the PR section
- --skip-rollover (optional): skip task rollover (e.g. Monday after a break)
- --skip-pr-sync (optional): skip GitHub PR sync
- --skip-dependabot (optional): skip Dependabot triage
If any required config is missing, ask once before starting. Don't abort midway.
Phase 1: Task rollover
Initialize the daily note path once, before any optional phase:
NOTE="${VAULT_DAILY}/$(date +%Y-%m-%d).md"Run olko:obsidian-task-rollover on the previous workday's note.
obsidian-task-rollover is an end-of-day migration skill: it copies unchecked tasks
from a given day's note into the next workday's note with a [>] marker. When invoked
here in the morning, it should operate on yesterday's (or the last workday's) note
so those unchecked tasks are pulled forward into today's note. If yesterday's note does
not exist, skip this step and note it in the report.
Skip if --skip-rollover is set, or if it's Monday and the user has explicitly
said they clear the board on Fridays.
After this phase, confirm:
grep -c "^\- \[ \]" "$NOTE" 2>/dev/null || echo "0" # open tasks today
grep -c "^\- \[>\]" "$NOTE" 2>/dev/null || echo "0" # migrated tasksRecord counts for the final report.
Phase 2: PR sync
Run olko:obsidian-pr-sync.
This fetches all open GitHub PRs where the user is assignee or review-requested,
filters out bots and drafts, and writes or replaces the ## PRs to review section
in today's daily note. PRs are grouped into Work (ORG_PREFIX org) and Personal.
Skip if --skip-pr-sync is set.
After this phase, count PRs written:
grep -c "^\- \[ \] \[" "$NOTE" 2>/dev/null || echo "0"Phase 3: Dependabot triage (quick sweep)
Run olko:dependabot-triage with patch-only auto-merge policy.
This auto-approves and merges safe patch bumps whose CI is green, flags major
upgrades for human review, and posts a digest. The patch-only policy means no
minor or major bumps are merged automatically, just the safest dependency noise.
Skip if --skip-dependabot is set, or if there are no open dependency PRs:
gh pr list --state open \
--json author --jq '
[.[] | select(.author.login | test("dependabot|renovate"; "i"))]
| length
' 2>/dev/nullIf the count is 0, skip phase 3 and note it in the report.
Final report
Print a compact brief suitable for the start of the day:
Morning routine complete: YYYY-MM-DD
Tasks: N open today (M carried over from yesterday)
PRs: X work PRs, Y personal PRs → see ## PRs to review in today's note
Dependabot: Z merged (patch, CI green), W flagged for review
Today's top 3:
[read from ## Top 3 for today section if populated, else print "(not filled in yet)"]
Flagged for you:
- [PRs older than 7 days ⚠️ from the PR sync, if any]
- [Major Dependabot bumps flagged for human decision, if any]If a phase failed (auth expired, vault not found, network error), surface the error clearly rather than silently skipping that phase.
Invocation patterns
Manual (user-triggered): User says "start my day", "run morning routine", or "set up today's note". Run the full flow and show the final report.
Scheduled (cron / CCR): No user prompt needed. Run all three phases silently and emit the report as the run's output. Useful as a pre-meeting brief or as a first message in a new session.
Partial run:
If the user wants to re-sync only PRs mid-day: --skip-rollover --skip-dependabot.
Chaining
| Before this skill | After this skill |
| (none, start of session) | Work the PR queue (olko:pr-to-green on flagged items) |
| (none) | olko:dependabot-triage with patch-and-minor if the quick sweep flagged many |
olko:obsidian-task-rollover alone | nothing: this skill already calls 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.

