Menu

Individual skill

crm-enrichment-sync

0upvotes

Use this skill when a user has an approved set of enriched contacts and wants to create or update CRM records without duplicates, silent overwrites, or ambiguous writes. Produces a schema-aware field map, duplicate decisions, an exact create-update-skip plan, an approval gate, and a reconciliation receipt for every attempted record.

skills/nylan-richard/crm-enrichment-sync/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 enriched data is ready to cross the boundary into the CRM. It turns a contact file or result set into an explicit, reversible write plan before changing any system of record.

## Confirm the boundary

Require two inputs:

1. a bounded contact set with identity, enriched fields, quality status, and provenance;
2. an authenticated connection to the destination CRM that can inspect schema and search existing records.

Confirm the destination workspace, object type, owner or routing expectation, and business purpose. If the connector is absent or authentication fails, stop. Offer an import-ready file; never work around the missing connection.

The enrichment source is not the CRM writer. Keep retrieval and destination writes as separate operations with separate approvals.

## Read the destination schema
Back to top