Gedcomx
- 388 repo stars
- Updated April 29, 2026
- FamilySearch/gedcomx
gedcomx is an agent skill that generates and validates GEDCOM X genealogical data for structured family-history applications.
About
gedcomx is an agent skill that teaches and operationalizes the GEDCOM X standard for genealogical data—so you can produce, inspect, and validate family-history records without guessing XML/JSON shapes. Developers use it when integrating with FamilySearch-style ecosystems, building tree viewers, or ETL from legacy GEDCOM exports into modern services. The skill centers on generation and validation: turning narrative or partial facts into structured entities and catching schema or relationship errors before they hit production databases. It is narrower than a full genealogy product stack; it is the interchange and correctness layer. Install it when your agent must speak GEDCOM X fluently during backend and integration work, especially if compliance with community tooling matters for trust and partnerships.
- Covers GEDCOM X model knowledge for persons, relationships, events, and sources
- Generates conformant GEDCOM X payloads from agent-guided prompts
- Validates existing genealogical data against GEDCOM X expectations before merge or export
- Fits solo builders shipping family-tree SaaS, APIs, or archival tooling
Gedcomx by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add FamilySearch/gedcomx/plugin install gedcomx@gedcomxAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 388 |
|---|---|
| Last updated | April 29, 2026 |
| Repository | FamilySearch/gedcomx ↗ |
What it does
Generate and validate GEDCOM X genealogical records inside your agent workflow when building family-history apps or data pipelines.
Who is it for?
Best when you're shipping family-tree backends, migration tools, or API integrations that must honor GEDCOM X.
Skip if: General-purpose CRUD apps with no genealogy domain or teams that only need informal JSON without a standard.
When should I use this skill?
You need GEDCOM X generation, explanation, or validation while building genealogy-related features.
What you get
Your agent outputs and checks GEDCOM X–conformant genealogical records ready to import, API-post, or store.
- GEDCOM X–structured payloads
- Validation notes on genealogical inputs
Files
GEDCOM X knowledge, generation, and validation for genealogical data.
gedcomx
Source: ./tools/claude-plugin
{ "name": "gedcomx", "source": "./tools/claude-plugin", "description": "GEDCOM X knowledge, generation, and validation for genealogical data." }
Related skills
Microsoft FoundryDeploy, evaluate, and continuously improve Microsoft Foundry agents from a single agent interface.490k1.3k
Ai Research ReproductionOrchestrate trustworthy, auditable reproduction of deep learning repositories directly from their READMEs.176k511Run TrainSafely execute selected deep learning training commands with standardized evidence capture.176k511Explore RunSafely run isolated exploratory experiments with clear recording and conservative selection before committing changes.176k511Paper Context ResolverFetch precise reproduction-critical details like dataset splits, preprocessing steps, or evaluation protocols from the original academic paper when the repo README leav141k511Repo Intake And PlanScan unfamiliar AI research repositories and receive a minimal, trustworthy reproduction target before investing significant time.140k511How it compares
Use for standards-based genealogy interchange instead of ad-hoc JSON schemas with no validation story.
FAQ
Who is gedcomx for?
Developers and small teams creating genealogy SaaS, archival tools, or data bridges who need GEDCOM X literacy in Claude Code or similar agents.
When should I use gedcomx?
During Build integrations when modeling persons and events, before exporting to partners, or when validating imports from legacy GEDCOM files.
Is gedcomx safe to install?
Review the Security Audits panel on this Prism page and treat generated genealogical data as sensitive PII in your own storage policies.