Weekly Prep Brief

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

AI-generated overview

Builds a weekly briefing on upcoming external customer and prospect calls with per-meeting account and contact research.

What it does
This skill gathers the next 7 days of external meetings, either from a connected calendar or from user-supplied input, and confirms the list before research begins. It then compiles account and contact research for each meeting, adds a limited recency check from web search, and produces one structured weekly brief sorted by meeting date and time. Meetings with sparse data get a compressed, explicitly flagged section instead of the full template.
When to use it
Use it for weekly planning when a rep or team needs preparation material for all external calls in the coming week. It fits requests such as a Monday prep brief or an overview of the week's customer and prospect meetings. It is not intended for internal-only meetings or one-off single-call prep.
Requirements
Requires a calendar connector for automatic meeting retrieval, or the user must supply meeting details manually. Research depends on Common Room data plus the account-research and contact-research skills, and web search access for recency checks. No scripts are included; the skill is instructions only, with a reference guide file.

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.

Briefing Process

Step 1: Get the Week's External Meetings

Option A — Calendar connected: Use the ~~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

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.

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
  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)

Step 4: Synthesize the Weekly Brief

Compile all per-meeting research into a single structured document, sorted by meeting date/time.

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

Output Format

# Weekly Prep Brief — Week of [Date]
## Week Overview[2–4 bullets: key themes, flagged priorities, call count]
---
## [Monday / Tuesday / etc.]
### [Company Name] — [Time]**Attendees:** [Names and titles]**Meeting type:** [Discovery / QBR / Renewal / Expansion / etc. — inferred if possible]
**Company Snapshot**[4–5 bullets: account status, top signals, recent activity]
**Attendee Profiles**- **[Name]** ([Title]): [2–3 bullets on their signals, persona, conversation angle]- [Repeat per attendee]
**Top Signals This Week**[2–3 most relevant signals for this specific call]
**This Week's News** [If notable news found][Only genuinely noteworthy findings — funding, leadership changes, major press]
**Recommended Objectives**[1–2 sentences: what to accomplish in this meeting]
---
[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

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.)

Source and attribution

Source:anthropics/knowledge-work-pluginsinpartner-built/common-room/skills/weekly-prep-briefat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today