agentleFS
Sign inStart free
runxhqrunxhq/runx/skills/lead-enrichment/SKILL.md

lead-enrichment

Skill97 starsChanged 33 days agoApache-2.0View on GitHub

Normalize factual person and company evidence for one confidently matched lead, preserving provenance, freshness, missing fields and conflicts.

12 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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    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:

    Do not claim that running this skill performs an Apollo lookup.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 11 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 Enrichment

Build factual context for one person or company. Enrichment answers what is known about the subject. lead-qualify decides whether those facts meet an ICP; cold-outreach prepares copy only after contact eligibility is supplied.

The default enrich runner reuses supplied structured evidence. It makes no provider request and spends no enrichment credits. An upstream declared connector operation can supply evidence; Apollo is the planned first lookup provider, whose credential presentation remains a native connector dependency. Do not claim that running this skill performs an Apollo lookup.

Procedure

  1. Bind one subject reference and the professional fields actually needed.
  2. Supply source references, native or upstream digests, observation times, explicit subject matches, and factual field/value pairs. A caller-supplied digest is provenance, not independent provider verification.
  3. Reuse only fresh sources confidently matched to that exact subject. A weak name match, stale observation or mismatched identity does not fill a field.
  4. Preserve conflicting values with their separate sources. Do not silently choose the latest value or invent a merged person from several matches.
  5. Return enriched, partial or needs_more_evidence, supported facts, missing fields, conflicts and the admitted source index.

The runner performs deterministic normalization rather than an extra model turn. Evidence acquisition and entity matching belong to the selected provider; commercial fit belongs to qualification. It does not infer buying intent, budget, consent, sensitive traits or private personal details.

Composition

Pass lead_enrichment_packet into lead-qualify#qualify together with the actual ICP criteria. Preserve the native artifact digest. For another lookup, request only missing professional fields with a bounded credit allowance and the same subject identity. Never enable personal-email/phone reveal or a waterfall merely to make an incomplete packet look complete.

The skill neither updates CRM records nor authorizes messages. The calling application owns refresh schedules and continuing work; connectors own exact provider requests, credential custody and billing evidence.

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