Obsidian Daily Note

Create and manage Obsidian daily notes. Use when asked to write daily notes, record today's work, log session activities, or create daily summaries. Triggers...

Security Scan

The skill's instructions and requirements align with its stated purpose (creating and writing Obsidian daily notes); it is an instruction-only skill with no install, credentials, or unrelated requests.

Purpose & Capability

Name/description (Obsidian daily notes) match the SKILL.md content: templates, filename conventions, vault layout, and write workflow. No unrelated credentials, binaries, or installs are requested.

Instruction Scope

The workflow instructs the agent to "collect today's activities from session context" and to write files to a user-specified vault path. This is consistent with the feature but is a bit vague: it gives the agent broad discretion over what conversational/contextual data to use and instructs writing files to disk. The skill does not instruct reading arbitrary system files, shell history, or external endpoints.

Install Mechanism

No install spec or code — instruction-only. This minimizes the risk of arbitrary code being downloaded or executed on install.

Credentials

No environment variables, credentials, or config paths are requested. The only implicit requirement is that the user supplies the vault/base path and that the agent has permission to write files there, which is proportional to the skill's purpose.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request persistent elevated privileges or modification of other skills or system-wide settings.

Assessment

This skill appears coherent with its stated purpose. Before installing or using it, decide how you will supply the vault/base path (so the agent only writes where you expect), and limit the agent's filesystem permission to that vault if possible. Review generated notes before saving if you are concerned about sensitive content being pulled from broader conversation history. On Windows, follow the provided UTF-8 write guidance to avoid encoding problems. If you want tighter control, require the agent to output note content for manual saving rather than allow automatic writes.

Configuration

Set these to match your vault:

• Base path: path to your DAILY folder inside the vault
• Sync: adjust if using OneDrive / iCloud / Obsidian Sync

File Naming

YYYY-MM-DD_short-summary.md

Examples:

• 2026-02-18_fix-env-gsudo-chrome.md
• 2026-02-19_maibotalks-app-submit.md

The title should briefly summarize the day's main activities.

Template

# YYYY-MM-DD (Day) — Daily Note

## Completed Today

### [Category]
- **Task** → Result
  - Details

## Tomorrow's Actions

- [ ] Action 1
- [ ] Action 2

Category emoji prefixes: 🔧 Dev, 📱 Mobile, 🚀 Deploy, 🔗 Integration, 📝 Docs, 💡 Ideas, 📋 Planning

Encoding

CRITICAL on Windows: Never use Set-Content. Always use:

[System.IO.File]::WriteAllText($path, $content, [System.Text.Encoding]::UTF8)

Workflow

1. Collect today's activities from session context
2. Group by category
3. Generate filename with descriptive title
4. Write using UTF-8 encoding
5. Include tomorrow's action items from pending tasks

Vault Structure (PARA)

• 00.DAILY/ — daily notes
• 01.PROJECT/ — project dashboards and kanban
• 02.AREA/ — ongoing areas of interest
• 03.RESOURCES/ — reference material
• 04.ARCHIVE/ — archived notes

Project docs live in PROJECT_ROOT/docs/ with A/D/I/T prefixes (Analysis / Design / Implementation / Test).