shipshitdev/leads-researcher
bundles/sales/skills/leads-researcher/SKILL.md
This skill should be used when users need to research leads, find company information, discover contact details, or identify buyer intent signals. It activates when users ask about lead research, company research, contact discovery, buyer intent, or prospect research.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library leads-researcherInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 6:42 AM110.6s3 files scanned
SKILL.md
- name:
- leads-researcher
- description:
- This skill should be used when users need to research leads, find company information, discover contact details, or identify buyer intent signals. It activates when users ask about lead research, company research, contact discovery, buyer intent, or prospect research.
- version:
- 1.0.0
- tags:
- leads, research, sales
Leads Researcher
Overview
Research leads by gathering company information, discovering contact details, and identifying buyer intent signals. Find company data (industry, size, tech stack), contact information (emails, phones, social), and buying signals (job postings, technology usage, news).
When to Use This Skill
- Research companies or prospects
- Find company information (industry, size, location)
- Discover contact information (emails, phone numbers)
- Identify buyer intent signals
- Enrich lead data
- Find decision makers at companies
- Research tech stack or technology usage
Project Context Discovery
- Check for existing lead research tools or processes
- Review data sources and APIs in use
- Look for lead data schemas
- Check for compliance/privacy requirements
Research Workflows
1. Company Information
- Company name and legal name
- Industry and vertical
- Employee count and revenue
- Headquarters location
- Website and social profiles
- Technology stack
- Recent news or funding
2. Contact Discovery
Key Contacts to Find:
- CEO/Founder
- CTO/Technical decision makers
- Head of Sales/Marketing
- Department heads
- Procurement/Finance contacts
3. Buyer Intent Signals
- Job Postings: Hiring for relevant roles
- Technology Usage: Tools on website/job posts
- Company News: Funding, acquisitions, expansion
- Online Behavior: Website visits, content downloads
Data Sources
Company Data: Clearbit, ZoomInfo, Apollo.io, Crunchbase, LinkedIn Sales Navigator
Contact Discovery: Hunter.io, RocketReach, Lusha
Intent Signals: Job boards (LinkedIn, Indeed), BuiltWith, News API
Best Practices
- Comply with GDPR, CCPA, privacy regulations
- Verify information from multiple sources
- Use APIs to automate data gathering
- Always verify contact information
- Develop consistent intent scoring methodology
For complete API implementation examples, research methodology details, data source specifics, buyer intent scoring code, and example user requests, see: references/full-guide.md
Related Skills
shipshitdev/weekly-review
development
VerifiedTrustedCommunity
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/project-board
testing
VerifiedTrustedCommunity
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/board-sync
testing
VerifiedTrustedCommunity
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/how
development
VerifiedTrustedCommunity
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.
35SKILL.mdUpdated Aug 31, 2026