agentleFS
Sign inStart free
aiagentwithdhruvaiagentwithdhruv/skills/classify-leads/SKILL.md

classify-leads

Skill16 starsChanged 9 months agoMITView on GitHub

Classify leads using LLM for complex distinctions like product SaaS vs agencies. Use when user asks to classify leads, filter leads by type, or categorize businesses.

  • Reads credentials

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 2 are common, 0 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    NOT for simple categories (dentists, realtors)

    line 15
  2. Common:

    Default: includes "unclear" classifications (medium confidence)

    line 33

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LLM Lead Classification

Goal

Classify leads using Claude for complex distinctions that keyword matching can't handle.

When to Use

  • Product SaaS vs IT consulting agencies
  • High-ticket vs low-ticket businesses
  • Subscription vs one-time payment models
  • NOT for simple categories (dentists, realtors)

Scripts

  • ./scripts/classify_leads_llm.py - Main classification script
  • ./scripts/update_sheet.py - Update sheets
  • ./scripts/read_sheet.py - Read from sheets

Usage

python3 ./scripts/classify_leads_llm.py .tmp/leads.json \
  --classification_type product_saas \
  --output .tmp/classified_leads.json

Performance

  • ~2 minutes for 3,000 leads
  • ~$0.30 per 1,000 leads
  • Default: includes "unclear" classifications (medium confidence)

Classification Types

  • product_saas: Product companies vs service/consulting
  • Custom types can be added

Output

JSON file with classification added to each lead record.

Schema

Inputs

NameTypeRequiredDescription
leads_filefile_pathYesJSON file with lead data
classification_typestringYesClassification type (e.g., 'product_saas')
outputfile_pathNoOutput JSON file path

Outputs

NameTypeDescription
classified_filefile_pathJSON file with classification added to each lead

Credentials

NameSource
ANTHROPIC_API_KEY.env

Composable With

Skills that chain well with this one: scrape-leads, gmaps-leads, instantly-campaigns

Cost

$0.30 per 1,000 leads

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free