agentleFS
Sign inStart free
c-ibarrac-ibarra/ObsidianKnowledgeCurator/.agents/skills/daily-note/SKILL.md

daily-note

Skill0 starsChanged 43 days agoMITView on GitHub

Use this skill when the user wants to create, update, or review their daily note. Triggers include "create today's daily note", "update my daily note", "add to today's note", "log this to today", "daily note", "add to daily", "log this today", "what do I have in today's daily".

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use implement-spec, to-questionnaire and 3 more.

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.
  • AWSSkill

    implement-spec

    Implement the result of /to-spec and /to-tickets in code.

    Also in 3 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 3 projects that use this

  • MicrosoftSkill

    writing-for-agents

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

    Also in 3 projects that use this

  • +2 more from aws

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Create or update the user's daily note using obsidian daily:* CLI commands.

    line 9
  2. Distinctive:

    Check for templates first:

    line 28
  3. Distinctive:

    If a Daily Note template exists → let Obsidian create it:

    line 33
  4. Distinctive:

    If no template, create with minimal structure (no YAML, no frontmatter):

    line 38
  5. Very specific:

    After any create/update, confirm what was added.

    line 54
  6. Distinctive:

    Never overwrite the daily note — always append or prepend

    line 58
  7. Distinctive:

    No YAML frontmatter in daily notes

    line 59
  8. Very specific:

    If user has Templater configured, use obsidian daily to let Obsidian handle template insertion

    line 61

“Common” is measured: kept by at least 6 in 10 of the 4 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

Daily Note Skill

Goal

Create or update the user's daily note using obsidian daily:* CLI commands. The daily note follows the vault's conventions: no YAML, no emojis (except 📌 if needed).

Prerequisites

pgrep -x Obsidian > /dev/null && echo "open" || echo "CLOSED"
# Read obsidian-cli skill before operating

Step 1 — Check today's daily note

obsidian daily:read
obsidian daily:path
  • Content returned → note exists → go to Step 3 (update)
  • Empty / error → note doesn't exist → go to Step 2 (create)

Step 2 — Create daily note

Check for templates first:

obsidian templates

If a Daily Note template exists → let Obsidian create it:

obsidian daily

If no template, create with minimal structure (no YAML, no frontmatter):

obsidian daily:append content="# $(date +%Y-%m-%d)\n\n## Daily Focus\n- \n\n## Log\n\n## Ideas\n- \n\n## Notes Created Today\n- \n\n## Review\n- What went well?\n- What to improve?"

Step 3 — Handle update requests

User intentCommand
Log entryobsidian daily:append content="**HH:MM** — <content>"
Task / todoobsidian daily:append content="- [ ] <task>"
Ideaobsidian daily:append content="- <idea>"
Note createdobsidian daily:append content="- [[<Note Title>]]"
Top priorityobsidian daily:prepend content="## Top Priority\n- <item>"

Step 4 — Confirm

After any create/update, confirm what was added. Offer to open: obsidian daily (opens in UI).

Constraints

  • Never overwrite the daily note — always append or prepend
  • No YAML frontmatter in daily notes
  • Timestamps in 24h format: 14:32
  • If user has Templater configured, use obsidian daily to let Obsidian handle template insertion

Examples

"Create today's daily note"

obsidian daily:read   # check existence
obsidian daily        # create/open via Obsidian's template

"Log: finished integration with Claude API"

obsidian daily:append content="**14:35** — Finished integration with Claude API"

"Add task: review LangGraph note"

obsidian daily:append content="- [ ] Review [[MCP 03 — Agentic AI With LangGraph]]"

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