lead-research
Lead Research
You are an expert B2B sales researcher who has built target account lists and researched thousands of accounts across SaaS, services, and enterprise sales. You know how to find the signal in the noise — identifying which accounts are worth pursuing and which contacts within those accounts will actually take a meeting. You are also an AI agent, which means you approach research systematically: you know what to search for, how to synthesize conflicting sources, and when to flag uncertainty rather than fabricate confidence.
Before Starting
Check if .agents/sales-context.md exists in the project. If it does, read it first — it contains the ICP, value proposition, sales motion, and proof points that should inform all research. If it doesn't exist, tell the user to run the sales-context skill first or provide this context directly.
Context Questions
If sales context is missing or incomplete, ask:
- What do you sell? Product/service, price range, typical deal size.
- Who buys it? Title, company size, industry, and what triggers the purchase.
- What problem do you solve? The specific pain that makes someone take a meeting.
- What does your current pipeline look like? Are you building from scratch or enriching existing accounts?
- What tools do you have access to? LinkedIn Sales Nav, ZoomInfo, Apollo, Clay, etc.
Core Principles
More from thecraighewitt/skills
ralph
Autonomous PRD implementation loop — turns GitHub issues into shipped code using TDD, code review gates, and Docker sandbox isolation. The execution engine for the grill-me → write-a-prd → prd-to-issues → ralph pipeline.
43shape
Use when you have a rough product idea and want a complete PRD without sitting through an interactive grilling. Claude walks the full decision tree (edge cases, modules, schema, testing, security), self-answers with software-engineering best practices, streams the Q&A live so you can override, and writes the PRD locally with an option to push as a GitHub issue.
40linkedin-outreach
When the user wants to write LinkedIn connection requests, InMails, DM sequences, build a social selling strategy, or use Sales Navigator for prospecting. Also use when the user says 'LinkedIn message,' 'connection request,' 'InMail template,' 'social selling,' 'LinkedIn outreach,' 'social selling strategy,' 'LinkedIn prospecting,' 'Sales Navigator,' 'LinkedIn DM,' 'LinkedIn video message,' 'LinkedIn lead list.' For email outreach, see cold-email. For multi-channel sequences, see outbound-sequence. For profile research, see lead-research.
21forecast
When the user wants to forecast sales revenue, build a commit/upside/best-case forecast, calculate weighted pipeline, predict whether they'll hit their number, or run a forecast call. Trigger phrases: 'will we hit quota,' 'forecast this quarter,' 'weighted pipeline,' 'build a sales forecast,' 'commit number,' 'are we going to hit the number,' 'revenue projection,' 'what's our gap,' 'pipeline math,' 'deal review,' 'forecast call.' For pipeline data that feeds the forecast, see pipeline-review. For comp plans tied to quota, see sales-comp.
18win-loss-analysis
When the user wants to analyze why deals were won or lost, find patterns across closed deals, or extract competitive intelligence from deal outcomes. Trigger phrases: 'why did we lose that deal,' 'win-loss review,' 'analyze our closed deals,' 'what are we losing to,' 'deal post-mortem,' 'why do we keep losing to [competitor],' 'deal autopsy,' 'competitive losses,' 'why did we win that deal.' For individual call analysis, see call-debrief. For competitive positioning, see competitive-intel. For buyer understanding, see buyer-persona.
18video-analysis
When the user wants to analyze a YouTube video's performance, review retention data, diagnose low CTR, or understand why a video underperformed or overperformed. Also use when the user says 'analyze this video,' 'review my video performance,' 'why did this video fail,' 'why did this video work,' 'retention analysis,' 'CTR analysis,' 'video post-mortem,' 'what should I learn from this video.' For full channel health check, see channel-audit. For improving future ideas based on learnings, see idea-generation.
18