agentleFS
jqaisystemsjqaisystems/jqai-ai-skills/skills/obsidian-daily-note/SKILL.md

obsidian-daily-note

Skill3 starsChanged 6 months agoMITView on GitHub

Create or append to today's daily note in an Obsidian vault from the terminal. Adds timestamped sections to the right dated file without overwriting anything, creating the note with a date heading if it does not exist yet. Use when the user says "daily note", "log this to today", "add to my daily note", or "note this down".

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    If no config file exists: check whether the current directory (or a parent) contains a .obsidian folder.

    line 22
  2. Distinctive:

    Never guess a vault path. Writing notes into the wrong directory is worse than asking once.

    line 25
  3. Very specific:

    If the file does not exist: create it with a # <date> heading, then the new section.

    line 34
  4. Distinctive:

    If the file already exists: read it first, then append the new section at the end.

    line 35
  5. Very specific:

    If the user separates a title from the body (for example with a |), use their title.

    line 46
  6. Distinctive:

    If the text starts with an obvious label ("Meeting with X:", "Reminder:"), use that.

    line 47
  7. Distinctive:

    Keep the user's text as written.

    line 50
  8. Distinctive:

    Never overwrite existing daily note content.

    line 58
  9. Distinctive:

    Never modify other notes in the vault.

    line 59
  10. Distinctive:

    Do not add frontmatter unless the user's daily note template uses it (check an existing daily note for the pattern and match it).

    line 60
  11. Distinctive:

    If a daily note template exists in the vault settings, follow its structure when creating a new note.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Obsidian Daily Note

Append a thought, log entry, or reminder to today's daily note in an Obsidian vault without leaving the terminal. The note is created if it does not exist, and existing content is never overwritten.

Step 0: Find the vault (once)

Resolve the configuration in this order:

  1. A daily-note.config.md file in the current project or its parents, with:
VAULT_PATH      Absolute path to the Obsidian vault root
NOTES_FOLDER    Folder for daily notes relative to the vault, e.g. "Daily" or "_Notes"
DATE_FORMAT     File name date format, default YYYY-MM-DD
  1. If no config file exists: check whether the current directory (or a parent) contains a .obsidian folder. If so, that is the vault; read .obsidian/daily-notes.json for the folder and format if present.
  2. Otherwise ask the user for vault path and notes folder, then offer to save the answers to daily-note.config.md for next time.

Never guess a vault path. Writing notes into the wrong directory is worse than asking once.

Step 1: Build the file path

  1. Get today's date from the current-date context (never from training data).
  2. Build the path: VAULT_PATH/NOTES_FOLDER/<date in DATE_FORMAT>.md

Step 2: Write

  • If the file does not exist: create it with a # <date> heading, then the new section.
  • If the file already exists: read it first, then append the new section at the end. Never overwrite or reorder existing content.

Section format:

## <section title>

<the user's text>

Title rules:

  • If the user separates a title from the body (for example with a |), use their title.
  • If the text starts with an obvious label ("Meeting with X:", "Reminder:"), use that.
  • Otherwise use Note.

Keep the user's text as written. Light cleanup (trim whitespace, fix an obvious typo the user flags) is fine; rewriting their words is not.

Step 3: Confirm

Report what was written and the full file path, and whether the note was created or appended to.

Rules

  • Never overwrite existing daily note content. Append only.
  • Never modify other notes in the vault.
  • Do not add frontmatter unless the user's daily note template uses it (check an existing daily note for the pattern and match it).
  • If a daily note template exists in the vault settings, follow its structure when creating a new note.

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.