agentleFS
bradautomatesbradautomates/second-brain/.claude/skills/today/SKILL.md

today

Skill217 starsChanged 8 months agoMITView on GitHub

Generate daily plan from due tasks and active projects. Part of chief-of-staff vault system.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use update and start.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    update

    Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

    Also in 3 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 7

    Distinctive

    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
  1. Very specific:

    Check if daily/YYYY-MM-DD.md exists - if so, read it first

    line 12
  2. Distinctive:

    If no tasks found for today/overdue, grep for dates through end of week

    line 16
  3. Distinctive:

    If still none, grep to find the next earliest due date

    line 17
  4. Distinctive:

    Read only the matching task files

    line 18
  5. Very specific:

    Run git log --since="midnight" --grep="cos:" --oneline for today's activity

    line 20
  6. Very specific:

    Create or update daily/YYYY-MM-DD.md

    line 21
  7. Very specific:

    All tasks have due: YYYY-MM-DD in frontmatter.

    line 25
  8. Distinctive:

    Only read files returned by grep.

    line 38
  9. Distinctive:

    When the daily file already exists:

    line 42
  10. Very specific:

    Keep any [x] completed items as-is

    line 43
  11. Distinctive:

    Keep any manually added items (not from vault tasks)

    line 44
  12. Distinctive:

    Add new tasks from vault that aren't already present

    line 45

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “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 - Daily Planning

Generate today's plan from vault contents.

Steps

  1. Check if daily/YYYY-MM-DD.md exists - if so, read it first
  2. Find tasks by due date using grep (never glob all tasks):
    • Grep for due: YYYY-MM-DD (today's date) → Due Today
    • Grep for dates before today → Overdue
    • If no tasks found for today/overdue, grep for dates through end of week
    • If still none, grep to find the next earliest due date
  3. Read only the matching task files
  4. Grep projects/*.md for status: active, read those files
  5. Run git log --since="midnight" --grep="cos:" --oneline for today's activity
  6. Create or update daily/YYYY-MM-DD.md

Task Discovery (grep-first approach)

All tasks have due: YYYY-MM-DD in frontmatter. Use grep to find relevant tasks efficiently:

# Today's tasks (replace with actual date)
grep -l "due: 2026-01-23" tasks/*.md

# Overdue: grep for each date before today, or use date range pattern
grep -l "due: 2026-01-2[0-2]" tasks/*.md  # dates 20-22 if today is 23rd

# This week: grep for dates through end of week
grep -l "due: 2026-01-2[3-9]" tasks/*.md  # adjust pattern for week

Only read files returned by grep. Never glob and read all task files.

Update Behavior

When the daily file already exists:

  • Keep any [x] completed items as-is
  • Keep any manually added items (not from vault tasks)
  • Add new tasks from vault that aren't already present
  • Refresh the Recent Activity section with latest git log
  • Preserve any custom sections added by user

Output Format

---
type: daily
date: YYYY-MM-DD
---

## Due Today
- [ ] Task items from tasks/ with today's due date

## Overdue
- [ ] Tasks past due (X days overdue)

## Active Projects
- Project Name (next: next action from file)

## Recent Activity
- Items from git log

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.