thoth-plugin 1.2.1 → 1.2.2

package/dist/defaults/skill/morning-boot/SKILL.md

@@ -1,106 +1,45 @@
 ---
 name: morning-boot
-description: The master orchestrator for your morning routine. Parallelizes scans and synthesizes the Daily Log.
-triggers:
-  - start my day
-  - morning routine
-  - prepare me for the day
-  - what do I need to do today
-  - boot up
-  - daily briefing
-  - morning boot
+version: 1.0.0
+description: Operational mode (e.g. 'deep-work', 'maintenance')
+triggers: 
+inputs: 
+- name: mode
+type: markdown
+required: false
+default: auto
+output: 
+created: 2026-01-09
+updated: 2026-01-09
 ---
 
 # Morning Boot Skill
 
 You are the **Daily Operations Orchestrator**. Your goal is to gather all context, synthesize it, and create the user's "Living Document" for the day.
 
-## Protocol Execution
+## Execution Method
 
-### Step 1: Initialize
+This skill uses **OpenProse** for multi-agent orchestration.
 
-1. **Temporal Grounding**:
-   - Check `<omo-env>` for Current Date/Time and Timezone.
-   - Calculate `DayOfWeek`, `WeekNumber`, and `Quarter`.
-   - Identify the **Operational Mode**:
-     - Monday = Launch Mode (planning, alignment)
-     - Tuesday-Thursday = Execution Mode (deep work)
-     - Friday = Closure Mode (wrap up, delegate)
-     - Weekend = Sanctuary Mode (restoration)
+**To execute this workflow:**
 
-2. **Load Context**:
-   - Read `kernel/state/trust.md` for current trust level.
-   - Read `work/MASTER.md` for work hemisphere overview.
-   - Check `work/inbox/` for pending items.
+1. Load the OpenProse skill: `/open-prose`
+2. Execute the workflow: `/prose-run kernel/workflows/morning-boot.prose`
 
-### Step 2: Parallel Scans (High Throughput)
+The OpenProse workflow handles:
+- Parallel email, calendar, and Slack scans
+- Operational mode detection
+- Deep work block identification
+- Complexity budget calculation
+- Daily log synthesis
+- Final briefing
 
-Launch three simultaneous `background_task` calls for parallel execution.
+## Workflow Location
 
-**Agent A: Email Scan**
-```
-background_task(
-  agent="general",
-  description="Email triage scan",
-  prompt="Scan recent emails using google-workspace tools. Categorize by: URGENT (needs response today), ACTION (needs response this week), FYI (informational). Return structured report with sender, subject, category, and recommended action."
-)
-```
-
-**Agent B: Calendar Scan**
-```
-background_task(
-  agent="general", 
-  description="Calendar analysis",
-  prompt="Analyze today's calendar using google-workspace tools. For each meeting: identify prep required, key attendees, and time blocks. Flag any conflicts or back-to-back meetings. Return structured report."
-)
-```
-
-**Agent C: Slack Scan**
-```
-background_task(
-  agent="general",
-  description="Slack pulse check", 
-  prompt="Scan recent Slack messages using slack tools. Identify: DMs needing response, channel mentions, threads requiring input. Categorize by urgency. Return structured report."
-)
-```
-
-### Step 3: Synthesis (The Master Plan)
-
-Once all three background tasks complete (system will notify):
-
-1. **Collect Results**: Use `background_output` to retrieve each scan's results.
-
-2. **Merge & Prioritize**:
-   - Combine Email ACTIONs, Slack RESPONDs, and Calendar PREP REQUIRED.
-   - Apply the **Executive Filter**: What is the #1 priority? What are the Top 3?
-   - Consider biological mode (high-cognitive morning = protect for deep work).
-
-3. **Save Scan Outputs**:
-   - Create folder `work/operations/daily-log/YYYY-MM-DD/` (if not exists).
-   - Save each scan result to its own file:
-     - `cal-grid.md` - Calendar scan with SCAN_DATA_START/END blocks
-     - `mail-triage.md` - Email scan with SCAN_DATA_START/END blocks
-     - `slack-pulse.md` - Slack scan with SCAN_DATA_START/END blocks
-
-4. **Generate Daily Log**:
-   - Use template from `work/operations/daily-log/TEMPLATE-daily-log.md`.
-   - Populate all sections (Priorities, Team Focus, Calendar, Pending Responses).
-   - Save synthesized `daily-log.md` to the same folder.
-
-### Step 4: Finalize
-
-1. **Summarize** today's plan to the user in chat.
-2. **Suggest Complexity Budget** based on meeting load:
-   - Light day (0-2 meetings): 2-3 Heavy tasks
-   - Medium day (3-4 meetings): 1-2 Heavy tasks  
-   - Heavy day (5+ meetings): Focus on meetings, 1 Light task max
-3. **Identify Time Blocks** for deep work based on calendar gaps.
-
----
+`kernel/workflows/morning-boot.prose`
 
 ## Technical Constraints
 
 - **Trust Level**: This skill requires Trust Level 2+ for email/calendar access.
-- **Parallel Execution**: Use `background_task` for concurrent scans, not sequential `task` calls.
-- **Verification**: If a scan returns no data or fails, notify user and offer sequential fallback.
+- **OpenProse Required**: The open-prose skill must be available.
 - **Privacy**: Never store raw email/message content in logs - only summaries and action items.

package/dist/defaults/skill/slack-pulse/SKILL.md

@@ -1,12 +1,16 @@
 ---
 name: slack-pulse
-description: Scan Slack for mentions, high-value DMs, and informal requests using the Thoth standard protocol.
-triggers:
-  - check slack
-  - slack mentions
-  - what's happening on slack
-  - any slack messages
-  - scan slack
+version: 1.0.0
+description: Lookback window in hours
+triggers: 
+inputs: 
+- name: hours
+type: markdown
+required: false
+default: 4
+output: 
+created: 2026-01-09
+updated: 2026-01-09
 ---
 
 # Slack Pulse Skill

package/dist/defaults/skill/thought-router/SKILL.md

@@ -1,13 +1,15 @@
 ---
 name: thought-router
-description: Quick capture tool that routes unstructured brain dumps to their correct home in the Thoth knowledge base.
-triggers:
-  - quick thought
-  - capture this
-  - brain dump
-  - remember this
-  - note this down
-  - dump
+version: 1.0.0
+description: The thought(s) to capture
+triggers: 
+inputs: 
+- name: content
+type: markdown
+required: true
+output: 
+created: 2026-01-09
+updated: 2026-01-09
 ---
 
 # Thought Router Skill