C✳CODEZ.WIN
🌐 English

Localized reading guide

call-prepPurpose, usage and source

Pre-call brief for an upcoming meeting - attendees, account history, prior call context from transcripts, open opportunity status, and suggested discovery questions. Use when the user asks "prep me for [meeting/company]", "call prep [company]", "I'm meeting with [company], prep me", "get me ready for [meeting]", or "what do I need to know before my [time] call".

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
sales/skills/call-prep/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Business
Last collected

License: License file needs review

Source SKILL.md

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

Pre-call brief for an upcoming meeting - attendees, account history, prior call context from transcripts, open opportunity status, and suggested discovery questions. Use when the user asks "prep me for [meeting/company]", "call prep [company]", "I'm meeting with [company], prep me", "get me ready for [meeting]", or "what do I need to know before my [time] call".

How the upstream workflow works

Step 1 - Ground

Check which tools are connected (plus any org facts the user or the project instructions already gave). Ground stage names and qualification framework from the live crm schema and org context (inferred from what is connected or uploaded; if the answer depends on a fact no one has given, ask ONE question, use the answer for this conversation and suggest adding it to the project instructions; otherwise use a clearly labeled default and continue)

Upstream passage · L33 ↗

Step 2 - Resolve the meeting

Calendar: find the event; extract title, time, attendees, agenda. From attendee domains, identify the customer company. No calendar connected: use an uploaded calendar export if present; otherwise ask for account + time in one question. If every calendar call is refused with a permission error, say plainly at the TOP of the brief that calendar is unavailable and the org's admin needs to enable it (Google Workspace admin for Google Calendar; Microsoft Entra consent or the Claude org's Microsoft 365 tool settings for Outlook); keep the connect-your-calendar tile, do not retry in a loop, and never present an empty calendar as if no meeting existed - ask for the account + time instead.

Upstream passage · L38 ↗

Step 3 - Account history

crm: account record, open opps (stage, amount, close date, next step, last activity), contacts matching attendees, recent activities. Files fallback: the matching rows of the uploaded book. transcripts: Gong plus meeting notes docs by title/attendee match (Gemini docs in Drive). Extract: key topics, open questions, commitments made, objections raised. Name the source per record. Gong returns cited answers, not transcript text: Call ask_account with the account ID from crm (not a typed name), default date window, sources on. One question per call: open questions and commitments on each side; objections and risks; who the stakeholders are and what they care about. For a specific open deal, ask_deal with the opportunity ID; if it searched 0 calls, the calls sit on the account - use the ask_account answers.

Upstream passage · L46 ↗
Upstream passage · ↗
tiers:
  files-only:   brief from uploaded book + pasted transcript/notes +
                stated meeting details
  read-only:    live calendar + crm + transcripts + email + chat reads
  gated-writes: none (prep only reads)

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

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Skill format and directory specification ↗

Read further in the source

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.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
4f772694f3f8fc1ef0d8bb8bb868f6c44661160f57c99dd8c9ebf97f7fe2a947
Back to the full Skill catalog