with one click
daily
// Append a timestamped bullet to today's daily log. No inbox, no triage — one line per call.
// Append a timestamped bullet to today's daily log. No inbox, no triage — one line per call.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | daily |
| description | Append a timestamped bullet to today's daily log. One line per call. |
| allowed-tools | Bash Read |
Append timestamped bullet to daily/YYYY-MM-DD.md. No MATCH/NEW, no inbox, no triage. Use /note for knowledge fragments; use /daily for time-anchored observations and daily progress.
Uses create-or-append and property:set (see CLI docs). Local daily/ dir created via mkdir -p if missing.
See §1 Vault path resolution. If no vault is configured, abort with:
No vault configured — run /wiki init first.
| User says | Operation |
|---|---|
/daily <text>, "daily note this …", "log to today …", "log this …", "add to today's log …", "daily log: …" | CAPTURE |
No LIST, no PROCESS. Daily files are an append-only log — triage and synthesis are handled by /daily-close.
Steps:
Extract arguments from the user's message. Everything after the trigger phrase. Scan for image-path tokens (any token that resolves to a path or carries a supported image extension); keep them separate. Join the remaining non-path tokens as the verbatim text segment in original order with single spaces. Do not include image-path tokens in the verbatim text.
Image routing. If any image paths are present → read ${CLAUDE_PLUGIN_ROOT}/_shared/image-capture.md. Use that file to determine the image-specific bullet text and attachment handling only. Then continue with steps 3–8 below for the normal daily append flow — resolve <vault_root>, compute date/time, ensure daily directory, probe and write the daily file via the CLI, and confirm.
Resolve <vault_root> per §1. Abort with No vault configured — run /wiki init first. if unresolved.
Compute today as YYYY-MM-DD and current local time as HH:MM (24-hour, zero-padded).
Ensure directory: if <vault_root>/daily/ does not exist, create it silently with mkdir -p. (Local directory creation, not a vault page op.)
Append the bullet: issue one obsidian create-or-append call. Wrapper handles both branches; model never reads/reconstructs body.
obsidian create-or-append \
file=daily/YYYY-MM-DD.md \
template="---\ntype: daily\ndate: YYYY-MM-DD\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\n---\n\n## Captures\n" \
content="- HH:MM <verbatim text>"
The template argument is used only when the file is missing; when the file exists, the wrapper appends content and ignores template. See §2 frontmatter schema for the daily template shape.
Bump updated: issue one obsidian property:set call. Obsidian updates only that property; body passes verbatim.
obsidian property:set \
name=updated \
value=YYYY-MM-DD \
type=date \
path=daily/YYYY-MM-DD.md
Confirm with exactly one line:
Logged to daily/YYYY-MM-DD.md
One line only. No diff, no reasoning.
Per §7:
HH:MM prefix in file order — no collision handling, no counter.See §2 Frontmatter schema — daily shape.
First call of the day (file does not exist):
user> /daily shipped the /note slug rewrite
# daily/2026-04-27.md created with frontmatter + ## Captures heading
assistant> Logged to daily/2026-04-27.md
Subsequent call (file exists, heading present):
user> log to today: pairing session with @dana on the wiki lint refactor
# one bullet appended under ## Captures
assistant> Logged to daily/2026-04-27.md
Two calls in the same minute:
user> /daily standup done
assistant> Logged to daily/2026-04-27.md
user> daily note this: retrospective rescheduled to Thursday
assistant> Logged to daily/2026-04-27.md
# both bullets share the same HH:MM prefix — acceptable
No vault configured:
user> /daily fixed the flaky test
assistant> No vault configured — run /wiki init first.