agentleFS
Sign inStart free
bobmmaobobmmao/agent-workflow-skills/skills/growth/lead-handoff/SKILL.md

lead_handoff

Skill0 starsChanged 5 months agoMITView on GitHub

Validate qualified distributor leads and write them into the shared approved_leads.jsonl handoff file for the sales agent

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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 this skill when a lead has already been qualified and is ready for sales outreach.

    line 7
  2. Distinctive:

    Only write leads that clearly passed qualification

    line 34
  3. Distinctive:

    Do not write generic marketing agencies, SEO sellers, link builders, lead generation services, fake directories, or incomplete contacts

    line 37
  4. Distinctive:

    Do not write leads with missing recipient name or missing email

    line 38
  5. Distinctive:

    Do not write duplicates intentionally.

    line 39
  6. Distinctive:

    Prefer concise notes describing why the lead passed

    line 40
  7. Distinctive:

    Read the JSON result and confirm whether the lead was added or skipped

    line 46

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

Use this skill when a lead has already been qualified and is ready for sales outreach.

Shared file:

  • ~/.openclaw/shared/leads/approved_leads.jsonl

Write command:

  • ~/.openclaw/workspace-crm/bin/lead_append_approved <json_file>
  • or pipe JSON directly into ~/.openclaw/workspace-crm/bin/lead_append_approved -

Accepted input:

  • one JSON object
  • a JSON array
  • JSONL

Minimum required fields:

  • company
  • contact_name
  • email

Recommended fields:

  • country
  • title
  • website
  • notes
  • source

Approval rules:

  • Only write leads that clearly passed qualification
  • The lead should be a real distributor, wholesaler, importer, retailer, marketplace seller, brand owner, or other plausible B2B channel partner
  • The lead must contain a real company identity and a usable business email or direct contact email
  • Do not write generic marketing agencies, SEO sellers, link builders, lead generation services, fake directories, or incomplete contacts
  • Do not write leads with missing recipient name or missing email
  • Do not write duplicates intentionally; the helper already deduplicates by email
  • Prefer concise notes describing why the lead passed

Suggested workflow:

  1. Build a JSON object with the approved lead fields
  2. Save it to a temp file
  3. Run ~/.openclaw/workspace-crm/bin/lead_append_approved <temp_file>
  4. Read the JSON result and confirm whether the lead was added or skipped

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