
weekly-prep-brief
โ Officialโ 22,378by anthropic ยท part of anthropics/knowledge-work-plugins
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.
This is the playbook your agent receives when the skill activates โ you don't need to read it to use the skill, but it's here to audit before installing.
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:
- Account research โ full account snapshot using the account-research skill
- 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]" newsscoped 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.)
npx skills add anthropics/knowledge-work-plugins --skill "weekly-prep-brief" --full-depthRun this in your project โ your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.
Licensed under Apache-2.0โ you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub โ