Build, maintain, and debug hierarchical gazetteers for genealogy place resolution.
npx skills add https://github.com/jonaseck2/slaktforskning --skill gazetteers
Please help me install this Agent Skill. Skill: gazetteers Source: https://github.com/jonaseck2/slaktforskning/tree/main/.claude/skills/gazetteers Command: npx skills add https://github.com/jonaseck2/slaktforskning --skill gazetteers
Gazetteers turn human place strings into structured place matches for genealogy workflows, so you can reliably resolve things like "Roskilde, Danmark" to coordinates and a correct hierarchy.
Use the gazetteers skill to diagnose why a specific place query resolves incorrectly and to determine which build script or normalization rule needs to be changed.
High-intent search queries and answers about installing and using this skill.
To resolve genealogy place strings, you use hierarchical gazetteers and a resolver pipeline to parse human place strings into structured matches with accurate coordinates and hierarchy. The pipeline applies normalization, hierarchy scoring, and mechanical merging rules to ensure deterministic outputs.
Place query resolution mismatches occur when normalization rules, alias data, or hierarchy scoring in the gazetteer pipeline are misconfigured. You can debug this by investigating coordinate, alias, type, or hierarchy mismatches and adjusting the relevant build script or normalization rule.
Adding a new country or language contribution to a place gazetteer involves extending the dataset with new admin levels and boundary layers. You must adhere strictly to the closed node type vocabulary and run deterministic rebuild scripts to generate the updated derived JSON.
The best way to maintain gazetteer data integrity is to rebuild deterministic outputs strictly from canonical source datasets. You must avoid hand-editing derived JSON and rely on mechanical merging rules and deterministic rebuild scripts to ensure reproducibility and non-persistence of gazetteer-derived values.
Yes, the gazetteer resolver pipeline supports integrating Wikidata and GeoNames data. These sources feed into the canonical datasets used by the deterministic rebuild scripts to generate the structured place matches, aliases, and coordinates for genealogy workflows.
A key limitation of mechanical merging rules is that they require strict contract adherence to a closed node type vocabulary, meaning any deviation breaks the deterministic rebuild. Additionally, gazetteer-derived values are non-persistent and must not be hand-edited, limiting manual overrides.
jonaseck2Audit genealogy place resolution against a SQLite database and bucket outlier mismatches.
SCStelzRender interactive world maps of attack origins from Sentinel coordinate data.
dchukAdd or update fetch pipeline stages in SourceMonitor with a call(source:, result:) interface.
chebizarroQuery the Google Places API for text search, place details, and location resolution.
