agentleFS
philpalmieriphilpalmieri/engineering-manager-skills/skills/management/today-priorities/SKILL.md

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.

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
  1. Distinctive:

    Check what's already scheduled (meetings, 1:1s, deadlines) and any existing todos or focus items.

    line 23
  2. Distinctive:

    Search the vault for unchecked tasks with priority signals:

    line 27
  3. Very specific:

    Search locations: People/, Projects/, Dailies/ (last 3-5 days), Areas/

    line 38
  4. Very specific:

    Read last 3 daily notes for open - [ ] items that haven't been completed.

    line 42
  5. Distinctive:

    Add a "Today's Priority Focus" section to today's daily note with a live query block:

    line 63
  6. Distinctive:

    When a task is completed, the user checks it off normally

    line 89
  7. Very specific:

    Only add ➡️ arrows when the user confirms keeping the item for another day (not automatically)

    line 91
  8. Very specific:

    Place ➡️ markers before the #today tag for readability

    line 92
  9. Very specific:

    When removing #today, also remove all ➡️ markers

    line 93
  10. Very specific:

    If items tagged #today are found on previous days' dailies (not yet rolled over), present them:

    line 97
  11. Very specific:

    Do not remove #today tags without asking.

    line 101

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-day orchestration (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:

SignalMeaning
⏫ or 🔺High priority marker
📅 YYYY-MM-DDDue date (flag if today or overdue)
⏳ YYYY-MM-DDScheduled date (flag if today)
#followupNeeds follow-up action
#figureoutNeeds investigation/decision
#todayAlready 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

  • #today is 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 #today tags (from previous days) are handled by the task-rollover skill
  • Only add ➡️ arrows when the user confirms keeping the item for another day (not automatically)
  • Place ➡️ markers before the #today tag 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.