fuzzy-matching

Match vendor SKUs to inventory items using PostgreSQL trigram indexes.

783|62|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/dadbodgeoff/drift --skill fuzzy-matching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fuzzy-matching
Source: https://github.com/dadbodgeoff/drift/tree/main/drift%20v1%20depreciated/skills/fuzzy-matching
Command: npx skills add https://github.com/dadbodgeoff/drift --skill fuzzy-matching

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of accurately matching and reconciling entities (like inventory items or products) that have variations in their names, formats, or details, preventing duplicates and ensuring data consistency.

Core Features & Use Cases

  • Multi-stage Fuzzy Matching: Employs a three-stage pipeline for efficient and accurate matching: PostgreSQL trigram pre-filtering, salient overlap checks, and multi-factor similarity scoring.
  • Entity Reconciliation: Ideal for matching vendor SKUs to inventory items, deduplicating products across different sources, or reconciling entities with inconsistent naming conventions.
  • Use Case: Automatically match incoming vendor SKUs like "BNLS CHKN BRST 10LB" to your existing inventory items, even if your internal names are slightly different, like "Boneless Chicken Breast - 10 lb Bag".

Quick Start

Use the fuzzy-matching skill to find similar items for 'BNLS CHKN BRST 10LB' in the 'poultry' category for user 'user_123'.

Frequently Asked Questions about fuzzy-matching

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I match vendor SKUs to inventory items with inconsistent naming formats?

To match vendor SKUs to inventory items with inconsistent names, use multi-stage fuzzy matching. This process applies PostgreSQL trigram pre-filtering, salient overlap checks, and weighted similarity scoring for accurate entity reconciliation.

What is the best way to deduplicate products across different sources in PostgreSQL?

Deduplicating products across sources requires multi-stage fuzzy matching in PostgreSQL. It uses trigram indexes for efficient pre-filtering, then applies multi-factor similarity scoring with configurable thresholds to identify and reconcile duplicate entities.

How does trigram indexing speed up fuzzy matching for large datasets?

Trigram indexing accelerates fuzzy matching by breaking strings into character sequences for rapid PostgreSQL pre-filtering. This narrows down potential matches before executing computationally intensive multi-factor similarity scoring on the full dataset.

Can I configure similarity thresholds for entity reconciliation?

Yes, entity reconciliation supports configurable thresholds for similarity scoring. You can adjust these parameters to control match strictness, balancing precision and recall when reconciling entities with varying name formats or details.

Do I need Python to run multi-stage fuzzy matching with PostgreSQL?

Yes, multi-stage fuzzy matching requires Python alongside PostgreSQL. The pipeline combines Python's processing capabilities with PostgreSQL trigram indexes to execute pre-filtering, overlap checks, and weighted similarity scoring efficiently.

Why does standard exact matching fail for reconciling entities with varying name formats?

Exact matching fails for entity reconciliation because it cannot handle abbreviations or formatting differences. Fuzzy matching solves this by using trigram overlap and weighted similarity scoring to match strings like 'BNLS CHKN BRST' to 'Boneless Chicken Breast'.