Agent skill

Sales Call Prep

by gooseworks-ai in gooseworks-ai/goose-skills

Pre-sales-call intelligence composite. An agent skill from gooseworks-ai/goose-skills.

MITAuto-check passedSales & Support

Install Sales Call Prep

skills CLI
$ npx skills add gooseworks-ai/goose-skills --skill sales-call-prep -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gooseworks-ai/goose-skills sales-call-prep --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sales/composites/sales-call-prep .claude/skills/sales-call-prep && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sales-call-prep
GitHub stars
1.2k
Used in
1 other repo
Token cost
~9.7k tokens
SKILL.md length
2,677 words
Files
2
Skills in repo
273
Repo updated
First seen
Licence
MIT

At a glance

Pre-sales-call intelligence composite. An agent skill from gooseworks-ai/goose-skills.

  • Works in 6 steps: Configuration (One-Time Setup) → Gather Context → Company Deep Dive → …
  • Tasks that involve Sales call preparation
  • SKILL.md covers When to Auto-Load, Step 0: Configuration…, Step 1: Gather Context and Step 2: Company Deep Dive, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sales Call Prep is an agent skill from gooseworks-ai/goose-skills. Pre-sales-call intelligence composite. Deep dives on the person AND their company before a sales call, then maps findings to your product to generate talking points, objection prep, and a call strategy. Goes beyond generic attendee research — this is sales-specific intelligence that helps SDRs, AEs, and founders walk into calls with a plan. Tool-agnostic — works with any CRM, research source, and calendar.

Its SKILL.md is about 9.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`).

It sits in Sales & Support, covering Sales call preparation and CRM management. The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.

When your agent uses it

  • Tasks that involve Sales call preparation
  • Tasks that involve CRM management

Example prompts

  • “/sales-call-prep”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Configuration (One-Time Setup)
  2. Gather Context
  3. Company Deep Dive
  4. Person Deep Dive
  5. Product-to-Prospect Mapping
  6. Generate Call Strategy & Brief

What it can do on your machine

Read from SKILL.md and the folder at commit c650c6d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sales Call Prep loads about 9.7k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 2,677 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~9.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 2,677 words, ~9,683 tokens.

Download SKILL.mdSave it as .claude/skills/sales-call-prep/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
sales-call-prep
description
Pre-sales-call intelligence composite. Deep dives on the person AND their company before a sales call, then maps findings to your product to generate talking points, objection prep, and a call strategy. Goes beyond generic attendee research — this is sales-specific intelligence that helps SDRs, AEs, and founders walk into calls with a plan. Tool-agnostic — works with any CRM, research source, and calendar.
version
1.1.0
tags
research

Sales Call Prep

The pre-call intelligence report that turns a 50/50 sales call into an 80/20 one. Researches the company (with a sales lens — not Wikipedia facts, but buying signals, pain indicators, competitive landscape, and budget context), researches the person (not just their bio, but their authority level, priorities, likely objections, and what they care about), then maps everything to your product to generate a specific call strategy.

What makes this different from meeting-brief:

Dimensionmeeting-briefsales-call-prep
FocusWho is this person?How do I sell to this person?
Company researchBasic overviewSales-lens: pain signals, budget indicators, competitive stack, decision process
Person researchLinkedIn + GitHub + newsAuthority mapping, buying style, priorities, likely objections
Product connectionNoneMaps your product's value to their specific situation
OutputBackground briefCall strategy with talk track, questions, and objection prep
AudienceAnyone with a meetingSDR, AE, founder walking into a sales call

When to Auto-Load

Load this composite when:

  • User says "prep me for my sales call", "call prep for [company]", "research [person] before our demo"
  • User says "I have a call with [person] at [company] tomorrow", "meeting prep for a prospect"
  • User has an upcoming meeting with a prospect (not an internal meeting, not a customer check-in)
  • An upstream workflow (meeting lifecycle, daily BDR rhythm) triggers call prep for sales meetings

Step 0: Configuration (One-Time Setup)

On first run, collect and store these preferences. Skip on subsequent runs.

Your Product Context
QuestionPurposeStored As
What does your company do? (2-3 sentences)Frame product-to-prospect mappingcompany_description
What problem do you solve?Identify if the prospect has this problempain_point
Who is your ideal buyer? (title, department)Map to the person on the callideal_buyer
What are your top 3 proof points? (customer, metric, result)Arm the seller with specific evidenceproof_points
What are the top 5 objections you hear? And how do you handle each?Pre-load objection handlingcommon_objections
What competitors do you run into? And what's your positioning against each?Competitive prepcompetitors
What's your pricing model? (ballpark)Budget qualification contextpricing_model
What does your typical sales process look like? (stages, timeline)Calibrate call objectives by stagesales_process
What discovery questions do you typically ask?Augment with prospect-specific questionsdiscovery_questions
Data Source Config
QuestionOptionsStored As
Where do you track deals?Salesforce / HubSpot / Pipedrive / Close / Supabase / Nonecrm_tool
Where do you track outreach?Smartlead / Instantly / Outreach / Noneoutreach_tool

Store config in the current working directory or wherever the user prefers.


Step 1: Gather Context

Purpose: Understand what this meeting is, who's attending, and what stage the deal is at. Pull any existing data from CRM/outreach history.

Input Contract
meeting_input: {
  # Option A: Calendar-driven (meeting already scheduled)
  calendar_event: {
    title: string
    date: string
    time: string
    attendees: [ { name: string, email: string } ]
    description: string | null
    meeting_link: string | null
  }

  # Option B: Manual input (user tells you who the call is with)
  manual: {
    person_name: string
    person_title: string | null
    person_email: string | null
    person_linkedin: string | null
    company_name: string
    company_domain: string | null
    meeting_type: string | null       # "discovery", "demo", "follow-up", "negotiation", etc.
    notes: string | null              # Any context the user provides
  }
}
Process
  1. Identify the prospect(s) from calendar or manual input. Filter out internal team members.

  2. Check ALL prior interaction sources (critical — do this before any web research):

    The goal is to reconstruct a complete interaction timeline before the call. Walking into a meeting without knowing you've already emailed someone, had a deal in pipeline, or that a teammate talked to their colleague is a credibility killer. Check every available source.

    A) CRM Records (Attio, Salesforce, HubSpot, Pipedrive, etc.)

    Check for BOTH the person AND their company. Pull:

    What to CheckWhat to PullWhy It Matters
    Company recordDoes the company exist in your CRM? What lists is it on?Shows if they're already a prospect, customer, or cold
    Contact recordDoes THIS person exist? Are there other contacts at the company?Tells you if a colleague already engaged with you
    Active dealsAny open deal for this company? Stage, value, owner, age?You might already be mid-cycle with them — don't restart the conversation
    Closed dealsAny won or lost deals? If lost, what was the reason?Lost deals = you know their objections. Won deals = upsell conversation.
    Deal notesNotes from previous calls, meetings, or interactionsRead every note — they contain gold for personalization
    Deal historyStage changes, timeline, velocityShows how fast (or slow) they move
    Other contacts at companyNames, titles, roles of other people you've talked toReference them: "I was speaking with [colleague] about..."
    Comments / activitiesAny logged calls, emails, tasks, or comments on their recordMay contain context that didn't make it into deal notes
    B) Outreach / Sequencing Tool (SmartLead, Instantly, Outreach, Lemlist, etc.)

    Search by email AND by name. Pull:

    What to CheckWhat to PullWhy It Matters
    Campaign membershipWere they in a campaign? Which one? When?You already reached out — don't pretend this is a cold intro
    Emails sentExact subject lines and email bodies you sent themKnow what you said so you don't repeat yourself or contradict it
    Their replyDid they reply? What did they say? Full reply text.Their exact words are the best conversation opener: "You mentioned X..."
    Lead categoryInterested / Not interested / Out of office / Bounced / etc.If they were marked "interested," you know their temperature
    Trigger signalWhat signal sourced this outreach? (hiring, funding, leadership change)Reference the original signal: "When we first reached out, it was because [signal]..."
    Sequence positionWhich email in the sequence did they respond to (or stop at)?Tells you what messaging resonated vs. fell flat
    Email account usedWhich sender mailbox was used?Know which "version of you" they interacted with
    C) Other Interaction Sources

    Check any additional places where prior contact may have occurred:

    SourceWhat to Check
    Client notes fileAny existing notes — may reference past conversations, call summaries, or decisions
    Previous content/outputsPast call preps, outreach drafts, or research that included this person or company
    CalendarPrevious meetings with this person or company
    LinkedIn messagesDirect messages or InMail exchanges (ask user if they recall any)
    Referral contextHow did this meeting come about? Warm intro from whom? Ask user.
    Shared Slack/email threadsAny back-channel conversations about this prospect
    D) Compile Interaction Timeline

    After checking all sources, build a chronological timeline of every touchpoint:

    interaction_timeline: [
      { date: "2026-01-15", type: "outreach_sent", detail: "Email 1 of hiring-signal campaign. Subject: 'The new CCO mandate'" },
      { date: "2026-01-18", type: "reply_received", detail: "Replied: 'Interesting, let's chat next month'" },
      { date: "2026-02-01", type: "deal_created", detail: "Deal created in Attio. Stage: Meeting booked. Value: $36K" },
      { date: "2026-02-10", type: "call_completed", detail: "Discovery call. Notes: 'Interested in outbound automation, evaluating Clay'" },
      { date: "2026-02-10", type: "deal_stage_change", detail: "Stage moved to Evaluation" },
    ]

    This timeline goes directly into the 30-Second Brief and Call Strategy. If you have prior interactions, the call type, opening line, and discovery questions all change:

    Prior InteractionHow It Changes the Call
    No prior interactionTrue cold discovery — qualify from scratch
    Outreach sent, no replyWarm-ish — they've seen your name. Reference the email: "I sent you a note about X a few weeks ago..."
    Outreach sent, they replied positivelyWarm — pick up where the conversation left off. Don't re-pitch.
    Outreach sent, they replied negativelyHandle carefully — they already said no. Understand why before re-engaging.
    Active deal in CRMYou're mid-cycle — this is a follow-up, not a discovery call. Read all notes.
    Lost deal in CRMRe-engagement — acknowledge the history: "I know we talked back in [month] and the timing wasn't right..."
    Colleague already engagedMulti-thread — reference the colleague: "I've been working with [name] on..."
  3. Determine call type and objective:

    Call TypeHow to DetectDefault Objective
    Cold discoveryNo prior deal, first meetingQualify: Do they have the problem? Budget? Authority? Timeline?
    Warm discoveryThey replied to outreach positivelyQualify + build rapport. They already showed interest — figure out why.
    DemoPost-qualification, scheduled demoShow value. Map product to their specific pain. Get next step.
    Follow-upPost-demo, they're evaluatingHandle objections. Introduce new proof. Advance to proposal.
    NegotiationProposal sent, discussing termsClose. Handle final objections. Align on timeline and terms.
    Champion callInternal champion, not decision makerArm the champion. Give them ammunition to sell internally.
    Executive meetingVP+ or C-suite involvedBe strategic, not tactical. ROI and vision, not features.
Output Contract
meeting_context: {
  call_type: string
  call_objective: string
  prospect: {
    name: string
    title: string | null
    email: string | null
    linkedin_url: string | null
    company: string
    company_domain: string | null
  }
  prior_interactions: {
    has_prior_contact: boolean           # Critical flag — changes the entire call approach
    interaction_timeline: [              # Chronological list of all touchpoints
      {
        date: string
        type: "outreach_sent" | "reply_received" | "deal_created" | "deal_stage_change" |
              "call_completed" | "note_added" | "linkedin_message" | "referral" | "other"
        source: "crm" | "outreach_tool" | "email" | "linkedin" | "notes" | "calendar" | "other"
        detail: string                   # What happened, in one sentence
      }
    ]
    crm_context: {
      company_record_exists: boolean
      contact_record_exists: boolean
      active_deal: {
        stage: string
        age_days: integer
        amount: number | null
        owner: string | null
        notes: string[]
      } | null
      closed_deals: [ { outcome: "won" | "lost", amount: number, reason: string | null } ]
      other_contacts: [ { name: string, title: string } ]
      comments_and_activities: string[]
    } | null
    outreach_context: {
      campaign_name: string | null
      campaign_status: string | null
      emails_sent: integer
      emails_sent_detail: [ { seq_number: integer, subject: string, date: string } ]
      their_reply: string | null         # Full reply text
      reply_date: string | null
      lead_category: string | null       # Interested, Not Interested, etc.
      trigger_signal: string | null      # What signal sourced the outreach
    } | null
    other_context: {
      client_notes_mentions: string[]    # Relevant mentions from notes.md
      previous_outputs: string[]         # Previous call preps, research, etc.
      referral_source: string | null     # How this meeting came about
    } | null
  }
  additional_attendees: [ { name: string, title: string } ] | null
}

Step 2: Company Deep Dive

Purpose: Research the prospect's company with a sales lens. Not a Wikipedia summary — focus on signals that indicate need, budget, urgency, and competitive landscape.

Input Contract
prospect: { company, company_domain, ... }  # From Step 1
your_company: { ... }                        # From config
Process

Research across seven dimensions. Use web search (always available) as the primary tool.

A) Company Overview (Quick Context)
What to FindWhere to LookWhy It Matters for the Call
What they do (1-2 sentences)Website, Crunchbase, LinkedInSets the context for everything else
Industry / verticalWebsiteDetermines which proof points to use
Company size (employees)LinkedIn, CrunchbaseMaps to pricing tier and complexity
HQ locationWebsiteTimezone, regional context
Founded yearCrunchbaseMaturity indicator
Business model (B2B/B2C/marketplace)WebsiteAffects how they think about tools
B) Financial & Growth Signals
What to FindWhere to LookWhy It Matters for the Call
Funding historyCrunchbase, web searchIndicates budget availability and growth stage
Last funding date + amountCrunchbase, press releasesRecent raise = fresh budget, evaluating vendors
Revenue estimate (if public or disclosed)Press, SEC filings, web searchBudget calibration
Growth trajectory (hiring velocity, office expansion)LinkedIn, job boardsGrowing = buying. Flat/contracting = harder sell.
Recent layoffsWeb search, newsBudget pressure — position as cost-saving, not cost-adding
C) Pain & Need Indicators
What to FindWhere to LookWhy It Matters for the Call
Job postings related to your product's domainLinkedIn Jobs, IndeedHiring for the role = they have the problem you solve
Complaints/challenges on social mediaLinkedIn posts, Twitter, RedditDirect evidence of pain you can reference
Industry-specific challengesIndustry reports, web searchCommon pain points they're likely facing
Recent company news that implies needPress, blog, LinkedInExpansion, new product, compliance change = new needs
Product reviews of their product (if applicable)G2, Capterra, app storesTheir customers' complaints may point to needs your product addresses
D) Technology & Competitive Stack
What to FindWhere to LookWhy It Matters for the Call
Current tools in your categoryJob postings (mentioning tools), website source, BuiltWithKnow what you're displacing or complementing
Competitor's product in use?Web search, job postings, LinkedIn mentionsPrepare competitive positioning
Tech stack (relevant parts)Job postings, websiteIntegration opportunities or blockers
Vendor evaluation signalsG2 comparisons, LinkedIn research postsActively shopping = high intent
Show full SKILL.md (1,067 more words)Show less
E) Decision-Making Landscape
What to FindWhere to LookWhy It Matters for the Call
Organizational structureLinkedIn, website team pageWho else is involved in the decision?
Other stakeholders (above/below the prospect)LinkedInWho do they report to? Who reports to them?
Recent leadership changesLinkedIn, web searchNew leader = re-evaluating stack
Company culture signalsGlassdoor, careers page, LinkedInFast-moving vs. bureaucratic affects sales cycle
Procurement styleCompany size indicatorSMB = founder decides. Enterprise = procurement process.
F) Relationship Mapping
What to FindWhere to LookWhy It Matters for the Call
Mutual connectionsLinkedInWarm intro potential, reference-ability
Past interactions with your companyCRM, outreach historyDon't repeat what they already know
Customer of a partner?Partner recordsPotential warm angle
In your existing customer's network?LinkedIn, web search"Your peer [company] uses us"
G) Recent Company News (Last 90 Days)
What to FindWhere to LookWhy It Matters for the Call
Product launchesBlog, pressNew products = new ops challenges
Partnerships announcedPress, LinkedInNew partnerships = integration needs
Awards / recognitionWeb searchCompliment material, shows what they're proud of
Controversies / issuesWeb searchLandmines to avoid
Earnings / performancePress, SECBusiness health indicator
Output Contract
company_research: {
  overview: {
    name: string
    description: string
    industry: string
    employee_count: string
    location: string
    founded: string
    business_model: string
  }
  financial: {
    funding_total: string | null
    last_round: { amount: string, stage: string, date: string } | null
    revenue_estimate: string | null
    growth_signal: "growing" | "stable" | "contracting" | "unknown"
  }
  pain_indicators: [
    { signal: string, source: string, relevance_to_product: string }
  ]
  tech_stack: {
    known_tools: string[]
    competitor_in_use: string | null
    integration_opportunities: string[]
  }
  decision_landscape: {
    decision_maker_likely: string     # Title of likely decision maker
    other_stakeholders: string[]
    procurement_style: "founder_led" | "committee" | "procurement" | "unknown"
    estimated_sales_cycle: string
  }
  recent_news: [
    { headline: string, date: string, relevance: string }
  ]
  relationship_map: {
    mutual_connections: string[]
    peer_customers: string[]          # Your customers in their network
    past_interactions: string | null
  }
}

Step 3: Person Deep Dive

Purpose: Research the specific person on the call. Not just their bio — understand their authority, priorities, communication style, and likely concerns.

Input Contract
prospect: { name, title, email, linkedin_url, company }  # From Step 1
company_research: { ... }                                  # From Step 2
your_company: { ... }                                      # From config
Process
A) Professional Profile
What to FindWhere to LookWhy It Matters
Current title + departmentLinkedInAuthority level, budget ownership
Time in current roleLinkedIn<6 months = new, evaluating stack. 2+ years = established, harder to displace incumbent
Career trajectoryLinkedIn experienceMoving up fast = ambitious, wants tools to accelerate. Lateral = stable, risk-averse.
Previous companiesLinkedInIndustry experience, tools they've used before
EducationLinkedInConversation starter, common ground
Skills / endorsementsLinkedInTechnical vs. business orientation
B) Authority & Buying Power Assessment
FactorHow to AssessImplication
Title levelVP+ = likely has budget. Director = may have budget. Manager = influencer, not buyer. IC = user/champion.Determines whether to talk ROI (buyer) or workflow (user)
DepartmentDoes their department buy your product?If they're in engineering and you sell to sales, they might be evaluating for someone else
Reports to whomLinkedIn org structureThe person above them is likely the decision maker if they're not
Team sizeLinkedIn, company pageLarger team = more at stake, bigger deal potential
Budget indicatorsTitle + company size + funding"Does this person plausibly control the budget for our product?"

Authority classification:

LevelWhoHow to Sell
Economic buyerVP+, C-suite, founderTalk ROI, strategic value, competitive advantage. Don't demo features.
Technical buyerDirector, senior manager, tech leadTalk capabilities, integrations, implementation. Demo the product.
ChampionManager, senior ICTalk workflow improvement, daily life impact. Help them build the internal case.
UserIC, operatorTalk ease of use, time savings, learning curve. Get them excited to use it.
EvaluatorAnalyst, consultantTalk data, comparisons, proof points. Be thorough and transparent.
C) What They Care About
What to FindWhere to LookWhy It Matters
Recent LinkedIn postsLinkedIn activityWhat are they thinking about? What problems are they voicing?
Articles they've sharedLinkedIn sharesWhat topics interest them?
Comments they've madeLinkedIn engagementWhat opinions do they hold?
Conference talks / webinarsWeb search, YouTubeWhat are they publicly expert in?
Published content (blog, podcast)Web searchDeep insight into their thinking
D) Communication Style Signals
SignalHow to DetectHow to Adapt
Data-drivenPosts include numbers, references studies, shares reportsLead with metrics and ROI. Bring a business case.
VisionaryPosts about trends, future of industry, big ideasLead with vision and strategic impact. Don't get stuck in details.
OperationalPosts about process, efficiency, team managementLead with workflow improvement and implementation ease.
SkepticalPosts questioning tools/trends, contrarian takesAnticipate tough questions. Lead with proof, not claims.
Relationship-orientedPosts about people, culture, team winsSpend time on rapport. Don't rush to the pitch.
E) Likely Objections (Predicted)

Based on their profile, company situation, and your common objections:

Their SituationLikely ObjectionPre-Load
Using a competitor"We already have [tool]"Prepare competitive positioning, switching cost analysis
Recently hired"I'm still getting up to speed"Position as "quick win for your first 90 days"
Small team / early stage"We can't afford this right now"Prepare ROI framing, start small options
Large enterprise"Our procurement process takes 6 months"Prepare for a longer cycle, ask about process early
Technical role"Does it integrate with [our stack]?"Prepare integration story
Recently burned by a vendor"We tried something like this before"Prepare "what's different" narrative
Output Contract
person_research: {
  profile: {
    name: string
    title: string
    department: string
    time_in_role: string
    previous_roles: [ { title: string, company: string, duration: string } ]
    education: string | null
  }
  authority: {
    level: "economic_buyer" | "technical_buyer" | "champion" | "user" | "evaluator"
    budget_authority: "confirmed" | "likely" | "unlikely" | "unknown"
    reports_to: string | null
    team_size: string | null
    assessment: string                # One-sentence assessment of their buying power
  }
  interests_and_priorities: {
    recent_posts_summary: string      # What they've been posting/sharing about
    key_topics: string[]              # Themes they care about
    public_opinions: string[]         # Positions they've taken publicly
    conversation_hooks: string[]      # Specific things to reference in the call
  }
  communication_style: {
    primary_style: string             # "data-driven", "visionary", "operational", "skeptical", "relationship-oriented"
    how_to_adapt: string              # Specific guidance
  }
  predicted_objections: [
    {
      objection: string
      likelihood: "high" | "medium" | "low"
      reasoning: string               # Why we predict this
      prepared_handle: string          # How to address it
    }
  ]
}

Step 4: Product-to-Prospect Mapping

Purpose: This is the core value-add. Map your product's capabilities to this specific prospect's situation. Not generic value props — specific connections based on the research. Pure LLM reasoning.

Input Contract
company_research: { ... }            # From Step 2
person_research: { ... }             # From Step 3
meeting_context: { ... }             # From Step 1
your_company: {
  description: string
  pain_point: string
  proof_points: string[]
  competitors: [ { name: string, positioning: string } ]
  pricing_model: string
  sales_process: string
  discovery_questions: string[]
}
Process
A) Value Mapping

For each pain indicator found in Step 2, map to a specific product capability:

Their Pain/NeedYour Product's AnswerProof PointHow to Say It
[pain from research][specific capability][customer/metric][one sentence pitch]
[another pain][another capability][proof][pitch]

Only include pains where there's a genuine connection. Don't force-fit.

B) Competitive Positioning (If Relevant)

If they're using or evaluating a competitor:

DimensionCompetitorYour ProductHow to Frame
[key differentiator 1][their approach][your approach][framing]
[key differentiator 2][their approach][your approach][framing]

Rules:

  • Never trash the competitor. Acknowledge what they do well. Differentiate on where you're stronger.
  • If you don't know the competitor, ask the prospect: "What do you like about [tool]? What's missing?"
  • Frame as "different approach" not "we're better"
C) Relevant Proof Points

Select 2-3 proof points most relevant to THIS prospect:

Proof PointWhy It's Relevant to Them
"[Customer] saw X% improvement"Same industry / same size / same problem
"[Metric] in [timeframe]"Matches their pain indicator
"[Company] switched from [competitor]"They're using the same competitor

Selection criteria: Same industry > same size > same problem > same competitor > general. Always choose the most specific proof point available.

D) Risk Factors & Landmines

Things that could derail the call:

RiskSourceMitigation
[risk — e.g., "just signed 2-year contract with competitor"][where you found this][how to handle]
[risk — e.g., "company culture is anti-vendor"][source][how to handle]
[risk — e.g., "recent bad press — sensitive topic"][source][avoid this topic]
Output Contract
product_mapping: {
  value_connections: [
    {
      their_pain: string
      your_answer: string
      proof_point: string
      how_to_say_it: string
      confidence: "strong" | "moderate" | "speculative"
    }
  ]
  competitive_positioning: {
    competitor_in_play: string | null
    differentiators: [ { dimension: string, their_approach: string, your_approach: string, framing: string } ]
    competitive_advice: string        # One paragraph on how to handle the competitive dynamic
  } | null
  relevant_proof_points: [
    { proof: string, why_relevant: string }
  ]
  risk_factors: [
    { risk: string, source: string, mitigation: string }
  ]
}

Step 5: Generate Call Strategy & Brief

Purpose: Synthesize everything into a single pre-call document with: executive brief, call strategy, talk track, discovery questions, and objection prep.

Input Contract
meeting_context: { ... }              # From Step 1
company_research: { ... }            # From Step 2
person_research: { ... }             # From Step 3
product_mapping: { ... }             # From Step 4
your_company: { ... }                # From config
Report Structure
# Sales Call Prep: [Person Name] @ [Company]
**Date:** [meeting date/time] | **Call type:** [discovery/demo/follow-up/etc.]
**Prepared for:** [user's name/role]

---

## 30-Second Brief

[4-5 bullet points. Everything you need if you have 30 seconds before the call.]

- **Who:** [Name], [Title] at [Company] — [authority level]. [Time in role].
- **What they do:** [Company] is a [1-sentence description]. [Size, industry, stage].
- **Prior interaction:** [CRITICAL — "No prior contact" OR "We emailed them on [date] about [topic], they replied [summary]" OR "Active deal in [stage] since [date]" OR "Lost deal [date] — reason: [reason]". This single line changes the entire call approach.]
- **Why this call:** [How this meeting came about — outreach reply, inbound, referral, etc.]
- **Key signal:** [The one thing that makes this call timely — funding, hiring, pain post, etc.]
- **Your angle:** [One sentence on why your product matters to them right now]

---

## Company Intelligence

### Overview
[2-3 sentences on what the company does, their market position, and current trajectory]

### Business Context
| Factor | Detail | Sales Relevance |
|--------|--------|----------------|
| Size | [employees] | [pricing tier / complexity indicator] |
| Funding | [last round] | [budget indicator] |
| Growth | [signal] | [expanding = buying, contracting = cost-cutting] |
| Industry | [vertical] | [which proof points to use] |

### Pain Signals Found
| Signal | Source | Connection to Your Product |
|--------|--------|--------------------------|
| [pain] | [where you found it] | [how your product addresses this] |
| [pain] | [source] | [connection] |

### Their Current Stack
| Category | Tool | Implication |
|----------|------|------------|
| [your category] | [competitor or unknown] | [displacement or greenfield opportunity] |
| [adjacent] | [tool] | [integration opportunity] |

### Recent News
| Date | Headline | Relevance |
|------|----------|-----------|
| [date] | [news] | [why it matters for this call] |

---

## Prior Interactions

[If no prior interactions exist, state "No prior contact found across CRM, outreach tools, or other sources. This is a true cold meeting." and move on.]

[If prior interactions exist, this section becomes one of the most important in the brief.]

### Interaction Timeline
| Date | Type | Source | Detail |
|------|------|--------|--------|
| [date] | [outreach_sent / reply / deal / call / etc.] | [CRM / SmartLead / email / etc.] | [What happened] |

### What They Already Know About You
[Based on the outreach and interactions above, summarize what this person already knows about your product/company. This prevents you from re-explaining things they've already heard.]

### What You Already Know About Them
[Based on replies, call notes, CRM notes — summarize what you've learned from prior interactions. These are conversation gold: "Last time we spoke, you mentioned X..."]

### How Prior Interactions Should Shape This Call
[Specific guidance on how to adjust the call approach based on history. Examples:]
- "They replied positively to your hiring-signal outreach — open by referencing that: 'You mentioned you were interested when we first reached out about [topic]...'"
- "Deal has been in Evaluation for 18 days with no movement — this is a re-engagement call, not a discovery call. Ask what's changed since the last conversation."
- "Your colleague [name] already talked to their VP Sales — reference that: 'I know [colleague] has been working with [their VP]...'"
- "They were marked 'Not Interested' in a previous campaign 3 months ago — acknowledge it: 'I know we reached out before and the timing wasn't right. What's different now?'"

---

## Person Intelligence

### Profile
[1-2 paragraphs on who this person is — not their resume, but what makes them tick.
What they care about, what they've been vocal about, what their priorities likely are.]

### Authority Assessment
| Factor | Assessment |
|--------|-----------|
| Authority level | [economic buyer / technical buyer / champion / user] |
| Budget authority | [likely/unlikely] |
| Reports to | [name/title] |
| Decision process | [solo / committee / procurement] |

### Communication Style: [Type]
[2-3 sentences on how to adapt your communication to this person.
E.g., "Lead with data — they post frequently about metrics and ROI.
Don't spend too long on rapport. Get to the numbers quickly."]

### Conversation Hooks
[3-5 specific things you can reference to show you've done your homework]
1. [Their recent post about X — use as an opener or bridge]
2. [A project they led at their previous company]
3. [Something from company news they're likely proud of]
4. [Mutual connection or shared experience]
5. [A comment they made about a problem you solve]

---

## Call Strategy

### Objective
**Primary:** [What you want to achieve in this call — e.g., "Qualify: confirm pain, budget, timeline, authority"]
**Secondary:** [Backup objective — e.g., "If not qualified, get referral to right person"]

### Agenda Suggestion
[A proposed call structure. Adapt to call type.]

| Phase | Time | What to Do |
|-------|------|-----------|
| **Open** | 2 min | [How to open — rapport hook, agenda set] |
| **Discovery / Context** | 10-15 min | [Key questions to ask — see below] |
| **Value / Demo** | 10-15 min | [What to show or discuss — see value connections] |
| **Next Steps** | 3-5 min | [What to propose — see below] |

### Opening Line
> "[Suggested opening — references a conversation hook and sets the agenda naturally.
  E.g., 'Thanks for making time, [Name]. I saw your post about [topic] — that's actually
  a big part of why I wanted to connect. I'd love to learn about how [Company] is
  handling [pain area] and see if what we're building is relevant. Sound good?']"

### Discovery Questions (Prioritized)

**Must-ask** (qualify the deal):
1. [Question that confirms they have the pain your product solves]
2. [Question about how they're handling it today — incumbent tool or manual process?]
3. [Question about timeline — are they actively evaluating or just learning?]
4. [Question about decision process — who else is involved?]
5. [Question about budget — how do they typically buy tools in this category?]

**Should-ask** (deepen the conversation):
6. [Question specific to their company situation from research]
7. [Question about their priorities for the next 6-12 months]
8. [Question that surfaces a pain they might not have articulated]

**Nice-to-ask** (if time allows):
9. [Question about their experience with competitors]
10. [Question about what a successful outcome looks like for them]

### Value Points to Make
[Ordered by relevance to THIS prospect — not your generic pitch deck]

1. **[Value point]** — [How to frame it for this prospect, using their specific situation]
   - Proof: [Relevant proof point]
   - Transition: [How to move from discovery to this point naturally]

2. **[Value point]** — [Framing]
   - Proof: [Proof]

3. **[Value point]** — [Framing]
   - Proof: [Proof]

### Proposed Next Step
[What to suggest at the end of the call, based on call type]

| Call Type | Suggest |
|-----------|---------|
| Discovery (qualified) | "Would it be helpful to see a demo tailored to [their specific use case]? I can have that ready by [date]." |
| Discovery (not sure yet) | "Let me put together a one-pager on how [peer company] handled this. Can I send it over and follow up [date]?" |
| Demo | "Based on what we covered, it sounds like [stakeholder] should probably see this too. Can we set up a follow-up with them?" |
| Follow-up | "I can have a proposal over by [date]. Would it be useful to include [specific thing they asked about]?" |
| Negotiation | "If we can align on [terms], we could have you live by [date]. What does your approval process look like from here?" |

---

## Objection Prep

[Pre-loaded responses for likely objections, ordered by predicted likelihood]

### [Objection 1 — Highest Likelihood]
**They'll say:** "[Exact wording of the objection]"
**Why:** [Why we predict this based on research]
**Handle:**
> "[Suggested response — acknowledge, reframe, proof point]"

### [Objection 2]
**They'll say:** "[Objection]"
**Why:** [Reasoning]
**Handle:**
> "[Response]"

### [Objection 3]
**They'll say:** "[Objection]"
**Why:** [Reasoning]
**Handle:**
> "[Response]"

---

## Landmines & Things to Avoid

- [Thing NOT to bring up and why — e.g., "Don't mention their recent layoffs. Still sensitive."]
- [Topic to avoid — e.g., "Don't reference competitor by name unless they bring it up first."]
- [Assumption NOT to make — e.g., "Don't assume they have budget authority — verify first."]

---

## After the Call

### Notes Template
After the call, capture:
- [ ] **Outcome:** Qualified / Not qualified / Needs follow-up
- [ ] **Key pains confirmed:** [What they actually said they struggle with]
- [ ] **Decision process:** [Who's involved, timeline, budget]
- [ ] **Next step agreed:** [What happens next]
- [ ] **Objections raised:** [What came up, how you handled it]
- [ ] **Competitive mentions:** [Any competitors discussed]
- [ ] **Follow-up items:** [What you promised to send/do]

© gooseworks-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/sales/composites/sales-call-prep of gooseworks-ai/goose-skills.

  • SKILL.md
  • skill.meta.json

Open the folder on GitHubat commit c650c6d

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Sales Call Prep next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sales Call Prep compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sales Call Prep this skillgooseworks-ai/goose-skills1.2k1 repos~9.7kAutomated safety check: PassMIT
SalesXiaomiMiMo/MiMo-Code14k—~637Automated safety check: PassMIT
Pp Clarifymvanhorn/printing-press-library2.1k—~8kAutomated safety check: NotesApache-2.0
Enterprise Customer Visit Playbookzj-unicom-ai/UniEmployee360—~458Automated safety check: PassMIT
GEO Prospect Trackerzubair-trabzada/geo-seo-claude11k—~1.7kAutomated safety check: NotesMIT
Luopan Company Researchzhangxiaoqiang1991/luopan389—~998Automated safety check: PassMIT

Similar skills

  • Sales

    XiaomiMiMo/MiMo-Code

    A skill your agent uses whenever Sales is explicitly invoked or the task involves customer meeting preparation, call follow-up, account prioritization, account signals, deal strategy, business…

    14k GitHub stars~637 tokensUpdated 2 days ago
    Sales & SupportAuto-check passed
  • Pp Clarify

    mvanhorn/printing-press-library

    Every Clarify API operation as a typed command, plus the morning briefing, meeting prep, and pipeline analytics the autonomous CRM knows about but cannot run.

    2.1k GitHub stars~8k tokensUpdated yesterday
    Sales & SupportAuto-check: notes
  • Enterprise Customer Visit Playbook

    zj-unicom-ai/UniEmployee

    Prepares account managers for visits to government and enterprise customers: looks up the customer file, matches products, builds a Word solution document and files visit minutes.

    360 GitHub stars~458 tokensUpdated 3 days ago
    Sales & SupportAuto-check passed
  • GEO Prospect Tracker

    zubair-trabzada/geo-seo-claude

    Tracks GEO agency leads and clients through a sales pipeline in a local JSON file, with notes, audit scores, deal values and a pipeline summary.

    11k GitHub stars~1.7k tokensUpdated yesterday
    Sales & SupportAuto-check: notes
  • Luopan Company Research

    zhangxiaoqiang1991/luopan

    罗盘的公司研究子模式。研究具体上市或非上市公司的财务增长、商业模式、 竞争生态位、治理与组织信号,并分别生成投资初筛和求职初筛。

    389 GitHub stars~998 tokensUpdated 2 mo ago
    Sales & SupportAuto-check passed
  • Company Research

    stophobia/deerflow2.0-enhanced

    综合企业背景调研技能,用于尽职调查、合作伙伴评估、投资分析、市场研究等场景。支持公司工商信息、财务数据、法律风险、舆情分析、竞品对比等多维度调研,自动生成Markdown和HTML格式的专业调研报告。触发条件:用户提及"企业调研"、"公司背景"、"尽职调查"、"合作伙伴评估"、"投资分析"、"市场研究"等关键词。

    822 GitHub stars~845 tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed

More from gooseworks-ai/goose-skills

All 273 skills in this repo
  • Reddit Post Finder

    gooseworks-ai/goose-skills

    Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Create Image Fal

    gooseworks-ai/goose-skills

    Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.

    1.2k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Render Hook Replacement

    gooseworks-ai/goose-skills

    Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.

    1.2k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed
  • Blog Feed Monitor

    gooseworks-ai/goose-skills

    Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.

    1.2k GitHub starsUsed in 1 repo~578 tokens
    Auto-check passed
  • Competitor Post Engagers

    gooseworks-ai/goose-skills

    Find leads by scraping engagers from a competitor's top LinkedIn posts.

    1.2k GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check: notes
  • Render Chatgpt Chat

    gooseworks-ai/goose-skills

    Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…

    1.2k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Sales Call Prep

What does Sales Call Prep do?

Pre-sales-call intelligence composite. An agent skill from gooseworks-ai/goose-skills. Sales Call Prep is an agent skill from gooseworks-ai/goose-skills. Pre-sales-call intelligence composite.

When should I use Sales Call Prep?

Sales Call Prep fits situations like: tasks that involve Sales call preparation; tasks that involve CRM management.

How do I install Sales Call Prep in Claude Code?

Run `npx skills add gooseworks-ai/goose-skills --skill sales-call-prep -a claude-code`. Or copy the skill folder (skills/sales/composites/sales-call-prep in gooseworks-ai/goose-skills) into .claude/skills/sales-call-prep in your project. Claude Code loads it when a task matches its description.

How do I install Sales Call Prep in Codex?

Run `npx skills add gooseworks-ai/goose-skills --skill sales-call-prep -a codex`. Or copy the skill folder (skills/sales/composites/sales-call-prep in gooseworks-ai/goose-skills) into .agents/skills/sales-call-prep in your project. Codex loads it when a task matches its description.

Can I use Sales Call Prep in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gooseworks-ai/goose-skills --skill sales-call-prep -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sales-call-prep, .gemini/skills/sales-call-prep, .github/skills/sales-call-prep and .opencode/skills/sales-call-prep in your project.

What does Sales Call Prep need to run?

SKILL.md names no scripts, command-line tools or credentials: Sales Call Prep is instructions for the agent only.

Does Sales Call Prep access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sales Call Prep safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sales Call Prep use?

Sales Call Prep is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sales Call Prep use?

About 9.7k tokens (SKILL.md is roughly 39k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sales Call Prep?

Skills that share tags, products or a category with Sales Call Prep: Sales (XiaomiMiMo/MiMo-Code, 14k stars), Pp Clarify (mvanhorn/printing-press-library, 2.1k stars), Enterprise Customer Visit Playbook (zj-unicom-ai/UniEmployee, 360 stars) and GEO Prospect Tracker (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sales Call Prep?

gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,240 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.

Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.