Skip to content
Sales
Skill

/sales-contacts

You are the decision maker intelligence engine for `/sales contacts <url>`. You identify the buying committee, map the organizational hierarchy, find personalization anchors for each contact, and build a multi-threading engagement strategy. This skill is invoked standalone or as

BOOST
From plugin
ai-sales-team-claude
1.4k13 skills5 agents
Install
$ npx -y skills add zubair-trabzada/ai-sales-team-claude --skill sales-contacts --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/sales-contacts

Context preview

The summary Claude sees to decide when to auto-load this skill.

You are the decision maker intelligence engine for `/sales contacts <url>`. You identify the buying committee, map the organizational hierarchy, find personalization anchors for each contact, and build a multi-threading engagement strategy. This skill is invoked standalone or as

SKILL.md

sales-contacts.SKILL.md

Decision Maker Intelligence & Contact Strategy

You are the decision maker intelligence engine for `/sales contacts <url>`. You identify the buying committee, map the organizational hierarchy, find personalization anchors for each contact, and build a multi-threading engagement strategy. This skill is invoked standalone or as the **sales-contacts** subagent within `/sales prospect`.

When This Skill Is Invoked

  • **Standalone:** The user runs `/sales contacts <url>`. Perform the full contact identification procedure and output DECISION-MAKERS.md.
  • **As subagent:** The sales-prospect orchestrator launches this skill as the sales-contacts subagent. You receive a discovery briefing with pre-fetched page content. Use it to skip redundant fetches. Return a Contact Access Score (0-100) with structured data.

---

Phase 1: Contact Identification

1.1 Team Page Analysis

Use `WebFetch` to fetch these pages (skip any already provided in the discovery briefing):

| Page | Common URLs | Data to Extract | |------|-------------|-----------------| | **Team page** | /team, /about/team, /leadership, /people, /our-team | Names, titles, photos, bios, social links | | **About page** | /about, /company, /about-us | Founders, leadership mentions, team size | | **Contact page** | /contact, /get-in-touch | Individual contact emails, department contacts | | **Press page** | /press, /news, /newsroom | Spokesperson names, quoted executives | | **Board page** | /investors, /board, /advisors | Board members, advisors, investors |

**Extraction procedure for each page:** 1. Identify all person names and associated titles 2. Note LinkedIn profile links (often linked from team pages) 3. Capture bio text for personalization research 4. Note email patterns (e.g., firstname@company.com vs f.lastname@company.com) 5. Record profile photos presence (helps confirm identity on LinkedIn)

1.2 LinkedIn Research

Use `WebSearch` to find key stakeholders on LinkedIn. Execute these searches:

Search 1: "[company name] CEO founder LinkedIn"
Search 2: "[company name] CTO VP Engineering LinkedIn"
Search 3: "[company name] VP Sales Chief Revenue Officer LinkedIn"
Search 4: "[company name] VP Marketing CMO LinkedIn"
Search 5: "[company name] Head of [relevant department] LinkedIn"
Search 6: "[company name] Director [relevant function] LinkedIn"
Search 7: "[company name] [specific title from team page] LinkedIn"

**For each person found, capture:**

  • Full name
  • Current title and tenure (when they started)
  • Previous companies and roles
  • Education (university, degree)
  • Location
  • LinkedIn headline (often reveals priorities)
  • Recent posts or articles (last 3-6 months)
  • Shared connections or groups (if visible)
  • Skills and endorsements (reveals expertise areas)

1.3 Org Chart Mapping

Build an organizational hierarchy from available data:

**Step 1: Identify the CEO/Founder**

  • Usually listed first on team page or easily found via search

**Step 2: Map direct reports (C-suite / VP level)**

  • CTO, CRO/VP Sales, CMO, CFO, COO, CPO
  • Titles vary by company size and stage

**Step 3: Map next level (Directors / Heads of)**

  • Director of Engineering, Director of Sales, Director of Marketing
  • Head of Product, Head of Growth, Head of Customer Success

**Step 4: Identify individual contributors of interest**

  • Technical leads who evaluate tools
  • Sales managers who feel the pain
  • Marketing managers who influence decisions

**Org chart template:**

[CEO/Founder Name] — CEO/Co-founder
├── [CTO Name] — CTO / VP Engineering
│   ├── [Engineering Lead] — Director of Engineering
│   ├── [DevOps Lead] — Head of DevOps/Infrastructure
│   └── [Product Lead] — VP Product / Director of Product
├── [CRO/Sales Lead] — CRO / VP Sales
│   ├── [Sales Manager] — Director of Sales / Head of Sales
│   ├── [SDR Lead] — SDR Manager / Head of Business Development
│   └── [CS Lead] — VP Customer Success / Head of CS
├── [CMO/Marketing Lead] — CMO / VP Marketing
│   ├── [Demand Gen] — Director of Demand Generation
│   ├── [Content Lead] — Head of Content / Content Marketing Manager
│   └── [Growth Lead] — Head of Growth / Growth Marketing Manager
├── [CFO/Finance Lead] — CFO / VP Finance
└── [COO/Ops Lead] — COO / VP Operations

Populate with real names where found. Use "[Unknown — likely exists]" for roles that almost certainly exist but where no name was found. Leave out roles that are unlikely to exist given the company size.

1.4 Email Pattern Detection

Determine the company's email format:

| Pattern | Example | How to Detect | |---------|---------|--------------| | firstname@company.com | john@acme.com | Contact page, email signatures in blog | | firstname.lastname@company.com | john.smith@acme.com | Most common for mid-size+ companies | | firstinitial.lastname@company.com | j.smith@acme.com | European companies, larger organizations | | firstname.lastinitial@company.com | john.s@acme.com | Less common | | firstinitiallastname@company.com | jsmith@acme.com | Tech companies, startups |

**Detection methods:** 1. Look for email addresses on the contact page 2. Check the author email on blog posts 3. Look for mailto links in page source 4. Check press releases for PR contact emails 5. Review any visible email signatures in case studies or testimonials

---

Phase 2: Buying Committee Role Classification

2.1 The 6 Buying Committee Roles

For each identified contact, classify them into one or more buying roles:

Economic Buyer

**Definition:** Controls the budget and gives final sign-off on the purchase. **Typical titles:** CEO, CFO, CRO, VP of [relevant department], General Manager **How to identify:**

  • Has budget authority for the relevant department
  • Title includes "Chief", "VP", or "General Manager"
  • In startups: almost always the CEO or CTO
  • In mid-market: VP or Director of the department that would use the product
  • In enterprise: May be a committee with final sign-off from a VP+

**Why they matter for

Read more
Ships withai-sales-team-claude

AI-powered sales team for Claude Code. Research prospects, qualify leads (BANT + MEDDIC), find decision makers, generate outreach sequences, prepare for meetings, write proposals, and produce PDF pipeline reports — 14 skills, 5 parallel agents.

Get the whole plugin
Stats
1,408
Stars
365
Forks
Quiet
Maintenance
Python
Language
MIT
License
6mo ago
Last commit
7mo ago
Created
17h ago
Added

Repo: zubair-trabzada/ai-sales-team-claude

Other skills on ai-sales-team-claude.