fuzzy-name-matching

    Use when linking or deduping datasets by entity NAME because no shared key exists — 'fuzzy match', 'fuzzy name matching', 'entity resolution', 'record linkage', 'match company or person names', 'match these on the firm name', 'just merge these on company name', 'dedupe entity names', 'name-based join', 'these two files have no common id', or any use of char n-gram TF-IDF, cosine similarity on names, `sparse_dot_topn`, or RapidFuzz at scale. Use proactively whenever a join is about to be keyed on a name string, even if the user never says 'fuzzy'. NEGATIVE ROUTING: identifier bridging that a real link table already covers (gvkey ↔ permno via CCM, cik ↔ gvkey via wciklink) is the wrds skill — come here only for identifiers that genuinely do not cross vendors; the surrounding merge, sample-coverage and pipeline work is ds, not this skill.

    Rank#2300
    edwinhuskills.shWorkflow4Last updated Nov 14, 2026, 08:32 AMskills.sh/edwinhu/workflows/fuzzy-name-matching
    Created
    11 months ago
    Last commit
    6 days ago
    Latest release
    workflows--v5.103.14 months ago

    Security Findings

    Eval/exec with dynamic content

    SuspiciousAnalyzer

    Dynamic code execution: d=${CLAUDE_SKILL_DIR}; command -v skill-toc >/dev/null 2>&1 && exec skill-toc "$d"; s=$HOME/.claude/...

    Dynamic-context command auto-execution

    SuspiciousAnalyzer

    Command auto-executes from dynamic context before review: d=${CLAUDE_SKILL_DIR}; command -v skill-toc >/dev/null 2>&1 && exec skill-toc "$d"; s=$HOME/.claude/...

    No license file

    SuspiciousLineage

    No license file at the repo root and GitHub's licenseInfo is empty — code's legal status is unclear

    Versions

    2
    • Scanned Nov 14, 2026, 08:32 AMLow
    • Scanned Oct 9, 2026, 02:50 PMLow