agentleFS
kelsi-bizerkelsi-bizer/bizer-ai-agent-skills/skills/lead-triage/SKILL.md

lead-triage

Skill0 starsChanged 4 months agoMITView on GitHub

Capture, qualify, and route every incoming lead so none slip through the cracks. Works from whatever the owner gives you — a name they mention, a web-form or social message, a call note, or an inbound email. Dedupes against people already known, records the lead with a fast qualification read, logs one concrete next step, and drafts a first reply. Use when someone reaches out about work, the owner mentions a new prospect, or a pile of inquiries needs sorting.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 6

    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. Distinctive:

    Run this loop for each new lead:

    line 20
  2. Distinctive:

    Before you create anything, check whether this person is already known — search your contacts/records.

    line 24
  3. Distinctive:

    If you have email/messaging tools, draft a short qualifying reply for the owner to approve — ask the one or two things you still need and …

    line 55
  4. Distinctive:

    When several leads come in at once, sort them out loud so the owner spends their time right:

    line 63
  5. Distinctive:

    Keep everything in the owner's voice, scaled to a solo operator — you're triaging their pipeline, not running a call center.

    line 76
  6. Distinctive:

    Never invent a lead's budget, timeline, or contact info.

    line 78

“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

Lead Triage

You help the owner capture and qualify inbound leads FAST, so nothing falls through the cracks. A lead is anyone who reaches out about work: a name the owner mentions, a web-form / social / call note, or an inbound email. The whole point is speed — a lead worked in the first hour beats a perfect write-up done tomorrow.

Work with whatever the runtime offers: contact/CRM tools and email if you have them; otherwise keep the record in your task tools, a file, or a clean running list the owner can see. The method is the same either way.

Run this loop for each new lead:

1. DEDUPE first

Before you create anything, check whether this person is already known — search your contacts/records. If they are, UPDATE the existing record instead of making a duplicate. Duplicates are how a lead gets two half-done follow-ups and no real one.

2. RECORD with a fast qualification read

Capture the lead, and while you're at it, size it up — don't just file a name. Get:

  • Source — how they found the business (referral, web, social, walk-by). Referrals and repeat sources are your best leads; note them.
  • What they want — the job, in their words.
  • Fit — is this work the owner actually does and wants?
  • Urgency — do they need it now, this month, or "someday"?
  • Rough budget — even a guess; it separates real jobs from window-shopping.
  • Serviceable? — location / scope the owner can actually take.

You won't have every field on every lead — capture what you have and note what's missing as the first thing to find out.

3. NEXT ACTION — one concrete step, with a date

Log exactly one next step, written as an action with a due date: "Call back Jane re: driveway quote — Thursday." Not "follow up with Jane." One dated action per lead is what turns a list of names into a worked pipeline. If you can schedule reminders, set it; if not, put the date on the list and surface it next time.

4. FIRST REPLY (when you can)

If you have email/messaging tools, draft a short qualifying reply for the owner to approve — ask the one or two things you still need and propose a next step (a call or a site visit). Don't interrogate them; two questions, warm, specific. If you can't send, draft it anyway so it's ready to copy-paste.

Triage by readiness

When several leads come in at once, sort them out loud so the owner spends their time right:

  • Ready to book — clear job, fit, urgency, budget in range. These get worked FIRST, today.
  • Warm / needs qualifying — real but missing a piece (budget, timing, scope). One question moves them up.
  • Tire-kickers / not a fit — no budget, wrong work, not serviceable. Say so plainly and give the owner a polite decline to send, so it's off the plate cleanly instead of haunting the list.

Honesty rules

  • Keep everything in the owner's voice, scaled to a solo operator — you're triaging their pipeline, not running a call center.
  • Never invent a lead's budget, timeline, or contact info; capture what's known and flag what isn't.
  • A qualified lead is a next action, not a filed note. Every lead ends this loop with a dated step or a clean decline — never in limbo.

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.