Individual skill

bulk-contact-enrichment

Use this skill when a user uploads a CSV or spreadsheet of contacts and wants verified work emails, phone numbers, or professional fields appended at scale. Produces a cleaned input, confirmed field mapping, bounded enrichment run, non-destructive merge, quality report, and export that preserves every original row and value.

skills/nylan-richard/bulk-contact-enrichment/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Use this when bulk enrichment must improve a file without turning it into an unauditable replacement. It produces an enriched export plus the counts and provenance needed to trust it.

## Establish the job

Ask where the file came from and what happens after enrichment: outreach, CRM import, event follow-up, recruiting, or research. Confirm the requested fields and whether the run should fill blanks only or also flag conflicting values for review.

Do not assume that a column named `email` is a work email, that `company` is the current employer, or that a full-name field is safely splittable. The downstream use determines which ambiguities matter.

## Profile before spending

Read the file without altering it. Report:

- row and column counts;
- encoding, delimiter, and header issues;
Back to top