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".
In this repository47 other files it gives its agents.
- agents-md-writerSkill
- ai-image-run-pacingSkill
- automation-state-reconcilerSkill
- backup-readiness-auditorSkill
- brand-voice-linterSkill
- case-study-writerSkill
- client-delivery-auditorSkill
- client-intake-builderSkill
- client-workspace-scaffolderSkill
- code-deduplicatorSkill
- cold-outreach-writerSkill
- demo-animationSkill
- demo-animation-v2Skill
- discovery-briefSkill
- em-dash-removerSkill
- etsy-listing-optimizerSkill
- follow-up-radarSkill
- github-profile-proof-updaterSkill
- github-safe-publisherSkill
- idea-inboxSkill
- implement-client-feedbackSkill
- lead-scorerSkill
- llms-txt-generatorSkill
- local-app-public-demoSkill
- media-spec-checkerSkill
- ops-status-reportSkill
- outreach-pipeline-designerSkill
- php-form-mailerSkill
- proposal-writerSkill
- release-announcement-writerSkill
- remove-ai-image-metadataSkill
- research-brief-curatorSkill
- research-to-articleSkill
- screen-recorderSkill
- session-handoffSkill
- skill-builderSkill
- skill-reviewerSkill
- social-campaign-proof-trackerSkill
- skill-nameSkill
- thumbnail-legibility-checkSkill
- thumbnail-set-designerSkill
- vault-janitorSkill
- verify-public-claimsSkill
- web-scraperSkill
- website-change-verifierSkill
- windows-reinstall-plannerSkill
- write-evidence-backed-profileSkill
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
- Very specific: line 22
If no config file exists: check whether the current directory (or a parent) contains a .obsidian folder.
- Distinctive: line 25
Never guess a vault path. Writing notes into the wrong directory is worse than asking once.
- Very specific: line 34
If the file does not exist: create it with a # <date> heading, then the new section.
- Distinctive: line 35
If the file already exists: read it first, then append the new section at the end.
- Very specific: line 46
If the user separates a title from the body (for example with a |), use their title.
- Distinctive: line 47
If the text starts with an obvious label ("Meeting with X:", "Reminder:"), use that.
- Distinctive: line 50
Keep the user's text as written.
- Distinctive: line 58
Never overwrite existing daily note content.
- Distinctive: line 59
Never modify other notes in the vault.
- Distinctive: line 60
Do not add frontmatter unless the user's daily note template uses it (check an existing daily note for the pattern and match it).
- Distinctive: line 61
If a daily note template exists in the vault settings, follow its structure when creating a new note.
≈ “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.
Files
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:
- A
daily-note.config.mdfile 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- If no config file exists: check whether the current directory (or a parent) contains a
.obsidianfolder. If so, that is the vault; read.obsidian/daily-notes.jsonfor the folder and format if present. - Otherwise ask the user for vault path and notes folder, then offer to save the answers to
daily-note.config.mdfor next time.
Never guess a vault path. Writing notes into the wrong directory is worse than asking once.
Step 1: Build the file path
- Get today's date from the current-date context (never from training data).
- 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.
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
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.

