Claude Skill

discovery-call-assistant

Prepare discovery call questions, live-call structure, and post-call summaries that feed qualification and proposals. Use before and after prospect meetings.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_discovery-call-assistant-e9c73a3.zip · 1 KB
Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/discovery-call-assistant
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Discovery Call Assistant

Overview

Discovery quality determines everything downstream: qualification accuracy, proposal relevance, close rate. Prepare hard, listen more than pitch, capture verbatim.

Pre-call prep (the brief)

  1. account-research sheet: company, news, tech, likely pains
  2. Call goal: what must be true after 30 minutes to advance the deal?
  3. Question set (pick 8-10, ordered):
Theme Example questions
Trigger "Qu'est-ce qui fait que vous regardez ça maintenant ?"
Pain & cost "Que se passe-t-il si rien ne change ?" - chiffrer
Current state "Comment faites-vous aujourd'hui ? Qu'est-ce qui coince ?"
Decision "Qui d'autre est impliqué ? Comment se décide un projet comme ça chez vous ?"
Budget/timing "Une enveloppe est-elle définie ? Quelle échéance ?"
Success "À quoi ressemble une réussite dans 6 mois ?"

Post-call summary (within 2 hours)

## Discovery - <company> <date>
- Participants & roles
- Pain (their words, verbatim quotes)
- Cost of the problem: ...
- Decision process & players
- Budget/timing signals
- BANT-F scores → `lead-qualification`
- Objections heard
- Agreed next step + date
- Follow-up email draft (→ `meeting-followup`)

Store in sales/accounts/<company>/; sync to CRM (crm-update-agent).

Rules

  • 70/30 listening ratio: the question list is a map, not a script.
  • Never leave a call without a dated next step agreed aloud.
  • Verbatim beats paraphrase - proposals reuse their exact words.
Files (navin)
  • SKILL.md 1.8 KB
    ---
    name: discovery-call-assistant
    description: Prepare discovery call questions, live-call structure, and post-call summaries that feed qualification and proposals. Use before and after prospect meetings.
    metadata: {"navin":{"emoji":"🎧","category":"sales"}}
    ---
    
    # Discovery Call Assistant
    
    ## Overview
    
    Discovery quality determines everything downstream: qualification accuracy, proposal relevance, close rate. Prepare hard, listen more than pitch, capture verbatim.
    
    ## Pre-call prep (the brief)
    
    1. `account-research` sheet: company, news, tech, likely pains
    2. Call goal: what must be true after 30 minutes to advance the deal?
    3. Question set (pick 8-10, ordered):
    
    | Theme | Example questions |
    |-------|-------------------|
    | Trigger | "Qu'est-ce qui fait que vous regardez ça maintenant ?" |
    | Pain & cost | "Que se passe-t-il si rien ne change ?" - chiffrer |
    | Current state | "Comment faites-vous aujourd'hui ? Qu'est-ce qui coince ?" |
    | Decision | "Qui d'autre est impliqué ? Comment se décide un projet comme ça chez vous ?" |
    | Budget/timing | "Une enveloppe est-elle définie ? Quelle échéance ?" |
    | Success | "À quoi ressemble une réussite dans 6 mois ?" |
    
    ## Post-call summary (within 2 hours)
    
    ```markdown
    ## Discovery - <company> <date>
    - Participants & roles
    - Pain (their words, verbatim quotes)
    - Cost of the problem: ...
    - Decision process & players
    - Budget/timing signals
    - BANT-F scores → `lead-qualification`
    - Objections heard
    - Agreed next step + date
    - Follow-up email draft (→ `meeting-followup`)
    ```
    
    Store in `sales/accounts/<company>/`; sync to CRM (`crm-update-agent`).
    
    ## Rules
    
    - 70/30 listening ratio: the question list is a map, not a script.
    - Never leave a call without a dated next step agreed aloud.
    - Verbatim beats paraphrase - proposals reuse their exact words.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related