agentsclimarketplace
Sign in

Review daily todos

Skill yixin0829/semantic-obsidian/skills/review-daily-todos

Review recent Obsidian daily-note checkboxes, reconcile duplicate tasks against later completion evidence, annotate earlier instances with final completion dates, and add a categorized Daily Planning section to today's note. Use whenever the user asks to review, consolidate, deduplicate, carry forward, prioritize, or plan unresolved to-dos from recent daily notes.From its SKILL.md

Install
npx -y skills add yixin0829/semantic-obsidian --skill review-daily-todos

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.9 KB, as published. Nobody here has run it

Review Daily To-Dos

Turn recent daily-note task history into an accurate plan without confusing Obsidian's informational checkbox states for actionable work.

Workflow

  1. Read the vault's Obsidian Markdown To-Do Syntax.md note. Find it by basename if its folder casing or location differs.

  2. Determine the date range. Use the user-specified range; otherwise use the past 30 calendar days through today, inclusive.

  3. Extract checkbox entries with:

    uv run python <skill-dir>/scripts/extract_daily_checkboxes.py --vault <vault-root> --days 30 --today YYYY-MM-DD

    Resolve <skill-dir> to this skill's directory. The script's status classes are preliminary; the vault's syntax note is authoritative.

  4. Review candidates chronologically with their nearby prose, headings, parent tasks, links, and later occurrences.

  5. Reconcile repeated tasks and update prior instances only when later evidence supports the result.

  6. Group the remaining actionable tasks and add or update ### Daily Planning in today's daily note.

  7. Verify the edits with a fresh extraction and a diff.

Interpret Checkbox States Semantically

First use regex to collect checkbox-shaped entries, then distinguish task states from informational states.

  • Recognize task checkboxes under -, *, +, and numbered Markdown list markers.
  • Carry forward actionable states such as [ ], [/], [>], and [<].
  • Treat [x] as completed and [-] as cancelled.
  • Exclude informational or issue markers such as [!], [*], [I], [i], [?], [p], and [f] unless the vault's syntax note explicitly defines them as actionable.
  • Do not infer actionability merely because a line matches - [.].
  • Ignore checkbox examples inside fenced code blocks.

Reconcile Duplicates

Process occurrences from newest to oldest. Use these signals:

  1. Exact issue ID, canonical wikilink target, or distinctive URL.
  2. Same normalized task wording and intended outcome.
  3. Supporting context such as ownership, a linked deliverable, a completion statement, or a later note saying the work shipped.

The latest checkbox alone is not always sufficient. Read surrounding prose and later related entries before deciding.

  • If a later occurrence is completed, mark matching earlier actionable instances [x] and append ✅ YYYY-MM-DD.
  • Prefer an explicit completion date. Otherwise use the date of the evidence-bearing daily note.
  • Preserve the original wording, wikilinks, metadata, indentation, and context.
  • Do not propagate completion across merely related tasks or ambiguous paraphrases.
  • When evidence is uncertain, leave the earlier task unchanged and keep the latest actionable instance in the plan.

Build Today's Daily Plan

Place the section under ## Daily Log, before timed log entries. Do not modify ## Priority, ## Backlog, task query blocks, or unrelated daily-note content.

Use exactly:

### Daily Planning
#### Main Deliveries
- [ ] ...

#### Knowledge Work and Learnings
- [/] ...

#### Helping Others and Side Projects
- [>] ...

Classification guidance:

  • Main Deliveries: primary business outcomes, customer commitments, assigned bugs, release work, and owned feature delivery.
  • Knowledge Work and Learnings: reading, research, deliberate practice, and themed learning.
  • Helping Others and Side Projects: enablement, favors, automations, workshops, personal tasks, and work owned primarily for someone else.

Preserve meaningful hierarchy. Keep dependent tasks nested under their parent. Carry forward explicit ownership, intended outcome, and useful links when source context makes them clearer. Do not invent context or duplicate a task across categories.

Keep all three category headings even when one has no tasks. A stable structure makes the plan easier to scan and prevents an empty category from disappearing between reviews.

If today's note already has ### Daily Planning, update that section rather than adding another one. Remove stale entries only when this review establishes that they are completed, cancelled, duplicated, or non-actionable.

Verification

Before finishing, confirm:

  • every planned item has an actionable state under the vault's syntax
  • no completed, cancelled, informational, or fenced-example checkbox was carried forward
  • completion propagation has concrete later evidence and the correct final date
  • duplicates appear once in today's plan
  • parent-child structure and useful context are preserved
  • only intended historical task lines and today's Daily Planning section changed

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.