skills/sales-qualification/SKILL.md
Help users qualify sales leads effectively. Use when someone is wasting time on bad leads, struggling with low conversion rates, needs to build a qualification framework, or wants to improve their discovery process.
npx skillsauth add cvillamarp-lgtm/skillspodcast sales-qualificationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user qualify sales leads effectively using frameworks from 1 product leader.
When the user asks for help with sales qualification:
Jen Abel: "It's qualification. Qualification because if you spend your time on the wrong leads, that equates to a zero." If conversion rates are low, the issue is often pursuing leads that were never going to close rather than poor sales execution.
Jen Abel: "I am a qualification crazy person. I will not get in on another call with someone because on the first call it's either a yes or a no, there's no in between." The goal of early calls is to determine fit, not to convince. A clear "no" saves time that can be spent on better leads.
The best salespeople are rigorous about disqualification. They'd rather pursue fewer, better-qualified opportunities than spread themselves thin across mediocre leads.
If a lead requires multiple calls before you can determine whether they're a fit, your discovery process is too slow. Qualification should happen early and decisively.
Every hour spent on a bad lead is an hour not spent on a good one. The math of sales productivity favors aggressive filtering.
For all 2 insights from 1 guest, see references/guest-insights.md
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.