agentleFS
bookchaowalitbookchaowalit/platform-agent-skills/lead-research-and-crm/SKILL.md

lead-research-and-crm

Skill0 starsChanged 9 days agoApache-2.0View on GitHub

Research, qualify, organize, and follow up on potential clients and jobs for Solo Empire. Use when defining an ideal customer profile, building a lead list, preparing personalized outreach, updating a CRM pipeline, or deciding the next sales action.

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:

    Use permitted public or user-provided sources.

    line 13
  2. Distinctive:

    Never store passwords, tokens, payment data, or unnecessary sensitive personal data in CRM notes.

    line 25
  3. Distinctive:

    Keep research confidence and source date visible so old or weak information is not mistaken for current truth.

    line 26
  4. Distinctive:

    Do not send outreach or change an external CRM record without the required user approval and tool access.

    line 27

≈ “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 Research and CRM

Build a small, trustworthy pipeline whose next actions are clear and respectful.

Research workflow

  1. Define the ideal customer profile, offer fit, geography or market, trigger signals, disqualifiers, and the evidence needed to qualify a lead.
  2. Use permitted public or user-provided sources. Respect terms of service, robots rules, privacy expectations, rate limits, and opt-out requests.
  3. Normalize each record with name, organization, role, source URL, observed need, fit rationale, contact path, status, confidence, research date, owner, and next action.
  4. Deduplicate by person, organization, domain, and opportunity. Preserve the strongest source and keep uncertain matches marked for review.
  5. Score fit, urgency, budget likelihood, access to a decision maker, relevance of the trigger, and delivery capacity. Explain the score instead of presenting it as fact.
  6. Draft concise, personalized outreach based on observed evidence. State the relevant problem and a low-friction next step; avoid spam, scraping claims, fake familiarity, and unsupported promises.
  7. Record every approved touch, response, stage change, follow-up date, and reason for disqualification in the CRM or dashboard.
  8. Review stale leads on a schedule and close, nurture, or re-qualify them rather than allowing an unbounded backlog.

Pipeline rules

  • A lead is not qualified until the evidence supports need, fit, and a plausible path to a conversation.
  • A contact is not permission to send unlimited outreach. Honor consent, opt-outs, and applicable privacy rules.
  • Never store passwords, tokens, payment data, or unnecessary sensitive personal data in CRM notes.
  • Keep research confidence and source date visible so old or weak information is not mistaken for current truth.
  • Do not send outreach or change an external CRM record without the required user approval and tool access.

Metrics

Track qualified-lead rate, reply rate, meeting rate, proposal rate, win rate, time to next action, source quality, and revenue by offer. Use the metrics to improve targeting and the offer, not to justify low-quality volume.

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.