docs(skills): improve daily-recap, meeting-note, quick-note with obsidian cli

daily-recap:
- add step 2h: dia browser daily activity summary parsing
- add bash command to find latest dia context index.html
- add instructions for parsing completed/meetings/tomorrow sections
- add guidance for merging dia data into synthesis buckets
- add gitlab mr link formatting guidance with full url examples
- update step 2 description to include 2h in parallel execution

meeting-note:
- replace manual file creation with obsidian create cli
- simplify to use meeting-template for all frontmatter/structure
- add post-creation obsidian append instructions for attendees/agenda
- add summary field reminder and obsidian property:set example

quick-note:
- replace manual file creation with obsidian create cli path parameter
- simplify to minimal structure (no frontmatter)
- add obsidian append for inline content captures
- clarify title slug format and newline escaping

Author: dgokcin

ai-stuff/claude/skills/daily-recap/SKILL.md

@@ -13,6 +13,8 @@ allowed-tools:
   - Bash(obsidian create:*)
   - Bash(obsidian help:*)
   - Bash(sleep:*)
+  - Bash(ls:*)
+  - Bash(find:*)
   # Slack (read-only)
   - mcp__claude_ai_Slack__slack_search_public_and_private
   - mcp__claude_ai_Slack__slack_search_public
@@ -54,7 +56,7 @@ Parse from `$ARGUMENTS`:
 - If a date like `2026-03-23`: use that
 - If empty: use today's date
 
-### Step 2: Gather data (do ALL of these in parallel)
+### Step 2: Gather data (do ALL of these in parallel, including 2h)
 
 #### 2a. Today's calendar events
 
@@ -165,6 +167,30 @@ Look for:
 - Unresolved items (pending reviews, open feedback)
 - Skip pure automation spam or FYI-only notifications
 
+#### 2h. Dia browser — daily activity summary
+
+Dia is a browser that generates its own daily activity summaries as HTML artifacts. These often capture work context that Slack/Gmail misses (browsing activity, GitLab MR reviews done in the browser, etc.).
+
+**Find and read in one step:**
+
+```bash
+find "$HOME/Library/Application Support/Dia/User Data/Profile 1/AgentServer/contexts" -name "index.html" -print0 | xargs -0 ls -t 2>/dev/null | head -1
+```
+
+This returns the path to the most recently modified `index.html` across all contexts. **Read that file** using the Read tool.
+
+**Parse the HTML content** — look for these sections (the structure is consistent):
+- `.section` with section-label **"Completed"** → `.item h3` (title) + `.item p` (description) + `.tag` spans
+- `.section` with section-label **"Meetings"** → `.meeting` rows with time + title
+- `.section` with section-label **"Tomorrow"** → `.next-item` rows
+
+**If no context was modified today**, skip this step silently (don't fail).
+
+**Merge Dia data into synthesis (Step 4):**
+- Dia "Completed" items → merge into Bucket 1 (what you did today). Avoid duplicating items already captured from Slack/Gmail. Dia tends to have richer descriptions of browser-based work (MR reviews, Datadog investigations, etc.)
+- Dia "Tomorrow" items → merge into Bucket 2 (notes for tomorrow)
+- Dia tags (e.g. `DEVX-1111`, `Datadog`) → use as context when writing task descriptions, but don't include them literally as Obsidian tags
+
 ### Slack filtering guidance
 
 When synthesizing Slack data, apply these filters:
@@ -230,6 +256,8 @@ Write these like a human would — casual, concise, lowercase-ish. Examples from
 
 Keep the voice natural. Don't over-formalize. Use wikilinks for people: `[[ben minter]]`.
 
+**GitLab MR links**: When mentioning MRs, always include a markdown link using the full GitLab URL. GitLab is at `https://git.treatwell.net`. Derive the project path from the Slack/email context (e.g. `devx/k8s-gitops`). Format: `[!31](https://git.treatwell.net/devx/k8s-gitops/-/merge_requests/31)`. Never write bare `!31` without a link.
+
 #### Bucket 2: Forward-looking stuff (`## notes for tomorrow` section)
 
 This goes into the existing `## notes for tomorrow` section. Include:

ai-stuff/claude/skills/meeting-note/SKILL.md

@@ -1,53 +1,42 @@
 ---
 name: meeting-note
-description: Create a meeting note in the vault with proper frontmatter and structure. Use when starting or documenting a meeting.
-tools: Write, Read, Glob
+description: "Create a meeting note in the vault with proper frontmatter and structure. Use when the user mentions a meeting, wants to take notes for a call, says 'meeting with X', 'sync with X', 'let me document this call', or is about to join or just finished a meeting."
+tools: Bash, Read
 argument-hint: <meeting title>
 ---
 
 # Create Meeting Note
 
-Create a meeting note in the Obsidian vault following the established template.
+Create a meeting note in the Obsidian vault using the `meeting-template` via the Obsidian CLI.
 
 ## Instructions
 
 1. Parse the meeting title from: `$ARGUMENTS`
    - If no arguments provided, ask for the meeting title
-2. Get today's date in `YYYY-MM-DD` format
-3. Create the file at: `~/vault/work/meetings/YYYY-MM-DD <title>.md`
-   - Use the vault path: `/Users/denizgokcin/Library/Mobile Documents/iCloud~md~obsidian/Documents/vault`
+2. Create the note using the Obsidian CLI:
+   ```bash
+   obsidian create name="<meeting title>" template="meeting-template"
+   ```
+   The template handles everything — frontmatter, date prefix, folder placement (`work/meetings/`), and structure. No need to manually construct paths or content.
+3. Confirm creation and report the file path
 
-### File Format
+### What the template produces
 
-```markdown
----
-date: YYYY-MM-DD HH:mm
-type: meeting
-client: N/A
-tags: meeting
-summary: " "
----
-tags: [[salonized/meetings/moc]]
-Date: [[YYYY-MM-DD]]
-
-# [[YYYY-MM-DD <title>]]
-
-**Attendees**:
--
+The meeting-template creates a note at `work/meetings/YYYY-MM-DD <title>.md` with:
+- Frontmatter: date, type, client, tags, summary
+- Sections: Attendees, Agenda, Questions, Notes, Action Items
+- Wikilinks to the daily note and meetings MoC
 
-## Agenda
+### After creation
 
-*What is the meeting agenda*
-
-## Questions
--
+If the user provided attendees, agenda items, or context in their message, use `obsidian append` to fill in the relevant sections:
+```bash
+obsidian append file="YYYY-MM-DD <title>" content="- @person1\n- @person2"
+```
 
-## Notes
--
+### Summary field
 
-## Action Items
+The `summary` frontmatter field is important — it powers the meeting views (MoC, date summary, monthly summary). Remind the user to fill it in after the meeting, or offer to set it if they share what the meeting was about:
+```bash
+obsidian property:set file="YYYY-MM-DD <title>" name="summary" value="discussed X and decided Y"
 ```
-
-4. Use the current time for the `date` field (YYYY-MM-DD HH:mm format)
-5. The H1 title must be a wikilink wrapping the full filename (without .md)
-6. Report the created file path when done

ai-stuff/claude/skills/quick-note/SKILL.md

@@ -1,39 +1,35 @@
 ---
 name: quick-note
-description: Quick capture a note to work/random or personal/random. Use for ad-hoc ideas, links, or anything that needs a quick home.
-tools: Write, Read, Glob
+description: "Quick capture a note to work/random or personal/random. Use when the user says 'jot this down', 'save this thought', 'note to self', 'remember this idea', or mentions a random idea, link, or snippet they want to capture. Also trigger when the user wants to quickly save something without specifying a particular note type."
+tools: Bash, Read
 argument-hint: <note title> [--personal]
 ---
 
 # Quick Note
 
-Quickly capture a note to the vault's random folders.
+Quickly capture a note to the vault's random folders using the Obsidian CLI.
 
 ## Instructions
 
 1. Parse input from: `$ARGUMENTS`
-   - If `--personal` flag is present: file to `personal/random/`
+   - If `--personal` flag is present: target `personal/random/`
    - Otherwise: default to `work/random/`
    - The remaining text is the note title
    - If no arguments: ask what to capture
-2. Create the file at the appropriate path:
-   - Work: `~/vault/work/random/<title-slug>.md`
-   - Personal: `~/vault/personal/random/<title-slug>.md`
-   - Use the vault path: `/Users/denizgokcin/Library/Mobile Documents/iCloud~md~obsidian/Documents/vault`
-   - title-slug: lowercase with spaces (e.g., "devx support bot idea.md")
-
-### File Format
-
-```markdown
-# <Title>
-
-<content from conversation or user input>
-```
+2. Create the note using the Obsidian CLI:
+   ```bash
+   obsidian create path="<work|personal>/random/<title slug>.md" content="# <Title>"
+   ```
+   - title slug: lowercase with spaces (e.g., `devx support bot idea.md`)
+   - No template needed — quick notes are intentionally minimal
+3. If the user provided content in the same message, append it:
+   ```bash
+   obsidian append file="<title slug>" content="<the content>"
+   ```
+4. Report the created file path when done
 
 ### Rules
 
-- Minimal structure - no frontmatter needed (random notes don't use it)
-- Just a title and content
-- If the user provides content in the same message, include it
-- If only a title, create the note with the title and leave room for content
-- Report the created file path when done
+- Minimal structure — no frontmatter, just a title and content
+- If only a title is given, create the note with just the H1 heading
+- Use `\n` for newlines in content values passed to the CLI