Install
$ agentstack add skill-jqaisystems-jqai-ai-skills-obsidian-daily-note ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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/.md
Step 2: Write
- If the file does not exist: create it with a
#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:
##
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jqaisystems
- Source: jqaisystems/jqai-ai-skills
- License: MIT
- Homepage: https://www.ai.joaoqueiros.com/skills/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.