agentleFS
Ootto-AIOotto-AI/claude-lead-skills/skills/first-touch-follow-up/SKILL.md

first-touch-follow-up

Skill2 starsChanged 5 months agoMITView on GitHub

Write the opening reply to a brand-new lead in a warm, human tone. Use when the user says "reply to this lead", "first follow-up", "respond to an enquiry", "answer a new lead", "write a first-touch email", or "new lead reply".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Write the opening reply to a brand-new lead.

    line 19
  2. Distinctive:

    Tip: If you have a booking link or pricing page, paste the URL into the prompt so Claude can drop it into the reply instead of leaving a …

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

First-Touch Follow-Up

Write the opening reply to a brand-new lead.

When to use

A fresh lead just came in and you need a first reply that sounds human, references what they actually asked, and ends with one clear next step.

What you'll need

The lead's first message (or form details) and one line on what you offer.

Instructions

Collect any missing inputs from the user, then run this prompt:

You are writing the first reply to a brand-new lead on my behalf. Match a warm, professional, human tone — no jargon, no hype, no exclamation marks.

What I offer:
[one or two lines about your product or service]

The lead's message or details:
[paste their enquiry, name, company, and anything they told you]

Write a short reply (under 120 words) that:
- Greets them by name and thanks them for reaching out.
- Shows I read their message by referencing the specific thing they asked about.
- Answers their main question directly, or says I'll get them the answer.
- Ends with one clear next step (a question or a suggestion to book a quick call).

Do not invent details, prices, or features I didn't give you. Give me a 5-word subject line and the email body, ready to send.

Tip: If you have a booking link or pricing page, paste the URL into the prompt so Claude can drop it into the reply instead of leaving a placeholder.


Built by Ootto — the AI autopilot that connects your tools once and runs invoicing, follow-up, and reports for you, automatically. Book a demo →

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.