Generated banner for Weekly Prep Brief
Generated logo for Weekly Prep Brief

Weekly Prep Brief

AnthropicOfficialCreated by Common RoomDistributed by Anthropic

  • Skill
  • Content generator
  • Business and productivity
  • Apache-2.0
  • No issues found

From the author

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.
— the description by Common Room

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The weekly-prep-brief skill streamlines meeting preparation by compiling a structured, scannable document for all external calls scheduled over the next seven days. It integrates with calendar data to identify meetings, performs automated research on accounts and attendees using Common Room, and synthesizes the findings into a prioritized report. The skill includes logic for depth calibration based on account importance and provides a fallback format for meetings with limited data, ensuring reps receive actionable insights without fabricated information.

What it does

  • Fetches external meetings from the calendar for the upcoming week.
  • Performs automated account and contact research using Common Room.
  • Conducts targeted recency checks for noteworthy company or executive news.
  • Synthesizes research into a structured, date-sorted briefing document.
  • Prioritizes urgent signals like renewal risks or trial expirations in a week-level overview.
  • Adjusts research depth based on account priority and meeting type.

When to use it

  • At the start of the week to prepare for upcoming external calls.
  • When you need a consolidated view of account health and attendee context.
  • Before high-stakes meetings requiring specific preparation or executive involvement.
  • When you need to quickly identify which meetings require the most focus.

Advantages

  • Saves time by automating the gathering of account and contact intelligence.
  • Ensures consistent preparation quality across all external meetings.
  • Helps reps focus on high-priority accounts by flagging urgent signals.
  • Provides a scannable format optimized for quick reading.
  • Maintains transparency by clearly marking meetings with limited data.

Usage examples

“Prepare my week”
The agent fetches your external calendar events, researches the attendees and companies, and generates a structured briefing document for the next 7 days.
“What calls do I have this week?”
The agent lists your upcoming external meetings and asks for confirmation before proceeding to generate the full research brief.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/weekly-prep-brief/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip weekly-prep-brief.zip -d .agents/skills

Documentation by Common Room

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

Files

references/briefing-guide.md

Weekly Prep Brief — Structure and Edge Cases

Briefing Depth Guidelines

Calibrate research depth based on account type:

Account TypeDepth
Strategic account (large, high ARR)Full — account + all attendees
Active opportunity (open deal)Full — with emphasis on deal signals
Renewal within 90 daysFull — with emphasis on risk/health signals
Mid-market customer, routine callStandard — abbreviated account + key attendee
Small account, quick check-inMinimal — 3-4 bullets, single attendee
Brand new prospect (first meeting)Full contact + account — first impressions matter

Week Overview Priorities

Flag these situations prominently at the top of the brief:

  • Trial expiring within 7 days, renewal due within 30 days, or churn risk signals detected

  • Open critical support tickets or unresolved escalations

  • Expansion signals worth raising in the call

  • Executive stakeholder or new champion attending

  • Champion recently changed jobs or competitive signals in the account

  • Recent company funding, product milestone, or strong community advocacy (use as opener)

Edge Cases

  • No Common Room data: Note it explicitly, run external web research, recommend the rep check with their team for offline context.

  • Multiple meetings with the same company: Research the account once, share across meetings, differentiate by attendees and objectives.

  • 7+ meetings in a week: Ask whether to prioritize full research for specific accounts or run abbreviated prep for all; default to full for strategic.

  • Same-day meeting: Skip confirmation, produce compressed version (company snapshot + top signals + 1-2 talking points), mark as "[Quick Prep]".

  • Cancelled meetings: Exclude silently; if status is unclear, include with "[Status unclear — confirm this meeting is still on.]"

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Common Room
Publisher
Anthropic (Official)
Distributed by
Anthropic
Source
anthropics/knowledge-work-plugins · partner-built/common-room/skills/weekly-prep-brief · commit e050c2e
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from partner-built/common-room/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Common Room or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download weekly-prep-brief.zip