Normalize international phone numbers into E.164 before CRM imports or messaging workflows
Use libphonenumber-js when an agent needs to clean messy phone-number input, validate it against country rules, and return a stable E.164 value before storing contacts or triggering downstream messaging. The skill is about normalization and validation, not telephony delivery, call routing, or campaign orchestration.
npx skills add agentskillexchange/skills --skill normalize-international-phone-numbers-into-e164-before-crm-imports-or-messaging-workflows
Tool: libphonenumber-js. This skill lets an agent take raw phone-number input from forms, CSV exports, scraped datasets, or CRM records and turn it into a normalized value that downstream systems can trust. The core job is simple but important: parse the number, apply country-aware validation rules, and emit a stable representation such as E.164 so later steps do not fail because one record says (213) 373-4253 and another says +1 213 373 4253.
When to use it: invoke this skill before importing contacts, deduplicating lead lists, syncing data between CRMs, validating signup forms, or preparing outbound SMS or voice workflows. In those cases, using the product normally would mean hand-cleaning spreadsheet columns, guessing country defaults, or relying on brittle regex checks that miss valid international formats. An agent using libphonenumber-js can standardize the data, flag impossible numbers, and pass cleaner records to the next step.
Scope boundary: this is not a messaging API, telephony platform, call-routing system, or customer-engagement suite. It does not send SMS messages, buy numbers, or manage campaigns. Its boundary is much tighter: parse, validate, and format personal phone numbers so downstream systems receive consistent identifiers.
Integration points: form validation, CSV and spreadsheet imports, CRM deduplication jobs, contact enrichment pipelines, and outbound messaging preparation. Upstream evidence includes the official npm package, the maintained source repository, MIT licensing, and strong recent package adoption.