sales-qualification
Skill9 starsChanged 6 months agoMITView on GitHub
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.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- meaningfy-ws/skillerytheir own version, first seen Nov 1, 2026
- sumitake/agent-skills-salestheir own version, first seen Sep 3, 2026
- Layneformalized225/ai-cofounderedited, first seen Mar 22, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Layneformalized225/ai-cofounder★ 197% same
Wrote their own version · 2
- meaningfy-ws/skillery★ 2same name
- sumitake/agent-skills-sales★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository78 other files it gives its agents.
- anti-pattern-auditSkill
- brand-storytellingSkill
- business-investigationSkill
- ceo-weekly-reviewSkill
- cold-emailSkill
- community-buildingSkill
- company-intelSkill
- competitive-analysisSkill
- competitor-researchSkill
- composio-cliSkill
- conducting-user-interviewsSkill
- content-strategySkill
- copywritingSkill
- daily-recapSkill
- decision-playbookSkill
- designing-growth-loopsSkill
- discovery-debriefSkill
- email-sequenceSkill
- enterprise-salesSkill
- evening-recapSkill
- exa-code-searchSkill
- exa-company-researchSkill
- exa-lead-genSkill
- exa-people-researchSkill
- exa-personal-siteSkill
- exa-x-searchSkill
- feedback-trackerSkill
- find-email-by-nameSkill
- focus-keeperSkill
- founder-salesSkill
- fpf-problem-solvingSkill
- github-stars-monitorSkill
- google-calendarSkill
- grafana-monitoringSkill
- humanizerSkill
- hypothesis-trackerSkill
- idea-generatorSkill
- install-openclaw-to-digitaloceanSkill
- install-openclaw-to-hetznerSkill
- install-openclaw-to-ycSkill
- launch-marketingSkill
- lead-enrichmentSkill
- measuring-product-market-fitSkill
- meeting-prepSkill
- metrics-briefingSkill
- morning-briefSkill
- openclaw-guideSkill
- openclaw-user-onboardingSkill
- orthogonalSkill
- outreach-senderSkill
- person-lookupSkill
- ph-launch-timelineSkill
- pipeline-managerSkill
- positioning-messagingSkill
- positioning-workshopSkill
- posthog-analyticsSkill
- prepare-yc-workshopSkill
- pricing-strategySkill
- problem-definitionSkill
- product-hunt-launchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
- Distinctive: line 9
Follow output preferences from USER.md (language, format, platform constraints).
- Distinctive: line 19
When the user asks for help with sales qualification:
- Distinctive: line 21
Understand current process: - Ask how they currently decide which leads to pursue
- Distinctive: line 23
Design discovery questions: - Create questions that efficiently reveal fit
- Distinctive: line 38
If a lead requires multiple calls before you can determine whether they're a fit, your discovery process is too slow.
- Distinctive: line 41
Every hour spent on a bad lead is an hour not spent on a good one.
- Distinctive: line 56
No disqualification criteria: - Not having explicit reasons to say no
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
[YOUR_PRODUCT] Context
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
Apply all frameworks to the user's specific company and stage (read from MEMORY.md).
Follow output preferences from USER.md (language, format, platform constraints).
For chat platforms: max 15 lines, no markdown tables, be concrete and actionable.
Sales Qualification
Help the user qualify sales leads effectively using frameworks from 1 product leader.
How to Help
When the user asks for help with sales qualification:
- Understand current process - Ask how they currently decide which leads to pursue
- Identify disqualification criteria - Help them define what makes a lead NOT worth pursuing
- Design discovery questions - Create questions that efficiently reveal fit
- Build a qualification framework - Help them systematize qualification decisions
Core Principles
Most sales problems are qualification problems
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.
"No" is a successful outcome
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.
Disqualify aggressively
The best salespeople are rigorous about disqualification. They'd rather pursue fewer, better-qualified opportunities than spread themselves thin across mediocre leads.
First call should determine fit
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.
Time is the scarcest resource
Every hour spent on a bad lead is an hour not spent on a good one. The math of sales productivity favors aggressive filtering.
Questions to Help Users
- "What percentage of your pipeline actually closes? Is the problem quality or execution?"
- "What are the characteristics of your best customers? How quickly can you identify those traits?"
- "What questions do you ask in discovery that reveal whether a lead is qualified?"
- "When was the last time you disqualified a lead on the first call?"
- "What would need to be true for you to walk away from a lead earlier?"
Common Mistakes to Flag
- Pursuing all inbound - Treating every lead as equally worthy of time
- Slow qualification - Taking multiple calls to determine what could be known in one
- Hope selling - Continuing to pursue leads you know aren't a fit because the pipeline looks thin
- No disqualification criteria - Not having explicit reasons to say no
- Confusing activity with progress - Measuring calls made rather than qualified opportunities created
Deep Dive
For all 2 insights from 1 guest, see references/guest-insights.md
Related Skills
- pipeline-manager — FIT+INTENT+TIMING scoring and routing
- founder-sales — sales strategy for early-stage
- enterprise-sales — complex deal qualification
- product-led-sales — qualifying PLG-to-enterprise expansion
- signal-scanner — signal-based qualification triggers
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

