Back to Skills

Weekly Prep Brief

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.

$ npx promptcreek add weekly-prep-brief

Auto-detects your installed agents and installs the skill to each one.

What This Skill Does

This skill generates a weekly briefing for external customer or prospect calls, gathering account and contact research from Common Room. It's designed to help sales and customer success teams prepare for meetings by providing relevant background information. It can use calendar integrations or manual input.

When to Use

  • Prepare for upcoming sales calls.
  • Brief customer success on account status.
  • Quickly research meeting attendees.
  • Summarize key account information.
  • Identify recent news about a company.

Key Features

Connects to calendars to identify external meetings.
Performs account and contact research using Common Room.
Includes a recency check for recent news.
Allows manual input of meeting details.
Presents a consolidated briefing document.

Installation

Run in your project directory:
$ npx promptcreek add weekly-prep-brief

Auto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.

View Full Skill Content

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]" 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.)
0Installs
0Views

Supported Agents

Claude CodeCursorCodexGemini CLIAiderWindsurfOpenClaw

Details

License
MIT
Source
admin
Published
3/18/2026

Related Skills