today-priorities
Skill1 starsChanged 6 months agoMITView on GitHub
Scan the Obsidian vault for high-priority open items and organize them into today's focus list. Handles priority markers, overdue items, stale carry-overs, and the #today tagging system. Use when asked about today's priorities or focus.
In this repository30 other files it gives its agents.
- setupSkill
- enrich-prsSkill
- epic-cleanupSkill
- epic-overviewSkill
- oncall-reviewSkill
- sprint-managementSkill
- sprint-statusSkill
- team-activitySkill
- team-data-syncSkill
- direct-report-prepSkill
- interview-analysisSkill
- interview-prepSkill
- peer-prepSkill
- project-statusSkill
- team-analysisSkill
- weekly-snippetSkill
- bus-factorSkill
- contribution-velocitySkill
- nine-boxSkill
- project-people-mapSkill
- review-cardsSkill
- review-cyclesSkill
- review-networkSkill
- team-health-reportSkill
- task-rolloverSkill
- context-checkSkill
- prep-my-daySkill
- initiative-breakdownSkill
- product-briefSkill
- technical-deep-diveSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Check what's already scheduled (meetings, 1:1s, deadlines) and any existing todos or focus items.
- Distinctive: line 27
Search the vault for unchecked tasks with priority signals:
- Very specific: line 38
Search locations: People/, Projects/, Dailies/ (last 3-5 days), Areas/
- Very specific: line 42
Read last 3 daily notes for open - [ ] items that haven't been completed.
- Distinctive: line 63
Add a "Today's Priority Focus" section to today's daily note with a live query block:
- Distinctive: line 89
When a task is completed, the user checks it off normally
- Very specific: line 91
Only add ➡️ arrows when the user confirms keeping the item for another day (not automatically)
- Very specific: line 92
Place ➡️ markers before the #today tag for readability
- Very specific: line 93
When removing #today, also remove all ➡️ markers
- Very specific: line 97
If items tagged #today are found on previous days' dailies (not yet rolled over), present them:
- Very specific: line 101
Do not remove #today tags without asking.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Today's Priorities
Scan the vault for actionable items and organize them into a prioritized focus list for today.
When to use
- "Today's priorities", "what should I focus on today", "prep today tasks"
- As part of
prep-my-dayorchestration (after task rollover and 1:1 prep)
Process
Step 1: Read today's daily note
Check what's already scheduled (meetings, 1:1s, deadlines) and any existing todos or focus items.
Step 2: Scan for high-priority open items
Search the vault for unchecked tasks with priority signals:
| Signal | Meaning |
⏫ or 🔺 | High priority marker |
📅 YYYY-MM-DD | Due date (flag if today or overdue) |
⏳ YYYY-MM-DD | Scheduled date (flag if today) |
#followup | Needs follow-up action |
#figureout | Needs investigation/decision |
#today | Already tagged as today's priority |
Search locations: People/, Projects/, Dailies/ (last 3-5 days), Areas/
Step 3: Check for carry-over items
Read last 3 daily notes for open - [ ] items that haven't been completed. Items appearing in multiple consecutive dailies are likely important and stuck.
Step 4: Check for time-sensitive items
- Deadlines within 48 hours
- Items tied to today's meetings (prep work, deliverables)
- Anything in People files tied to today's 1:1s
Step 5: Present grouped by urgency
Present items to the user in three groups:
- Must do — deadlines, meeting prep, overdue items
- Should do — follow-ups, active project work
- If time allows — nice-to-haves, exploration items
Step 6: Tag confirmed items
For items the user confirms as today's priorities, add #today to the task line in its source file. Tasks are never moved between files for this purpose; the tag is added in place.
Step 7: Write Priority Focus section
Add a "Today's Priority Focus" section to today's daily note with a live query block:
## Today's Priority Focus
\`\`\`dataviewjs
dv.taskList(
dv.pages('"People" or "Projects" or "Dailies" or "Areas"')
.where(p => p.file.path !== dv.current().file.path)
.file.tasks
.where(t => !t.completed && t.text && t.text.includes("#today"))
.sort((a, b) =>
((b.text || "").match(/➡️/g) ?? []).length -
((a.text || "").match(/➡️/g) ?? []).length
)
)
\`\`\`This DataviewJS query surfaces all open #today items across the vault, sorted by rollover count.
The #today tag system
#todayis added in place on the original task line wherever it lives- Tasks are never duplicated or moved between files for priority tracking
- The DataviewJS query in the daily note is the live view
- When a task is completed, the user checks it off normally
- Stale
#todaytags (from previous days) are handled by thetask-rolloverskill - Only add
➡️arrows when the user confirms keeping the item for another day (not automatically) - Place
➡️markers before the#todaytag for readability - When removing
#today, also remove all➡️markers
Stale #today cleanup
If items tagged #today are found on previous days' dailies (not yet rolled over), present them:
These N items still have #today from yesterday. Keep them for today, or remove the tag?
Do not remove #today tags without asking.
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.

