sales-qualification

sales-qualification is a skill for Claude Code, Codex from liqiongyu/lenny_skills_plus. It costs 22 tokens per session (2,261 once invoked), scanned A, original, Apache-2.0.

A sales process for deciding which potential customers are a good fit and whether an opportunity is ready to move forward.

In plain words
What is it for?
Use it to define an ideal customer profile, qualification questions, scoring rules, disqualification criteria, and stage requirements.
Why use it?
It prevents sales teams from spending time on poor-fit leads and keeps inactive deals from remaining in the pipeline.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to define an ideal customer profile, qualification questions, scoring rules, disqualification criteria, and stage requirements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/liqiongyu/lenny_skills_plus/sales-qualification
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add liqiongyu/lenny_skills_plus --skill sales-qualification
Clone the repo
git clone --depth 1 https://github.com/liqiongyu/lenny_skills_plus

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sales-qualification

README.md
[![agentmods](https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/sales-qualification/github.svg)](https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/sales-qualification)
Your own site
<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/sales-qualification"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/sales-qualification/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sales-qualification

Your own site · 80×15
<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/sales-qualification"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/sales-qualification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,261 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.02261
Opus 5 $0.00011 $0.01130
Sonnet 5 $0.00004 $0.00452
Haiku 4.5 $0.00002 $0.00226

Measured 9d ago against content hash af401e4b633c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sales-qualification scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sales-qualification/SKILL.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sales Qualification

Scope

Covers

  • Defining what “qualified” means for your business (fit + need + access + urgency)
  • Writing explicit disqualification rules to avoid time sinks
  • Creating a qualification scorecard that produces consistent decisions across reps
  • Designing a discovery/qualification call script that surfaces deal reality quickly
  • Setting stage exit criteria + “no next step, no stage” pipeline hygiene rules
  • Implementing a lightweight rollout + measurement plan for adoption

When to use

  • “Our pipeline is full but nothing closes—help us qualify better.”
  • “Create a lead qualification scorecard and disqualification criteria.”
  • “Write a discovery/qualification script for SDRs/AEs.”
  • “Define stage exit criteria so deals don’t rot in CRM.”
  • “We’re spending time on bad-fit leads—create rules to stop it.”

When NOT to use

  • You don’t have an ICP hypothesis or you’re still pre-problem/solution fit (start with founder-sales or problem-definition)
  • You need a full sales org design (roles, hiring, enablement system) rather than qualification (use building-sales-team)
  • You need to navigate a complex multi-stakeholder enterprise deal already in flight (use enterprise-sales)
  • You need to design OTE, quotas, or commission mechanics for reps (use sales-compensation)
  • You need pricing/packaging strategy, contracting, or legal/security review
  • You want lead scraping/spammy outreach or anything deceptive

Inputs

Minimum required

  • Product + target customer (1 sentence each)
  • ICP hypothesis (industry, size, buyer titles, “not for” exclusions)
  • Sales motion (inbound/outbound/PLG→sales/enterprise) + current stages (if any)
  • Typical deal profile (ACV range, cycle length, required stakeholders)
  • Current pain: what “bad leads” look like (examples of 3–5 recent losses or stalls)
  • Constraints: rep capacity, required response times, tooling (CRM), and handoff (SDR→AE)

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md (max 3–5 at a time).
  • If data is missing, proceed with explicit assumptions and ship two variants if needed: (A) “Simple SMB motion” vs (B) “Complex/enterprise motion”.

Read the full file on GitHub · 134 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 134 lines · 22 tokens per session scan A af401e4b633c

Subscribe to this mod's changes

sales-qualification is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 2,261 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.