agentleFS
Sign inStart free
siddhartpaisiddhartpai/vault-hooks/skills/vault-daily/SKILL.md

vault-daily

Skill0 starsChanged 39 days agoMITView on GitHub

Open, create, or update today's Obsidian daily note from Claude Code. Use when the user says "daily note", "log this", "add a task for today", "what did I do today", or asks to plan the day.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. meaningfy-ws/skillery★ 2same 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.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create the note with a # <date> heading if it does not exist.

    line 16
  2. Very specific:

    Keep these sections in this order: ## Plan, ## Notes, ## Claude activity.

    line 17

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

Daily note

Config lives in ~/.config/vault-hooks/config (keys: VAULT, DAILY_DIR, DAILY_FORMAT). Resolve today's note path with:

. ~/.config/vault-hooks/config; echo "$VAULT/$DAILY_DIR/$(date +"$DAILY_FORMAT").md"

Rules

  • Create the note with a # <date> heading if it does not exist.
  • Keep these sections in this order: ## Plan, ## Notes, ## Claude activity. The last one is written by the hooks. Do not rewrite it.
  • Tasks are - [ ] text. Mark done with - [x].
  • Append; never delete the user's text. Use the Edit tool for targeted inserts.
  • Link projects and people with [[wikilinks]].

Actions

  • "log X" -> append - HH:MM X under ## Notes.
  • "add task X" -> append - [ ] X under ## Plan.
  • "what did I do today" -> read the note and summarise the activity section in five lines.
  • "plan my day" -> read open tasks from the last three daily notes, propose a ## Plan with at most five tasks, then write it after the user agrees.

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.

Check your setup, free