| name | obsidian-logs |
| description | Master conventions for chronological logs: governs Daily Notes, Meetings, and incoming Inputs (Emails, Slack, Readings). |
| version | 1.4.0 |
| author | Apollo |
| index | yes |
| license | MIT |
| platforms | ["linux","macos"] |
| metadata | {"hermes":{"tags":["obsidian","logs","daily-notes","meetings","inputs","folder-conventions"],"related_skills":["obsidian","obsidian-notes","work-log","apollo-granola-ingest"]}} |
Obsidian Type: Chronological Directory & Input Conventions
This master skill governs the structure, naming, templates, and navigation of chronological log files and incoming raw input streams under /Notebook/Daily Notes/ (or /Inputs/Daily Notes/) and /Inputs/ directories.
1. Directory Navigation & Coordinates
- Daily Notes Directory:
/home/justin.guest/Developer/obsidian-vault/Inputs/Daily Notes/ (or /home/justin.guest/Developer/obsidian-vault/Notebook/Daily Notes/ depending on sync setup)
- Category:
category: "[[Daily Notes]]"
- Meetings Directory:
/home/justin.guest/Developer/obsidian-vault/Inputs/Meetings/
- Category:
category: "[[Meetings]]"
- Emails Directory:
/home/justin.guest/Developer/obsidian-vault/Inputs/Emails/ (category: "[[Emails]]")
- Slack Directory:
/home/justin.guest/Developer/obsidian-vault/Inputs/Slack/ (category: "[[Slack]]")
- Readings Directory:
/home/justin.guest/Developer/obsidian-vault/Inputs/Readings/ (category: "[[Readings]]")
2. Daily Notes Management
Daily Notes are the central journal and timeline for Justin's day.
Naming Convention
- Format:
YYYY-MM-DD Weekday.md (e.g., 2026-06-09 Tuesday.md, 2026-06-14 Sunday.md). Weekdays must be fully capitalized, separated from the date by a space.
Note Layout & Structure
A Daily Note begins with an executive summary callout block followed by chronological schedule and work log sections (note: the Accomplishments, Notepad, and Daily Scratchpad sections were retired as redundant, replaced by a single global Scratchpad note in /Inbox/Scratchpad.md):
---
id: "YYYYMMDDHHmmss"
daily_note: "[[YYYY-MM-DD Weekday|YYYY-MM-DD Weekday]]"
category: "[[Daily Notes]]"
---
|> [!summary] Summary Callout
|> High-level executive bullet summary of the day.
## 🌄 Morning Briefing
- Work Log Review (Yesterday)
- Heads-Up (Urgent Tasks, Inbox/Calendar Candidates)
## 🗓 Schedule & Events
- List of meetings, calendar events, or appointments for the day.
## ✅ Work Log
### 🚀 Highlights & Decisions
- Key milestones, critical choices, and active decisions made during the day.
Interaction with work-log
When compiling a work log, fetch events from Google Calendar, Linear, and Slack, compile today's summary, and append/update the schedule and Highlights & Decisions sections directly inside today's Daily Note (omitting accomplishments/completed task lists entirely).
Updating Past Events & Cancellations
When updating past daily notes or reviews to reflect that a planned calendar event was not attended or was cancelled:
- Do not delete the event: Keep the event entry in the
Schedule & Events section to preserve the context of what was planned.
- Mark the status: Wrap the event text in strikethroughs
~~...~~ and append (Did not attend) or (Cancelled) to clearly signify the actual outcome.
- Align dependent sections: Scan the Daily Note's
Preview Summary and the following day's Morning Briefing (which contains the Work Log Review (Yesterday)) and update them to accurately reflect that the event did not occur.
3. Meetings & Granola Management
Governs meeting note formatting and the ingestion of raw transcripts.
Naming Convention
- Format:
YYYY-MM-DD - Spaced Meeting Title.md (e.g., 2026-06-09 - SignLab Product Alignment.md).
Meeting Note Layout
---
id: "YYYYMMDDHHmmss"
daily_note: "[[YYYY-MM-DD Weekday|YYYY-MM-DD Weekday]]"
category: "[[Meetings]]"
---
# Meeting Title
**Date:** YYYY-MM-DD
**Attendees:** [[Justin Goff]], [[Person Name]]
---
## Agenda
-
## Notes
-
## Action Items
- [ ]
Ingestion & Sync Pipeline
- Granola Sync: Raw transcripts and notes dropped into
/Meetings/ are automatically swept, formatted, and moved into the /Inputs/Meetings/ directory. This is automated by the apollo-granola-ingest skill.
- No Raw Logs in Root: Raw unformatted files must never be left in
/Meetings/. Ensure automated routines move and archive them inside /Inputs/Meetings/. Every meeting note must link back to its creation day in its YAML daily_note: property.
