Update to Common Room

{
  "name": "weekly-prep-brief",
  "description": "Generate a comprehensive weekly briefing for all external calls in the next 7 days. Triggers on 'weekly prep brief', 'prepare my week', 'what calls do I have this week', 'Monday prep', or any weekly planning request.",
  "included_files": [
    {
      "relative_path": "LICENSE",
      "size_in_bytes": 11358
    },
    {
      "relative_path": "NOTICE",
      "size_in_bytes": 173
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 444
    },
    {
      "relative_path": "references/briefing-guide.md",
      "size_in_bytes": 1889
    },
    {
      "relative_path": "references/me-context.md",
      "size_in_bytes": 2103
    }
  ],
  "skill_md_contents": "---\nname: weekly-prep-brief\ndescription: \"Generate a comprehensive weekly briefing for all external calls in the next 7 days. Triggers on 'weekly prep brief', 'prepare my week', 'what calls do I have this week', 'Monday prep', or any weekly planning request.\"\n---\n\n# Weekly Prep Brief\n\nGenerate a single comprehensive weekly briefing that covers every external customer or prospect call in the next 7 days, with per-meeting account and contact research from Common Room.\n\n## Data Sources\n\nUse the Common Room MCP server as the primary account and contact source. If its tools are unavailable or unauthenticated, tell the user that the Common Room connection is required and stop before producing signal-backed briefings. Use an available calendar connector to retrieve meetings; otherwise collect meeting details from the user.\n\n## Briefing Process\n\n### Step 1: Get the Week's External Meetings\n\n**Option A — Calendar connected:**\nUse an available calendar connector to fetch all meetings scheduled in the next 7 days (or a user-specified range). Filter to keep only external meetings — those with attendees from outside your organization. Discard internal-only meetings, one-on-ones with colleagues, and recurring internal syncs.\n\nIdentify for each external meeting:\n- Company name\n- Meeting date and time\n- External attendee names and email addresses\n\n**Option B — No calendar connected:**\nAsk the user: \"To build your weekly prep brief, I'll need your upcoming external calls. Please list them: company name, date/time, and attendee names.\"\n\nAccept freeform input and parse it into a structured list before proceeding.\n\n### Step 2: Confirm the Meeting List\n\nPresent the identified meetings to the user for confirmation before beginning research:\n\n> \"Here are the external calls I found for this week. Let me know if anything's missing or should be excluded:\n> - [Company] — [Day], [Time] — [Attendees]\n> - ...\"\n\nThis prevents wasted research on cancelled or incorrect meetings.\n\n### Step 3: Research Each Meeting\n\nFor each confirmed external meeting, run in parallel where possible:\n1. **Account research** — full account snapshot using the account-research skill\n2. **Contact research** — profile for each external attendee using the contact-research skill\n\nCommon Room data is the primary source. After CR research, run a quick **recency check** for each company — this is supplementary, not primary:\n- Search `\"[company name]\" news` scoped to the last 7 days\n- For executive attendees, search their name for recent public posts or interviews\n- Only include findings that are genuinely noteworthy (funding, leadership changes, major press). Don't pad the brief with generic news.\n\nDepth calibration:\n- For high-priority accounts (large accounts, open opportunities, renewal risk), produce full depth research\n- For lower-priority or short meetings, produce abbreviated snapshots (3–4 bullets each)\n\n### Step 4: Synthesize the Weekly Brief\n\nCompile all per-meeting research into a single structured document, sorted by meeting date/time.\n\nOpen with a brief week-level overview that flags:\n- Any accounts with urgent signals (at-risk, trial expiring, expansion opportunity)\n- Any meetings that need special preparation or executive involvement\n- Total external call count and estimated time commitment\n\n## Output Format\n\n```\n# Weekly Prep Brief — Week of [Date]\n\n## Week Overview\n[2–4 bullets: key themes, flagged priorities, call count]\n\n---\n\n## [Monday / Tuesday / etc.]\n\n### [Company Name] — [Time]\n**Attendees:** [Names and titles]\n**Meeting type:** [Discovery / QBR / Renewal / Expansion / etc. — inferred if possible]\n\n**Company Snapshot**\n[4–5 bullets: account status, top signals, recent activity]\n\n**Attendee Profiles**\n- **[Name]** ([Title]): [2–3 bullets on their signals, persona, conversation angle]\n- [Repeat per attendee]\n\n**Top Signals This Week**\n[2–3 most relevant signals for this specific call]\n\n**This Week's News** [If notable news found]\n[Only genuinely noteworthy findings — funding, leadership changes, major press]\n\n**Recommended Objectives**\n[1–2 sentences: what to accomplish in this meeting]\n\n---\n\n[Repeat per meeting, sorted by date/time]\n```\n\n## When a Meeting Has Sparse Data\n\nIf Common Room returns limited data for a particular meeting's account or attendees, use a compressed format for that meeting instead of the full template:\n\n```\n### [Company Name] — [Time] ⚠️ Limited Data\n**Attendees:** [Names and titles if known]\n**Data available:** [What Common Room actually returned]\n\n**Web Search Results**\n[Findings from web search — company news, attendee LinkedIn profiles]\n\n**Note:** Common Room has limited data on this account. The rep may want to check directly in CR or gather context from colleagues before this call.\n```\n\nDo not generate a full meeting prep section (company snapshot, signal highlights, talking points, recommended objectives) from sparse data. A short honest section is more useful than a fabricated full one.\n\n## Quality Standards\n\n- Keep each meeting section scannable — reps read these in the morning, often on mobile\n- Always sort by date/time ascending\n- Flag urgent situations prominently (risk, trial expiration, open opps) — don't bury them\n- If a meeting has very thin Common Room data, use the sparse-data format above — never fill the full template with guesses\n- Total brief should be readable in 10–15 minutes for a week with 4–6 meetings\n- **Every fact must come from a tool call** — no invented deal context, activity, or signals\n\n## Reference Files\n\n- **`references/briefing-guide.md`** — guidelines for structuring briefings, prioritization logic, and how to handle edge cases (cancelled meetings, new accounts with no data, etc.)\n- **`references/me-context.md`** — current-user and My Segments scoping\n"
}