← UnabyssCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Unabyss
Snapshot Sep 30, 2026 · 22:48 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "focus-drift",
"description": "Compare what the user said they were focused on against what they have actually been working on, and surface the gap. Use this skill whenever the user asks about focus, priorities, drift, alignment, whether they are working on the right things, what they have been spending time on, why they feel scattered, or says things like are we focused, am I on track, what did I actually work on this week, or I feel like I am losing focus.",
"included_files": [],
"skill_md_contents": "---\nname: focus-drift\ndescription: \"Compare what the user said they were focused on against what they have actually been working on, and surface the gap. Use this skill whenever the user asks about focus, priorities, drift, alignment, whether they are working on the right things, what they have been spending time on, why they feel scattered, or says things like are we focused, am I on track, what did I actually work on this week, or I feel like I am losing focus.\"\n---\n\n# Focus Drift\n\nCompare stated priorities against actual activity and surface the gap — honestly, specifically, without softening it.\n\n## Required Integrations\n\nThis skill uses **Unabyss MCP** — `query` for stated priorities, `agentic_query` for activity synthesis.\n\n> If Unabyss is not connected, tell the user: \"This skill requires Unabyss MCP. You can connect it from the Tools menu.\"\n\n---\n\n## How to Run\n\n### Step 1 — Pull stated priorities with `query`\n\n`query` is sufficient here — stated priorities are usually in explicit documents or notes:\n\n```\nLook for documents, notes, or messages where I defined my goals, priorities, or focus areas — quarterly plans, OKRs, weekly intentions, strategy docs, or anything where I wrote down what I was going to work on. What did I say my priorities were for this period?\n```\n\nIf `query` returns nothing, ask the user to share their priorities before proceeding.\n\n### Step 2 — Pull actual activity with `agentic_query`\n\nActivity is scattered across many sources — use `agentic_query`:\n\n```\nLook across all connected sources from the last 3–4 weeks for evidence of what I actually spent time on — emails sent and received, messages, calendar events, documents edited, tasks completed, decisions made, and conversations had. What does the activity trail show I was actually focused on?\n```\n\nCall `agentic_query_read` with the returned query id to retrieve the result.\n\n### Step 3 — Synthesize the gap\n\n---\n\n**Focus Drift Report — [Date]**\n\n**📌 Stated priorities**\nWhat you said you were focused on — pulled from goals, plans, or notes.\n\n**📊 Actual focus**\nWhat the evidence shows you actually spent time on. Not what you intended — what the trail shows.\n\n**⚠️ The drift**\nWhere the two don't match. For each gap:\n- What was stated but not happening\n- What is happening but was never a stated priority\n- One honest sentence on what this suggests\n\n**🔧 What to realign**\n1–2 concrete adjustments based on what actually drifted.\n\n---\n\n## Output Rules\n\n- `query` first for priorities, `agentic_query` for activity — don't use `agentic_query` for both\n- Be direct — this skill is most useful when it's uncomfortable to read\n- Every point must reference something specific from Unabyss\n- No preamble before the report header\n- Keep the full output under 350 words\n"
}SHA-256: f74dac4690d29df46b29cf55b7d9ac4dcf11ccd6dd59500c65ddb7bc20173071