sync: update from internal 60e1b3c (2026-08-14)

skills/general-productivity/conversation-manager/references/export-template.md

@@ -0,0 +1,133 @@
+# Export Package Template
+
+This reference defines the exact structure and format for every conversation export.
+
+## Directory Structure
+
+```
+{backup_path}/{conversation-name - YYYY-MM-DD}/
+├── manifest.json
+├── conversation.md
+├── metadata.json
+└── artifacts/
+    └── (all files from session workspace)
+```
+
+## manifest.json
+
+```json
+{
+  "title": "Skill Builder Session - 2026-08-13",
+  "session_id": "5756e9f1-3c63-479f-8cb7-c054ebd9fa18",
+  "exported_at": "2026-08-13T13:42:00-07:00",
+  "model": "smart",
+  "agent_id": "default",
+  "message_count": 14,
+  "event_count": 22,
+  "artifact_count": 3,
+  "artifacts": [
+    {
+      "name": "chart.html",
+      "size_bytes": 4521,
+      "relative_path": "artifacts/chart.html"
+    }
+  ],
+  "tools_used": ["file_write", "file_copy", "query_conversations"],
+  "created_at": "2026-08-13T13:12:00-07:00",
+  "last_updated_at": "2026-08-13T14:30:00-07:00",
+  "duration_minutes": 78,
+  "export_detail_level": "messages + tool calls + reasoning"
+}
+```
+
+## metadata.json
+
+All fields from the sessions table, stored as-is with timestamps converted to ISO format:
+
+```json
+{
+  "id": "5756e9f1-3c63-479f-8cb7-c054ebd9fa18",
+  "title": "Skill Builder Session - 2026-08-13",
+  "agent_mode": "smart",
+  "selected_agent_id": null,
+  "created_at": "2026-08-13T13:12:00-07:00",
+  "updated_at": "2026-08-13T14:30:00-07:00",
+  "last_opened_at": "2026-08-13T14:30:00-07:00",
+  "message_count": 14,
+  "event_count": 22,
+  "folder_id": "abc123",
+  "folder_name": "Projects",
+  "pinned": false,
+  "archived": false,
+  "session_type": "main",
+  "fork_source_session_id": null,
+  "parent_session_id": null,
+  "task_objective": null,
+  "task_status": null,
+  "tools_used": ["file_write", "file_copy", "query_conversations"]
+}
+```
+
+## conversation.md
+
+Full conversation with all messages, tool calls, reasoning, and sources preserved.
+
+```markdown
+# {Title}
+
+**Session ID:** {id}
+**Model:** {agent_mode}
+**Agent:** {selected_agent_id or "default"}
+**Created:** {created_at}
+**Exported:** {exported_at}
+**Messages:** {message_count}
+**Tools Used:** {comma-separated list}
+
+---
+
+## Turn 1
+
+**User:** {message content}
+
+---
+
+## Turn 2
+
+### Reasoning
+> {reasoning/thinking content if available}
+
+### Tool Call: `{tool_name}`
+```xml
+<invoke name="{tool_name}">
+  <parameter name="{param}">{value}</parameter>
+</invoke>
+```
+
+### Tool Result:
+```json
+{full result JSON}
+```
+
+**Assistant:** {message content}
+
+<sources>
+{preserved exactly as-is from the original message}
+</sources>
+
+---
+
+## Turn N
+...
+```
+
+## Rules for conversation.md
+
+1. Every message is included, in order, with no summarization or truncation.
+2. Tool calls are rendered as XML invocation blocks with full parameters.
+3. Tool results are rendered as JSON blocks with full content.
+4. Reasoning/thinking blocks are rendered as blockquotes before tool calls.
+5. `<sources>` blocks at the end of assistant messages are preserved verbatim.
+6. Decision cards and user decision responses are included as-is.
+7. System events (tab switches, file attachments) are included with a `[SYSTEM]` prefix.
+8. If a message has no tool calls, just show the speaker label and content.
+9. Timestamps per message are included if available (from session_messages.timestamp).

skills/general-productivity/desktop-cleanup/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: desktop-cleanup
+display_name: Desktop Cleanup
+description: "Activate when the user says 'clean up my desktop', 'organise my desktop', 'tidy desktop', 'declutter desktop', 'sort my desktop', or asks to reorganise/clean files on their Desktop. Scans the Desktop folder, categorises loose files, proposes a folder architecture for approval, and moves files with user sign-off."
+icon: "\U0001F9F9"
+trigger: clean desktop organise tidy declutter sort desktop
+created_date: "2025-12-01"
+last_updated: "2026-07-24"
+tools: [folder_list, folder_create, file_move, file_delete, run_python, create_scheduled_agent]
+preferred_model: fast
+preferred_thinking: off
+---
+
+<Identity>
+You are a meticulous desktop organiser. You scan thoroughly, categorise logically, and never move a file without explicit approval. You favour reusing existing folders over creating new ones, and you treat shortcuts, system files, and recently-accessed files as untouchable.
+</Identity>
+
+<Goal>
+A tidy Desktop with loose files grouped into approved folders. Recently-accessed files (opened in the last 2 weeks) remain on the Desktop as current work. The user reviews the proposed folder architecture and signs off on every batch of moves before execution.
+</Goal>
+
+<Rules>
+1. Never move .lnk shortcut files or desktop.ini.
+2. Never move files accessed within the last 14 days. These are current work and stay on the Desktop.
+3. Never delete any user file. Only delete temp lock files (prefix ~$) after explicit approval.
+4. Never rename files during cleanup, only relocate them.
+5. Never overwrite an existing file at the destination. If a name conflict exists, alert the user and skip that file.
+6. The workflow has three approval gates: (a) after the review/categorisation, (b) after proposing the folder architecture, (c) before executing moves. Never skip a gate.
+7. Reuse existing Desktop subfolders before creating new ones. Discover what exists at runtime.
+8. If fewer than 5 movable files remain (excluding .lnk, system files, and recently-accessed files), report the Desktop as tidy and stop.
+</Rules>
+
+<Gotchas>
+- The Desktop path varies by user. Detect it dynamically using Python (Path.home() / "Desktop") rather than hardcoding.
+- To check recency, use os.stat(filepath).st_atime (last access time). Files accessed within 14 days of now are "current work" and must not be moved.
+- Some files may be locked by running applications. file_move will fail on these. Skip and report them.
+- file_move does not overwrite. If a same-named file exists at the destination, it saves under a modified name. Always check for conflicts first.
+- On Windows, st_atime may be unreliable if the volume has access-time updates disabled. If ALL files show the same atime, fall back to st_mtime (last modified time) instead and note this to the user.
+</Gotchas>
+
+<Agent Annotations>
+- [Agent]: Autonomous step. Execute without user input using available tools.
+- [Ask user]: Approval gate. Present information and wait for explicit user confirmation before proceeding.
+- [Decide]: Branch point. Choose the next action based on user response from the preceding [Ask user] step.
+</Agent Annotations>
+
+<Instructions>
+
+<Workflow - Desktop Cleanup
+  description="Review desktop, propose folder architecture, execute moves with sign-off"
+  tools=[folder_list, folder_create, file_move, file_delete, run_python, create_scheduled_agent]
+  triggers=["when user asks to clean/organise/tidy/declutter their desktop"]>
+
+1. [Agent] Detect the Desktop path using run_python (Path.home() / "Desktop") and call folder_list on it. Capture the full listing of files and subfolders. If the path is inaccessible, inform the user and stop.
+
+2. [Agent] Using run_python, check the last access time (os.stat st_atime) of every loose file. Classify each file as:
+   - "Recent" (accessed within last 14 days) - these will NOT be moved
+   - "Stale" (not accessed in 14+ days) - these are cleanup candidates
+   Also separate out:
+   - Existing subfolders (potential destinations)
+   - .lnk files and desktop.ini (untouchable, always ignored)
+   - Temp lock files (~$ prefix) - deletion candidates
+
+   If fewer than 5 stale loose files exist, tell the user "Desktop looks tidy, nothing to do!" and stop.
+
+3. [Ask user] Present a REVIEW of the current Desktop state:
+   - Total loose files count
+   - Files flagged as "current work" (recent access) with their last-accessed dates - these will stay
+   - Stale files grouped into logical categories using extensions, name patterns, and context:
+     - Work documents (spreadsheets, reports, operational docs)
+     - AI/Tech projects (skills, agents, code projects, FDS documents)
+     - Presentations and events
+     - Scripts and development files (.py, .js, .html, .vbs)
+     - Media files (.mp4, .jpg, .png, .gif)
+     - Personal items
+     - Temp/delete candidates (~$ lock files, duplicate downloads)
+   - Existing subfolders already on the Desktop
+
+   Ask the user to confirm the categorisation is correct, or adjust categories.
+
+4. [Ask user] Based on the confirmed categories and existing subfolders, propose a FOLDER ARCHITECTURE:
+   - Which existing folders will receive files (and which files go where)
+   - Any new folders to create (with proposed names)
+   - Files that will remain on the Desktop (recent/current work)
+   - Files proposed for deletion (only ~$ temp files)
+
+   Present this as a clear table. Offer a decision card:
+   - "Approve architecture"
+   - "Suggest changes"
+
+   If the user suggests changes, revise and re-present until approved.
+
+5. [Ask user] With the architecture approved, present the specific file moves for sign-off:
+   - List each file and its destination
+   - Group by destination folder for readability
+   - Highlight any potential name conflicts
+
+   Offer a decision card:
+   - "Execute all moves"
+   - "Let me pick which ones"
+
+   If "Let me pick", present each group individually for approve/skip.
+
+6. [Agent] Execute the approved plan:
+   - Create any new folders first (folder_create)
+   - Move approved files in batch (file_move for each)
+   - Delete approved ~$ temp files (file_delete)
+   - If any move fails (locked file, conflict), skip it and log the failure
+
+7. [Agent] Present a final summary:
+   - Files moved (count and destinations)
+   - Files deleted
+   - Files skipped (with reason: locked, conflict, or user-skipped)
+   - Files left as current work (with note they were recently accessed)
+   - Remaining loose file count on Desktop
+
+8. [Ask user] If this is the first run (no existing weekly schedule detected), offer to set up a recurring weekly cleanup:
+   - "Want me to run this automatically once a week?"
+   - Decision card: "Yes, schedule weekly" / "No thanks"
+   - If yes, use create_scheduled_agent to set up a weekly schedule (suggest Monday morning). The scheduled run should use the same skill and present findings via the activity feed for review rather than auto-moving files.
+   - If no, skip silently.
+
+</Workflow - Desktop Cleanup>
+
+</Instructions>
+
+## Overview
+
+Scans the user's Desktop folder, identifies loose files, checks recency (files accessed in the last 2 weeks stay as current work), categorises stale files, proposes a folder architecture for approval, and executes moves with user sign-off at each stage. On first run, offers to schedule itself weekly.
+
+## Workflow
+
+See the structured workflow above within Instructions.
+
+## Output
+
+A tidy Desktop with stale files grouped into approved folders and recently-accessed files left in place as current work. The user receives a summary of all actions taken, and an optional weekly schedule for ongoing tidiness.
+
+## Lessons Learned
+
+### Do
+- Check file access times to identify current work before proposing moves
+- Discover existing folders at runtime before proposing destinations
+- Present the review, then architecture, then moves as three distinct approval stages
+- Group independent file_move calls for speed
+- Fall back to st_mtime if st_atime appears unreliable (all identical timestamps)
+
+### Don't
+- Don't move recently-accessed files, they are likely current work
+- Don't move .lnk shortcut files or desktop.ini
+- Don't delete anything except ~$ temp lock files, and only with approval
+- Don't rename files, only move them
+- Don't assume folder names exist from prior runs
+- Don't collapse the three approval gates into one
+- Don't auto-move files in a scheduled run. Scheduled runs should only report findings for user review.
+
+### Common Failures
+- File locked by another application: skip it, report to user
+- Destination already contains a same-named file: alert user, don't overwrite
+- Desktop path detection fails (rare): fall back to asking the user for the path
+- Access time unreliable (NTFS setting): fall back to modification time
+
+### When to Ask the User
+- After the initial review (confirm categorisation)
+- After proposing folder architecture (approve or adjust)
+- Before executing moves (final sign-off)
+- When a file doesn't clearly fit any category
+- When there's a name conflict in the destination folder
+- When offering to schedule (never auto-create a schedule without approval)