nw-entity-resolution
Cross-platform identity matching techniques for resolving entities across multiple OSINT sources, with confidence scoring framework, blocking strategies, and LLM-assisted validation.
npx skills add majiayu000/claude-skill-registry --skill nw-entity-resolution --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Entity Resolution ## When to Apply Apply entity resolution whenever data about the same entity arrives from 2+ sources. Common scenarios: - Same person name on GitHub, LinkedIn web profile, patent database, publication search - Same company name across registries, Crunchbase, news articles (with variations in legal form) - Cross-referencing board members across multiple company filings ## Company Name Normalization Before matching, normalize company names: 1. Strip legal suffixes: Inc, Corp, LLC, Ltd, GmbH, S.r.l., S.p.A., SA, SAS, AG, plc, NV, BV 2. Normalize abbreviations: "Intl" -> "International", "Tech" -> "Technology", "Sys" -> "Systems" 3. Lowercase, strip punctuation, collapse whitespace 4. Handle trade names vs legal names: "Google" vs "Alphabet Inc.", "Meta" vs "Meta Platforms Inc." Examples: - "Apple, Inc." -> "apple" - "APPLE COMPUTER INC" -> "apple computer" - "TechCorp S.r.l." -> "techcorp" - "Deutsche Bank AG" -> "deutsche bank" ## Person Name Matching Ranked by effectiveness for OSINT scenarios: **Jaro-Winkler**: Best for name variations. Prioritizes prefix similarity. Use for: "Marco" vs "Marc", "Rossi" vs "Rossy" **Levenshtein distance**: Good for typos and mino
- When to Apply
- Company Name Normalization
- Person Name Matching
- Confidence Scoring Framework
- Blocking Strategy
- LLM-Assisted Validation
- Common Pitfalls
- Output Format
What does the nw-entity-resolution skill do?
Cross-platform identity matching techniques for resolving entities across multiple OSINT sources, with confidence scoring framework, blocking strategies, and LLM-assisted validation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill nw-entity-resolution --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.