Update to Unabyss

{
  "name": "week-in-review",
  "description": "Synthesize the past week into a concise founder-focused brief covering deals, customer escalations, product development, engineering risks, hiring signals, team sentiment, and investor updates. Use this skill whenever the user asks for a \"week in review\", \"weekly summary\", \"weekly brief\", \"what happened this week\", \"recap the week\", \"weekly digest\", \"catch me up on the week\", or anything that suggests they want a high-level synthesis of recent activity across their company. Also trigger when the user mentions wanting to \"start the week calibrated\" or \"review last week\". Requires Unabyss MCP.",
  "included_files": [],
  "skill_md_contents": "---\nname: week-in-review\ndescription: Synthesize the past week into a concise founder-focused brief covering deals, customer escalations, product development, engineering risks, hiring signals, team sentiment, and investor updates. Use this skill whenever the user asks for a \"week in review\", \"weekly summary\", \"weekly brief\", \"what happened this week\", \"recap the week\", \"weekly digest\", \"catch me up on the week\", or anything that suggests they want a high-level synthesis of recent activity across their company. Also trigger when the user mentions wanting to \"start the week calibrated\" or \"review last week\". Requires Unabyss MCP.\n---\n\n# Week in Review\n\nSynthesize the past week into a single, scannable brief from the founder's perspective. The goal: replace 60–90 minutes of tab-hopping with a 30-second read, so the founder walks into the new week already calibrated.\n\n## Required Integrations\n\nThis skill uses **Unabyss MCP** — specifically `agentic_query` for deep cross-source 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 — Run `agentic_query`\n\nThis skill needs synthesis across many sources — use `agentic_query`, not `query`:\n\n```\nLook across all my connected sources from the past 7 days and surface:\n- Top deals moving (or stalling) — any signals on pipeline\n- Customer escalations or complaints — anything urgent from customers\n- Product development — features shipped, decisions made, roadmap changes\n- Engineering risks — incidents, blockers, infra issues, technical debt flagged\n- Hiring signals — candidate updates, offer stages, rejections, referrals\n- Team sentiment — any friction, wins, morale signals in internal comms\n- Investor or board signals — any updates sent or received\n\nReturn raw signals, not a summary.\n```\n\nThen call `agentic_query_read` with the returned query id to retrieve the result.\n\n### Step 2 — Synthesize into bullets\n\nCompress signals into one bullet per theme:\n\n---\n\n**Week in Review — [Date Range]**\n\n- 🤝 **Pipeline** — [Top deal movements, notable stalls, wins/losses]\n- 🚨 **Customer** — [Escalations, churns, notable positive signals]\n- 🛠️ **Product** — [Features shipped, key decisions, roadmap shifts]\n- ⚙️ **Engineering** — [Risks, blockers, infra or technical issues]\n- 🧑‍💼 **Hiring** — [Candidate progress, open roles, team changes]\n- 💬 **Team & Investors** — [Sentiment, internal friction, any investor updates]\n\n---\n\n### Step 3 — Surface what needs attention\n\nAdd one line: **\"This week, watch:\"** — 1–2 items flagged for attention.\n\n## Output Rules\n\n- No generic statements — every bullet must reference something specific\n- If a category had no signal, write: \"[Category] — Quiet this week.\"\n- Keep total output under 300 words\n- No preamble — start directly with the header\n"
}