check-warnings

Detect contradictions and implausible patterns in genealogical person data and retrieve FamilySearch quality scores.

3|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill check-warnings-pioneeraiacademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-warnings
Source: https://github.com/PioneerAIAcademy/cowork-genealogy/tree/main/packages/engine/plugin/skills/check-warnings
Command: npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill check-warnings-pioneeraiacademy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Genealogy research accumulates data errors silently: death dates before births, events recorded after death, impossibly young parents, or records from two same-name individuals merged into one profile. This Skill runs deterministic offline checks against your local tree data and fetches FamilySearch's live quality score, so you can catch integrity problems before they corrupt your conclusions. ## Core Features & Use Cases - Offline contradiction and plausibility checks: Runs the person_warnings tool against tree.gedcomx.json to flag physical impossibilities (event after death, burial before death, lifespan over 120 years) and implausible patterns (child born to a 13-year-old father, 18+ children) with severity levels and issue tags. - FamilySearch quality scoring: For persons with FamilySearch IDs, calls person_quality to retrieve the live profile's completeness, verifiability, consistency, and coherence scores with ready-made issue sentences. - Identity-confusion interpretation: Clusters multiple contradictions to distinguish a single wrong fact from two individuals merged into one profile, and recommends concrete verification steps. - Use Case: Before writing a proof summary for an ancestor, run a warnings check on the subject and every cited person to confirm no timeline impossibilities undermine the conclusion. ## Quick Start Check Patrick Flynn in my family tree for any genealogical warnings or data inconsistencies.

Frequently Asked Questions about check-warnings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check a family tree for data errors and contradictions?▼

Run a warnings check on the person by name or ID. The person_warnings tool scans the local GedcomX tree for impossibilities like death before birth, events after death, and implausible ages, returning each issue with a severity and explanation.

What is the difference between a genealogical warning and a source conflict?▼

A warning is a contradiction or implausible pattern within one person's own data, detectable from the assembled profile alone. A conflict is two or more sources disagreeing about the same fact, which requires comparing sources and is handled by conflict-resolution instead.

Can I get a FamilySearch quality score for a person in my tree?▼

Yes, when the person's ID is a FamilySearch ID (format like KWCJ-RN4), the person_quality tool retrieves the live profile's overall score and issues across completeness, verifiability, consistency, and coherence. It requires being logged in to FamilySearch.

Why does an event-after-death warning not always mean two people were merged?▼

An event-after-death warning has three legitimate causes: identity confusion, a wrong death date, or a posthumous mention such as an obituary, probate file, or city directory that merely references the deceased. The late-dated source must be inspected before choosing a corrective action.

What are the limitations of automated genealogy warning checks?▼

The tool does not check geographic impossibilities, future dates, child spacing under nine months, or births before parents' marriage. It also cannot judge source reliability; warnings are informational signals for the researcher to verify against original records.