← UnabyssCONTENT HISTORY

Update to Unabyss

Snapshot Sep 30, 2026 · 22:48 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Generate a pre-call brief for upcoming meetings — who the attendee is, your history with them, their likely agenda, risks to watch for, and a suggested opening line. Use this skill whenever the user asks \"what's my next meeting\", \"who am I talking to today\", \"prep me for my call\", \"brief me before my meeting\", \"what do I know about [person] before our call\", \"upcoming meeting prep\", or anything that implies they want context before a meeting or call. Also trigger when someone says \"I have a call in 30 minutes\" or \"what should I know before talking to [name]\". Requires Unabyss MCP. Web search is used as fallback for unknown contacts.",
  "included_files": [],
  "name": "pre-call-brief",
  "skill_md_contents": "---\nname: pre-call-brief\ndescription: Generate a pre-call brief for upcoming meetings — who the attendee is, your history with them, their likely agenda, risks to watch for, and a suggested opening line. Use this skill whenever the user asks \"what's my next meeting\", \"who am I talking to today\", \"prep me for my call\", \"brief me before my meeting\", \"what do I know about [person] before our call\", \"upcoming meeting prep\", or anything that implies they want context before a meeting or call. Also trigger when someone says \"I have a call in 30 minutes\" or \"what should I know before talking to [name]\". Requires Unabyss MCP. Web search is used as fallback for unknown contacts.\n---\n\n# Pre-Call Brief\n\nFor each upcoming meeting with external attendees, produce a concise brief the founder can read in under a minute.\n\n> **Note:** This skill is well-suited for automation (e.g. polling calendar every 15 min and pushing briefs to Slack). The research logic is the same whether run manually or by an agent.\n\n## Required Integrations\n\nThis skill uses **Unabyss MCP** — `query` for upcoming meetings and known contacts, `agentic_query` for deeper history.\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 — Fetch upcoming meetings from Unabyss\n\nUse `query` to pull today's calendar context:\n\n```\nWhat meetings do I have today or coming up soon? Who are the external attendees — names, companies, email domains?\n```\n\nFilter to events with at least one external attendee. Extract: event title, start time, external attendee name + company/domain.\n\nIf no qualifying meetings are found: \"No upcoming external meetings found.\"\n\n### Step 2 — Check for prior context with `query`\n\nFor each external attendee, run a fast `query`:\n\n```\nDo I have any previous context about [Attendee Name] or [attendee-domain.com]?\n```\n\n- **KNOWN** — specific information exists → proceed to Step 3a\n- **UNKNOWN** — empty or vague → proceed to Step 3b\n\n### Step 3a — KNOWN: Deep history with `agentic_query`\n\n```\nGive me the full history with [Attendee Name] and [attendee-domain.com] — all interactions, ongoing projects, commitments made, open threads, anything unresolved.\n```\n\n### Step 3b — UNKNOWN: Web search\n\nSearch for `[attendee name] [company]` and `[domain] company` — what the company does, their role, anything publicly notable.\n\n### Step 4 — Synthesize the brief\n\n---\n\n**Pre-Call Brief**\n**[Event Title]** · [Start Time]\n**With:** [Attendee Name], [Company / Domain]\n\n**1. Who they are**\nOne sentence — role, company, what they do.\n\n**2. Our history**\nPast interactions, commitments, last touchpoint. If first contact: *First contact — no prior history.*\n\n**3. Their likely agenda**\nWhat they probably want from this call based on context.\n\n**4. Watch out for**\nOpen commitments, tensions, or anything that could come up unexpectedly. Omit if nothing relevant.\n\n**5. Suggested opening line**\nOne specific, concrete sentence to open — not generic.\n\n---\n\n## Output Rules\n\n- Use `query` before `agentic_query` — only escalate if prior context warrants deeper research\n- Never guess if the attendee is unknown — say so clearly\n- Keep each brief under 200 words\n- Multiple meetings get one brief each, separated by a divider\n"
}

SHA-256 of public snapshot: 07f9b9886217d6b76d940af4b53ebc381abdb92fc61ae107931b0afb106769d9