Manages Obsidian Daily Notes via the official Obsidian CLI. Creates and opens daily notes, appends entries (journals, logs, tasks, links), reads daily notes and vault files, searches vault content, and handles relative dates like "yesterday", "last Friday", and "3 days ago". Requires Obsidian 1.12+ with Command line interface enabled.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Interact with Obsidian Daily Notes through the official obsidian command: create
or open today's note, append entries, read notes, and search vault content.
Check that the official CLI is available:
obsidian version
If the command is unavailable, ask the user to enable Obsidian's CLI:
Target a vault explicitly when needed by placing vault=<name-or-id> before the
command:
obsidian vault="Work" daily
Obsidian Daily Notes plugin defaults:
YYYY-MM-DDGet current date:
date +%Y-%m-%d
Cross-platform relative dates (GNU first, BSD fallback):
| Reference | Command |
|---|---|
| Today | date +%Y-%m-%d |
| Yesterday | date -d yesterday +%Y-%m-%d 2>/dev/null || date -v-1d +%Y-%m-%d |
| Last Friday | date -d "last friday" +%Y-%m-%d 2>/dev/null || date -v-1w -v+fri +%Y-%m-%d |
| 3 days ago | date -d "3 days ago" +%Y-%m-%d 2>/dev/null || date -v-3d +%Y-%m-%d |
| Next Monday | date -d "next monday" +%Y-%m-%d 2>/dev/null || date -v+monday +%Y-%m-%d |
obsidian daily
Opens today's daily note in Obsidian, creating it from template if it doesn't exist.
obsidian daily:append content="ENTRY_TEXT"
Append without adding a newline:
obsidian daily:append content="ENTRY_TEXT" inline
Today:
obsidian daily:read
Specific date, using the vault's configured daily-note folder and date format:
obsidian read path="Daily Notes/2025-01-10.md"
Relative date (yesterday):
obsidian read path="Daily Notes/$(date -d yesterday +%Y-%m-%d 2>/dev/null || date -v-1d +%Y-%m-%d).md"
obsidian search query="TERM"
Machine-readable search:
obsidian search query="TERM" format=json
Put vault="NAME" before the command:
obsidian vault="Work" read path="Daily Notes/2025-01-10.md"
- Went to the doctor
- [ ] Buy groceries
- https://github.com/anthropics/skills
- 15:45 This is a log line
Journal entry:
obsidian daily:append content="- Went to the doctor"
Task:
obsidian daily:append content="- [ ] Buy groceries"
Link:
obsidian daily:append content="- https://github.com/anthropics/skills"
Timestamped log:
obsidian daily:append content="- $(date +%H:%M) This is a log line"
Read last Friday:
obsidian read path="Daily Notes/$(date -d 'last friday' +%Y-%m-%d 2>/dev/null || date -v-1w -v+fri +%Y-%m-%d).md"
Search for "meeting":
obsidian search query="meeting"
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
The English summary is being prepared. Showing the original description.
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
The English summary is being prepared. Showing the original description.
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
The English summary is being prepared. Showing the original description.
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.
The English summary is being prepared. Showing the original description.
Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.
The English summary is being prepared. Showing the original description.
Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)
The English summary is being prepared. Showing the original description.