anthropics/knowledge-work-plugins

weekly-prep-brief

Generate a comprehensive weekly briefing for all external calls in the next 7 days.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill weekly-prep-brief

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
anthropics
公式

data-visualization

Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.

導入数
3
GitHub Stars
3.2万
更新日
10月22日
anthropics
公式

ux-copy

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

導入数
3
GitHub Stars
3.2万
更新日
10月22日
anthropics
公式

daily-briefing

Morning rundown - today's meetings with account context, opps closing soon with stale flags, waiting customer emails, and the day's top actions. Use when the user says "daily briefing", "daily brief", "morning briefing", "what's my day", "what's on my plate today", "prep my day", "start my day", "morning rundown", or on a schedule.

導入数
2
GitHub Stars
3.2万
更新日
10月22日
anthropics
公式

incident-response

Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

導入数
2
GitHub Stars
3.2万
更新日
10月22日