contact-hunter-skill
Search and extract contact information for people or companies including names, phone numbers, emails, job titles, and LinkedIn profiles. Aggregates data from multiple sources and provides enriched contact details. Use when users need to find contact information, build prospect lists, or enrich existing contact data.
What this skill does
# Contact Hunter <objective> Search and extract contact information for people or companies by aggregating data from multiple sources (LinkedIn, company websites, Apollo, Hunter.io, etc.). Provides structured search queries, email pattern detection, data enrichment guidance, and export-ready contact cards with full attribution and compliance notes. </objective> <quick_start> **Trigger:** "Find the VP of Sales at [Company]" or "Get contact info for [Name] at [Company]" **Input:** Person name, company, job title, location, or LinkedIn URL **Output:** Structured contact cards with email, phone, LinkedIn, verification steps, and export formats (CSV/JSON/vCard) </quick_start> <success_criteria> - [ ] Search type identified (person, company, role, email verification, bulk enrichment) - [ ] Structured search queries provided for LinkedIn, Google, company website - [ ] Email pattern detected with confidence level - [ ] Contact card populated with all available fields and source attribution - [ ] Verification steps included (cross-reference, format validation) - [ ] Compliance guidelines followed (public data only, GDPR/CAN-SPAM) </success_criteria> <workflow> ## Instructions When a user needs to find contact information: 1. **Identify Search Type**: - **Person search**: Find specific individual - **Company search**: Find people at a company - **Role search**: Find people with specific job title - **Email verification**: Validate and enrich existing email - **Bulk enrichment**: Enrich list of contacts 2. **Gather Search Parameters**: - Person name (first, last) - Company name - Job title / role - Location (city, state, country) - Industry - LinkedIn URL (if available) - Email domain - Any other identifying information 3. **Search Strategy**: **Sources to Check** (suggest to user): - LinkedIn (manual search with user's account) - Company website (About, Team, Contact pages) - GitHub (for developers) - Twitter/X profiles - Professional directories - Public databases - ZoomInfo (if user has access) - Apollo.io (if user has access) - Hunter.io (if user has access) - RocketReach (if user has access) **โ ๏ธ Important**: This skill GUIDES the search process. It doesn't directly access paid APIs. Instead, it: - Provides structured search queries - Suggests where to look - Helps organize found information - Validates and formats results 4. **Search Instructions Format**: ``` ๐ CONTACT SEARCH: [Name/Company] โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ ๐ SEARCH PARAMETERS โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ Target: John Smith Company: Acme Corp Title: VP of Engineering Location: San Francisco, CA โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ ๐ฏ RECOMMENDED SEARCH QUERIES โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ LinkedIn: 1. Search: "John Smith VP Engineering Acme Corp" 2. Use company filter: "Acme Corp" 3. Use title filter: "VP of Engineering" 4. Location: "San Francisco Bay Area" Google: 1. "John Smith" "VP of Engineering" "Acme Corp" 2. "John Smith" "Acme Corp" email 3. site:linkedin.com/in "John Smith" "Acme" 4. site:acme.com "John Smith" Company Website: 1. Check: https://acme.com/about 2. Check: https://acme.com/team 3. Check: https://acme.com/leadership 4. Check: https://acme.com/contact Email Pattern Guessing: Common patterns at acme.com: โข [email protected] โข [email protected] โข [email protected] โข [email protected] โข [email protected] GitHub (for technical roles): โข Search: "John Smith Acme" โข Look for company in bio โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ ๐ DATA COLLECTION TEMPLATE โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ Once you find the information, fill this template: Full Name: [First Last] Job Title: [Exact title] Company: [Company name] Email: [[email protected]] Phone: [(xxx) xxx-xxxx] LinkedIn: [linkedin.com/in/username] Location: [City, State/Country] Department: [Engineering, Sales, etc.] Additional Info: โข Reports to: [Manager name] โข Team size: [Number] โข Start date: [When they joined] โข Previous companies: [List] โข Education: [Degree, School] Data Sources: โข [LinkedIn profile URL] โข [Company website URL] โข [Other sources] โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ VERIFICATION STEPS โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ 1. Cross-reference multiple sources 2. Check LinkedIn profile matches company 3. Verify email format matches company pattern 4. Validate phone number format 5. Confirm job title is current 6. Check for recent company changes โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ ๏ธ COMPLIANCE & ETHICS โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โข Only use publicly available information โข Respect privacy and GDPR regulations โข Don't scrape private databases โข Honor do-not-contact preferences โข Use for legitimate business purposes only โข Keep CAN-SPAM compliance for cold outreach ``` 5. **Organize Results**: **Individual Contact Card**: ``` โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ JOHN SMITH โ โ VP of Engineering @ Acme Corp โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ ๐ง [email protected] โ โ ๐ฑ (415) 555-0123 โ โ ๐ผ linkedin.com/in/johnsmith โ โ ๐ San Francisco, CA โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ Department: Engineering โ โ Reports to: Sarah Chen (CTO) โ โ Team size: ~45 engineers โ โ Tenure: 2+ years at Acme โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ ๐ Sources: โ โ โข LinkedIn (verified) โ โ โข Company website โ โ โข Verified: 2024-01-15 โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ ``` **Bulk Results** (CSV/Excel format): ```csv Name,Title,Company,Email,Phone,LinkedIn,Location,Source,Verified John Smith,VP Engineering,Acme Corp,[email protected],(415) 555-0123,linkedin.com/in/johnsmith,San Francisco,LinkedIn,2024-01-15 Jane Doe,Director Marketing,Acme Corp,[email protected],(415) 555-0124,linkedin.com/in/janedoe,San Francisco,Company Website,2024-01-15 ``` 6. **Email Pattern Detection**: When searching company contacts, detect email patterns: ``` ๐ DETECTED EMAIL PATTERN: Acme Corp Confirmed Emails Found: โข [email protected] โข [email protected] โข [email protected] Detected Pattern: [email protected] Confidence: 95% Alternative Patterns (if primary fails): โข [email protected] โข [email protected] โข [email protected] To Verify Unknown Email: 1. Use email verification tool 2. Check for bounce/invalid 3. Look for SMTP response 4. Verify on LinkedIn ``` 7. **Data Enrichment**: For existing contacts, enrich with: - Current job title - Company changes - Updated contact info - Social profiles - Company information - Reporting structure - Recent activity/posts 8. **Export Formats**: - **CSV**: For CRM import - **JSON**: For API integration - **vCard**: For contact managers - **Salesforce CSV**: Pre-formatted for SFDC - **HubSpot CSV**: Pre-formatted for HubSpot ## Search Strategies **For Company Employees**: ``` site:linkedin.com/in "[Company Name]" OR site:[company-domain.com] "team" OR "about" OR "leadership" ``` **For Specific Roles**: ``` "[Job Title]" "[Company]" email OR "[Job Title]" site:linkedin.com "[Company]" ``` **For Email Validation**: - Check company website for email format - Use email verification services - Look for pattern in existing emails - Test with email finder tools *
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.