← Common RoomCONTENT HISTORY

Update to Common Room

Snapshot Nov 11, 2026 · 00:08 UTC · version 4.2.0

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for weekly-prep-brief

Skill instructions — Now says: For each external meeting, note the company, the date and time, and the external attendees' names and emails. Before researching, show the meetings found...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Common Room and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Sep 30, 2026 · 22:52 UTC

Generate 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. Identify for each external meeting: - Company name -...

After

Nov 11, 2026 · 00:08 UTC

For each external meeting, note the company, the date and time, and the external attendees' names and emails. Before researching, show the meetings found (company, day, time, attendees) and ask whether anything is missing or should be ex...

Supporting files

Before

Sep 30, 2026 · 22:52 UTC

[{"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...

After

Nov 11, 2026 · 00:08 UTC

[{"relative_path":"LICENSE","size_in_bytes":11358},{"relative_path":"NOTICE","size_in_bytes":173},{"relative_path":"agents/openai.yaml","size_in_bytes":447},{"relative_path":"references/briefing-guide.md","size_in_bytes":1889}]

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -5,8 +5,6 @@
 
 # Weekly Prep Brief
 
-Generate 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.
-
 ## Data Sources
 
 Use 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.
@@ -18,49 +16,28 @@
 **Option A — Calendar connected:**
 Use 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.
 
-Identify for each external meeting:
-- Company name
-- Meeting date and time
-- External attendee names and email addresses
+For each external meeting, note the company, the date and time, and the external attendees' names and emails.
 
 **Option B — No calendar connected:**
 Ask 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."
 
-Accept freeform input and parse it into a structured list before proceeding.
-
 ### Step 2: Confirm the Meeting List
 
-Present the identified meetings to the user for confirmation before beginning research:
-
-> "Here are the external calls I found for this week. Let me know if anything's missing or should be excluded:
-> - [Company] — [Day], [Time] — [Attendees]
-> - ..."
-
-This prevents wasted research on cancelled or incorrect meetings.
+Before researching, show the meetings found (company, day, time, attendees) and ask whether anything is missing or should be excluded.
 
 ### Step 3: Research Each Meeting
 
-For each confirmed external meeting, run in parallel where possible:
-1. **Account research** — full account snapshot using the account-research skill
+For each confirmed meeting, in parallel where possible:
+1. **Account research** — account snapshot using the account-research skill
 2. **Contact research** — profile for each external attendee using the contact-research skill
 
-Common Room data is the primary source. After CR research, run a quick **recency check** for each company — this is supplementary, not primary:
-- Search `"[company name]" news` scoped to the last 7 days
-- For executive attendees, search their name for recent public posts or interviews
-- Only include findings that are genuinely noteworthy (funding, leadership changes, major press). Don't pad the brief with generic news.
-
-Depth calibration:
-- For high-priority accounts (large accounts, open opportunities, renewal risk), produce full depth research
-- For lower-priority or short meetings, produce abbreviated snapshots (3–4 bullets each)
+Then a recency check per company, secondary to the Common Room data: search `"[company name]" news` for the last 7 days and, for executive attendees, their name for recent posts or interviews. Include only noteworthy findings (funding, leadership changes, major press).
 
-### Step 4: Synthesize the Weekly Brief
+Research high-priority accounts (large, open opportunity, renewal risk) at full depth; give lower-priority or short meetings 3–4 bullets each.
 
-Compile all per-meeting research into a single structured document, sorted by meeting date/time.
+### Step 4: Synthesize the Weekly Brief
 
-Open with a brief week-level overview that flags:
-- Any accounts with urgent signals (at-risk, trial expiring, expansion opportunity)
-- Any meetings that need special preparation or executive involvement
-- Total external call count and estimated time commitment
+Compile one document sorted by meeting date and time. Open with a week overview that flags accounts with urgent signals (at risk, trial expiring, expansion opportunity), meetings needing special preparation or executive involvement, and the external call count with estimated time.
 
 ## Output Format
 
@@ -76,7 +53,7 @@
 
 ### [Company Name] — [Time]
 **Attendees:** [Names and titles]
-**Meeting type:** [Discovery / QBR / Renewal / Expansion / etc. — inferred if possible]
+**Meeting type:** [Discovery / QBR / Renewal / Expansion / etc. — say if inferred]
 
 **Company Snapshot**
 [4–5 bullets: account status, top signals, recent activity]
@@ -99,33 +76,8 @@
 [Repeat per meeting, sorted by date/time]
 ```
 
-## When a Meeting Has Sparse Data
-
-If 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:
-
-```
-### [Company Name] — [Time] ⚠️ Limited Data
-**Attendees:** [Names and titles if known]
-**Data available:** [What Common Room actually returned]
-
-**Web Search Results**
-[Findings from web search — company news, attendee LinkedIn profiles]
-
-**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.
-```
-
-Do 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.
-
-## Quality Standards
-
-- Keep each meeting section scannable — reps read these in the morning, often on mobile
-- Always sort by date/time ascending
-- Flag urgent situations prominently (risk, trial expiration, open opps) — don't bury them
-- If a meeting has very thin Common Room data, use the sparse-data format above — never fill the full template with guesses
-- Total brief should be readable in 10–15 minutes for a week with 4–6 meetings
-- **Every fact must come from a tool call** — no invented deal context, activity, or signals
+**Sparse data:** when Common Room returns little for a meeting's account or attendees, mark that meeting "Limited Data", show only what was returned plus any web findings, and say what's missing so the rep can check before the call. Don't fill the template; every fact must come from a tool call.
 
 ## Reference Files
 
 - **`references/briefing-guide.md`** — guidelines for structuring briefings, prioritization logic, and how to handle edge cases (cancelled meetings, new accounts with no data, etc.)
-- **`references/me-context.md`** — current-user and My Segments scoping
Full technical diff · 2 changed fields

changed /included_files

BEFORE
[
  {
    "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
  }
]
AFTER
[
  {
    "relative_path": "LICENSE",
    "size_in_bytes": 11358
  },
  {
    "relative_path": "NOTICE",
    "size_in_bytes": 173
  },
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 447
  },
  {
    "relative_path": "references/briefing-guide.md",
    "size_in_bytes": 1889
  }
]

changed /skill_md_contents

BEFORE
"---\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"
AFTER
"---\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\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\nFor each external meeting, note the company, the date and time, and the external attendees' names and emails.\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\n### Step 2: Confirm the Meeting List\n\nBefore researching, show the meetings found (company, day, time, attendees) and ask whether anything is missing or should be excluded.\n\n### Step 3: Research Each Meeting\n\nFor each confirmed meeting, in parallel where possible:\n1. **Account research** — account snapshot using the account-research skill\n2. **Contact research** — profile for each external attendee using the contact-research skill\n\nThen a recency check per company, secondary to the Common Room data: search `\"[company name]\" news` for the last 7 days and, for executive attendees, their name for recent posts or interviews. Include only noteworthy findings (funding, leadership changes, major press).\n\nResearch high-priority accounts (large, open opportunity, renewal risk) at full depth; give lower-priority or short meetings 3–4 bullets each.\n\n### Step 4: Synthesize the Weekly Brief\n\nCompile one document sorted by meeting date and time. Open with a week overview that flags accounts with urgent signals (at risk, trial expiring, expansion opportunity), meetings needing special preparation or executive involvement, and the external call count with estimated time.\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. — say if inferred]\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**Sparse data:** when Common Room returns little for a meeting's account or attendees, mark that meeting \"Limited Data\", show only what was returned plus any web findings, and say what's missing so the rep can check before the call. Don't fill the template; every fact must come from a tool call.\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"
Full snapshot data
{
  "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": 447
    },
    {
      "relative_path": "references/briefing-guide.md",
      "size_in_bytes": 1889
    }
  ],
  "name": "weekly-prep-brief",
  "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\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\nFor each external meeting, note the company, the date and time, and the external attendees' names and emails.\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\n### Step 2: Confirm the Meeting List\n\nBefore researching, show the meetings found (company, day, time, attendees) and ask whether anything is missing or should be excluded.\n\n### Step 3: Research Each Meeting\n\nFor each confirmed meeting, in parallel where possible:\n1. **Account research** — account snapshot using the account-research skill\n2. **Contact research** — profile for each external attendee using the contact-research skill\n\nThen a recency check per company, secondary to the Common Room data: search `\"[company name]\" news` for the last 7 days and, for executive attendees, their name for recent posts or interviews. Include only noteworthy findings (funding, leadership changes, major press).\n\nResearch high-priority accounts (large, open opportunity, renewal risk) at full depth; give lower-priority or short meetings 3–4 bullets each.\n\n### Step 4: Synthesize the Weekly Brief\n\nCompile one document sorted by meeting date and time. Open with a week overview that flags accounts with urgent signals (at risk, trial expiring, expansion opportunity), meetings needing special preparation or executive involvement, and the external call count with estimated time.\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. — say if inferred]\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**Sparse data:** when Common Room returns little for a meeting's account or attendees, mark that meeting \"Limited Data\", show only what was returned plus any web findings, and say what's missing so the rep can check before the call. Don't fill the template; every fact must come from a tool call.\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"
}

SHA-256 of public snapshot: d4d30b318b7eec2716ec8c00386e07b88eef02106bc127eb570b2ab5dc4f9fec