Inspect a GEDCOM file with AI
Read the file version, encoding and record counts, then inspect an authorised record without exporting an entire family tree.
Inspect a GEDCOM file with AI when you have inherited an export and want to know what it contains before opening it in another genealogy program. The read-gedcom skill starts with the file version, encoding and record counts. A structural summary can answer a migration question without printing names or private family notes.
Decide how much information the task needs. An archivist checking whether family records exist may only need a count. A contributor investigating a single entry can request its identifier. A full JSON dump is available for authorised local processing but reveals more of the tree.
What it does
- Identify the GEDCOM version and declared character information.
- Compare counts of individual, family and source records.
- Inspect one authorised record by its cross-reference identifier.
- Read a targeted list without rewriting the original document.
- Choose plain text or structured output for a local review.
Install and use
- Give the agent an authorised GEDCOM file and the maker's official gedcom-lite command, available through normal Python packaging or uv. Keep sensitive material in the permitted environment.
- Ask, “Report the version and counts by record type. Leave names and notes out of this first inspection.”
- Request a specific record only if the summary leaves a question unresolved.
FAQ
Source
Made by Andrew Young (vaelen). Original skill: read-gedcom, published on GitHub under the MIT licence.
View on GitHub