Localized reading guide
call-prepPurpose, usage and source
Prepare for a customer or prospect call using Common Room signals. Triggers on 'prep me for my call with [company]', 'prepare for a meeting with [company]', 'what should I know before talking to [company]', or any call preparation request.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
partner-built/common-room/skills/call-prep/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- 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
Prepare for a customer or prospect call using Common Room signals. Triggers on 'prep me for my call with [company]', 'prepare for a meeting with [company]', 'what should I know before talking to [company]', or any call preparation request.
How the upstream workflow works
Step 1: Identify the Account and Attendees
Parse what the user has provided: Company name — required; look up the account in Common Room Attendee names — optional; if provided, research each one Calendar lookup: If a ~~calendar connector is available, search for upcoming meetings with the named company to automatically surface attendee names, meeting time, and any meeting notes or agenda. Use this to fill gaps the user didn't provide.
Step 2: Run Account Research
Use the account-research skill process to build a full account snapshot. For call prep, prioritize: Recent product signals (what are they doing in the product right now?) Open opportunities or renewal timeline Any risk signals (declining usage, support tickets, churned seats)
Upstream passage · L22 ↗Step 3: Run Contact Research for Each Attendee
For each external attendee, use the contact-research skill process. For call prep, focus on: Role and influence in the buying process Their personal activity and engagement history Any recent signals that suggest their current mood/priorities
Upstream passage · L32 ↗## Call Prep: [Company] — [Date/Time if known]
**Data available:** [List exactly what Common Room returned — e.g., "Name, title, email, two tags. No activity history, no scores, no Spark data."]
### What I Found
[Only the fields actually returned, presented as-is]
### Web Search Results
[Findings from web search on the company and attendees — or "No significant results"]
### Suggested Next Steps
- I can pull [specific field groups] from Common Room if available
- I can run deeper web searches on [specific topics]
- You may want to check Common Room directly for [what's missing]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
Ground every talking point in a real signal — no generic filler Keep the brief tight — it should be readable in 5 minutes or less
Upstream passage · L127 ↗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
- Call Prep
- Step 1: Identify the Account and Attendees
- Step 2: Run Account Research
- Step 3: Run Contact Research for Each Attendee
- Step 4: Synthesize Talking Points and Objectives
- Step 5: Recency Check (Web Search)
- Output Format
- When data is sparse (few fields returned, no activity, null sparkSummary):
- Quality Standards
- Reference Files
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
652c42776860edfa9b81c77aac0b545bb7748a708e01c001f356acc11d7e9f58