agentleFS
Sign inStart free
donnybacondigital-debugdonnybacondigital-debug/claude-code-business-kit/.claude/skills/lead-reply/SKILL.md

lead-reply

Skill0 starsChanged 2 months agoMITView on GitHub

Draft a fast, personal reply to an inbound lead (contact form, email, marketplace or portal enquiry) in the lead's own language, answering what they asked and asking up to three qualification questions, plus a structured CRM row. Use when the user pastes an enquiry from a potential client or asks to answer or qualify a lead.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Scino/fstack★ 18same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Answer what they asked first: If the answer is not in the company context, say you will confirm it.

    line 18
  2. Distinctive:

    If the reply is sent automatically in a real deployment, state clearly that it was prepared with an AI assistant, as required by local …

    line 43
  3. Distinctive:

    Do not send marketing to people who did not contact you.

    line 44
  4. Distinctive:

    Do not include personal data of other clients in replies.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 reply

The first business to answer well usually wins. This skill drafts the reply. A person reviews and sends it.

Inputs

  • The lead's message, with any form fields (name, email, phone, source, what they asked about).
  • CLAUDE.md for company context: services, prices you can share, availability, tone, the qualification questions that matter.

Steps

  1. Detect the language of the lead's message and write the reply in that language.
  2. Answer what they asked first. If the answer is not in the company context, say you will confirm it. Never invent availability, prices or features.
  3. Ask at most three qualification questions, chosen from the company's list in CLAUDE.md. If the list is missing, use: need or goal · timing · budget range or size.
    • Skip any question the lead already answered.
  4. Propose one concrete next step: a call slot, a visit, or a link. Only if CLAUDE.md allows it.
  5. Fill the CRM row with what is known. Use unknown for missing fields. Never guess.
  6. Score the lead hot, warm or cold from explicit signals only, and say which signals.

Output format

## Reply ([language])
Subject: [subject]

[reply, under 120 words, company tone]

## CRM row
| Name | Email | Phone | Source | Interest | Timing | Budget | Language | Score | Next step |
|---|---|---|---|---|---|---|---|---|---|

## Why this score
- [signal]

Rules

  • If the reply is sent automatically in a real deployment, state clearly that it was prepared with an AI assistant, as required by local transparency rules (e.g. EU AI Act art. 50).
  • Do not send marketing to people who did not contact you. This skill only answers inbound enquiries.
  • Do not include personal data of other clients in replies.

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