Localized reading guide
weekly-prep-briefPurpose, usage and source
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.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
partner-built/common-room/skills/weekly-prep-brief/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Other
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
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.
How the upstream workflow works
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: Meeting date and time External attendee names and email addresses
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.
Upstream passage · L27 ↗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:
Upstream passage · L37 ↗### [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.Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
Quality Standards
Keep each meeting section scannable — reps read these in the morning, often on mobile Always sort by date/time ascending
Upstream passage · L115 ↗Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
3c6a45f653a6c0a7b1b52e2f11f937236164d0c3f4df0f9f86d354dc6d16de16