What problem does it solve? Genealogical research requires executing planned searches against FamilySearch historical records in a disciplined, auditable way. This Skill bridges research planning and record analysis by running the correct MCP search tool for each record type, triaging results with match scoring, and logging every search — including nil results — to satisfy the Genealogical Proof Standard's reasonably exhaustive research requirement. ## Core Features & Use Cases - Plan-driven search execution: Reads the next planned item from the active research plan in research.json, constructs a broad-to-narrow query with surname, place, and date anchors, and calls record_search with projectPath and subjectId for automatic staging and ranking. - Match triage and ranking: Uses rank_search_matches to score every staged candidate against the tree subject with FamilySearch's matcher, re-ordering by real match quality rather than unreliable search rank, with attachment checks and needs-review flagging for namesakes. - GPS-compliant logging: Logs every search — positive and negative — with staged results sidecars, and hands promising records off to record-extraction while honestly reporting un-indexed or browse-only collections. - Use Case: A researcher asks to "find Patrick Flynn in the 1850 census". The Skill routes to record_search with residence year and place anchors, ranks the staged candidates against the tree person, logs the search with its results handle, and passes the top confirmed match to record-extraction. ## Quick Start Ask the assistant to search FamilySearch for a specific person in a specific record type, such as "search for Anna Halsteinsdatter in Norway marriage records".
