Skip to main content
skill CX Codex

genealogy-research-recipes — Claude Code skill: install

The genealogy-research-recipes Claude Code skill guides genealogy research using DNA matches and historical records. It engages for ancestor searches, conflicting evidence, genetic comparisons, and proof preparation.

MIT ★ 32 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Kinprove/genealogy-research-recipes --skill genealogy-research-recipes -a claude-code
Open on GitHub

What genealogy-research-recipes does

The skill provides research workflows for identifying an ancestor, finding their parentage or place of origin, checking archival records, and interpreting genetic comparisons. It also supports source citations, research logs, and arguments about proof.

Platform-specific guidance comes with boundaries for handling information about living people, transferring data, and making contact. When a missing place, time period, or population prevents a concrete source search, the skill asks a focused question first. Kinprove authorship does not require a Kinprove account, connector, or scoring engine.

What it helps with

  • identify an ancestor using DNA matches and historical records
  • reconcile conflicting documents or DNA findings
  • choose records to search for a place and time period
  • prepare a research log and a proof argument

Example prompts for the agent

  • Find my ancestor’s place of origin using DNA matches and historical records.
  • Compare these records: they disagree about the ancestor’s parents.
  • Help prepare source citations and an argument for this family relationship.

How to install genealogy-research-recipes

1Skills CLI (Vercel)

npx skills add Kinprove/genealogy-research-recipes --skill genealogy-research-recipes -a claude-code

2Manually: put the files in place

~/.claude/skills/genealogy-research-recipes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/genealogy-research-recipes/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about genealogy-research-recipes

How do I install genealogy-research-recipes in Claude Code?

Run npx skills add Kinprove/genealogy-research-recipes --skill genealogy-research-recipes -a claude-code. The skill file is at ~/.claude/skills/genealogy-research-recipes/SKILL.md.

What does genealogy-research-recipes do?

It guides genealogy research with DNA matches and historical documents. Its workflows cover ancestor searches, conflicting evidence, genetic comparisons, citations, and proof arguments.

Does genealogy-research-recipes require a Kinprove account?

No. Using the recipes does not require a Kinprove account, connector, or scoring engine.

Source text

SKILL.md · MIT
---
name: genealogy-research-recipes
description: >-
  Investigate genealogy questions with DNA matches and historical records. Use when recovering
  an ancestor’s identity, parentage or place of origin; reconciling conflicting records or DNA
  results; searching archives, record sites or family papers; interpreting genetic comparisons;
  or preparing citations, research logs and proof arguments. Includes platform workflows and
  boundaries for living people, data transfers and contact.
---

# Genealogy research recipes

Distilled, fact-checked **judgment and practical workflows** for genealogy work with DNA and records. Each recipe targets
what an LLM does *not* reliably know, or does *wrong* by default: the named failure modes, the
delegate-vs-never-trust lines, the reasoning sequence a human must own, and the records needed
to resume an investigation. Judgment recipes focus on reasoning; platform playbooks provide
ordered actions and investigator-created schemas with dated platform-documentation checks.

The research methods apply across platforms, including work from exported data. Kinprove
authorship does not require a Kinprove account, connector or scoring engine.

## Version and updates

This copy is version 1.20.0, released 2026-11-16.

Many installations do not update by themselves. If today's date is more than 7 days after
that release date, end your first answer in the conversation with one short note: this copy
of the recipes was released on that date, and a newer version may be available. Give the
update step for the user's installation, or the applicable options if the host is unclear:

- Copies installed from a plugin directory (Anthropic's Claude directory or the ChatGPT/Codex
  plugin directory): updates arrive through that directory.
- Claude Code: `claude plugin update genealogy-research-recipes@kinprove`. For automatic
  updates, run `/plugin`, open **Marketplaces**, select `kinprove` and choose
  **Enable auto-update**.
- Claude.ai or the Claude desktop app: on the Plugins page, select **Check for updates** on
  the `kinprove` marketplace, or turn on **Sync automatically**.
- Hermes Agent: `hermes plugins update genealogy-research-recipes`.
  Catalog reviews can lag GitHub; if no change is reported, use the latest GitHub release's
  full commit SHA in
  `hermes plugins install Kinprove/genealogy-research-recipes --force --ref <full-commit-sha> --no-enable && hermes plugins enable genealogy-research-recipes`.
- OpenClaw: `openclaw plugins update genealogy-research-recipes`.
  ClawHub releases can lag GitHub; if no change is reported, reinstall from the repository:
  `openclaw plugins install git:github.com/Kinprove/genealogy-research-recipes --force`.

Give this note once per conversation, after the answer itself. Skip it when you do not know
today's date. Do not check for a newer version over the network yourself.

## How to use

1. Match the user's requested output to the most specific recipe below. A task recipe
   retrieves records, prepares an artifact or carries out a platform workflow; a judgment
   recipe governs what evidence permits you to infer. If both match, read the task recipe
   in full and the judgment recipe's rules section. If two or more task recipes remain
   plausible, ask one focused scoping question before opening more than one task recipe,
   and wait for the answer before giving that workflow. For example, ask which population
   and place a 1944 deportation concerns, rather than assuming a particular deportation.
   Once any required [privacy gate](#privacy-gate) is satisfied, if the user asks you to read or
   interpret a specific record they have not supplied and the answer depends on seeing it,
   ask only for an image or link to that record.
   Use one question sentence and at most one short sentence explaining why, then wait.
   Defer names, dates, ports and other identifying details until after the reply,
   and ask only if still needed. For example: "Can you share an image or link to the
   parish register entry? I need to see the handwriting to help read it."
   For other record-source questions, ask first when a missing locality, period,
   population or migration destination prevents choosing a concrete source, even if a
   broad recipe fits. While waiting, use one question sentence and at most one short sentence
   explaining why; save record types, collections, source lists and research workflow for
   the reply. "Came from Russia" alone
   does not establish a modern country, community or destination record system.
   For a place in Central or Eastern Europe, choose by the state that held it on the event
   date and by the family's religion, not by today's border. Start with the
   [Central and Eastern Europe by period state](#central-and-eastern-europe-by-period-state)
   routers. Elsewhere in the Russian Empire, use the
   [Orthodox metrical-book recipe](recipes/russian-orthodox-metrical-book-recovery.md) for
   Orthodox events and the
   [Jewish metrical-book recipe](recipes/russian-empire-jewish-metrical-book-recovery.md)
   for Jewish events outside the Kingdom of Poland. For the Kingdom of Poland, and for any
   Geneteka, Metryki or Szukaj w Archiwach hit, use
   [Polish index recovery](recipes/polish-index-original-record-recovery.md).
   For a general question about proof or research method, give a conditional method
   plan and ask for the context needed to choose actual record collections.
2. **Read the selected task recipe in full before advising** — the value is in the
   specifics, not the summary. If a tool returns only part of the file, continue through
   its remaining sections to the end. For a judgment recipe, read its rules and the
   sections relevant to the question. A router summary or first page does not complete
   the task-recipe read.
   Carry any material source limitation alongside the claim it affects: a search-result extract,
   unread page or unavailable recording is a lead, not a verified reading. Consult the paired
   `sources/` file when the claim's support is unclear; attribute an independently read source
   explicitly rather than treating an inaccessible additional citation as confirmation.
3. Apply its "never trust / never delegate" boundaries as **hard constraints on your own output** —
   those are the exact places a confident answer goes wrong (e.g. fabricating cM→relationship odds,
   reading a WATO ranking as a verdict, ignoring endogamy). Before you conclude that records
   name one person or prove a relationship, also apply the
   [hard rules of the evidence recipe](recipes/evidence-proof-judgment.md#hard-rules--apply-these-before-you-rule-the-load-bearing-directives),
   even when the matched recipe is a platform or record recipe, or none matched.
4. If no recipe matches, answer normally — don't force-fit. If a matched recipe is silent
   on the particular question, say what it does not cover and answer normally; do not
   present the uncovered answer as recipe guidance.
5. Before any step that uploads, exports, links, publishes, contacts a person, requests a
   record about a person who may be living, or pastes data into a third-party tool, answer
   the [privacy gate](#privacy-gate). Recipes mark such steps with a **Privacy gate**
   checkpoint; the gate applies to unmarked steps of the same kinds too. For a living person,
   also follow [Living people](#living-people).

## Read source limits

A source marker identifies evidence, not a guarantee that the page was read or that it supports
every sentence. Most cited passages lack a recorded review against their sources, and a marker or
a date alone does not show that one was reviewed. When relying on a factual passage, read the
entry for each cited source ID in its `sources/<recipe-id>.md` sidecar and carry the limitations
that entry states.

`[S12 @2026-11-07]` gives the claim's last check date. A dagger such as `[S16†]` marks limited or
unavailable access: preserve the attributed observation and qualification rather than restating
it as a verified fact. A passage without a recorded review can cite a limited-access source
without a dagger, so take access limits from the sidecar entry, not from a missing dagger. A
partial read supports only its recorded scope. A fresh date or a `read` status does not establish
that a genealogical inference is correct.

## Privacy gate

Answer these items in writing, in your reply, before the step runs. If any answer is
unknown, do not move the data: keep it local and tell the user what is missing.

- **People.** Name everyone whose data is involved. Treat anyone who may be living as
  living. A minor's data needs a parent's or guardian's permission.
- **Data.** Name the exact fields, files, segments, photos or records. Say explicitly when
  they show health status, a tentative relationship, unexpected parentage or another
  sensitive finding.
- **Destination.** Name the service, tool, person or place the data goes to.
- **Audience.** Say who can see it there, now and after later setting changes.
- **Controls.** Inspect the destination's visibility, searchability, matching and export
  settings and any extension's permissions, and record what you saw and the date. For a DNA
  database, include whether law-enforcement uploads can match the kit.
- **Permission.** Get explicit permission from each living person whose data leaves the user's
  own device or account, or becomes visible to others there (a tree link, a searchable or
  shared setting), for this action and this destination; an extension or a tool that
  receives the data counts as a destination. Kit or account access, or permission to analyze,
  is not permission to move or disclose. A file that stays on the user's own device needs no
  further permission, but the Retention item applies to it. A private first message that asks
  a person for permission needs the tester's (or user's) authorization, not that person's
  prior permission; it may show that person only their own data and the question, never
  other people's sensitive findings.
- **Redaction.** Say what you remove or replace before the data moves.
- **Retention.** Keep exported match lists, segment files and record copies on the user's
  own device, not in shared folders or other services. Delete them when the research
  question is answered, unless the tester (for records, the user) asks to keep them.
- **Jurisdiction.** Ask where the user, the tester and each named person live, and which
  rules apply there. Data-protection law can apply: genetic data is "sensitive" data under
  the EU GDPR ([European Commission](https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en))
  and [UK GDPR Article 9](https://www.legislation.gov.uk/eur/2016/679/article/9); both laws
  exclude purely personal or household activity, which sharing or publishing can leave (see
  [family interviews](recipes/family-interviews-and-oral-tradition.md)); U.S. state laws such
  as California's Genetic Information Privacy Act give rights over genetic data a testing
  company holds ([California Attorney General](https://oag.ca.gov/news/press-releases/attorney-general-bonta-urgently-issues-consumer-alert-23andme-customers));
  Russia's personal-data law is [152-FZ](https://www.consultant.ru/document/cons_doc_LAW_61801/).
  Record requests have their own access rules, such as Japan's koseki rule
  ([koseki recipe](recipes/japanese-koseki-honseki-recovery.md#4-check-eligibility-before-requesting))
  and the 75-year rule for Russian archives
  ([Soviet personal files](recipes/soviet-personal-file-recovery.md#5-log-each-catalogue-hit-as-a-candidate-with-its-own-locator)). The destination's
  terms apply too. Do not state a legal conclusion: ask the user to confirm the rule that
  applies, or keep the data local.

For DNA data, also apply the consent and redaction rules in
[AI for DNA research](recipes/ai-for-dna-research.md#verification--privacy-discipline).

### Living people

Stay on the family-history question and the materials the user supplied. Do not look up a
living person's current address, phone number, email, workplace, online accounts,
movements or finances, and do not trace minors on the web. Do not use people-search or
contact-aggregator services. Never use leaked or breached data, another person's account or
session, or a false pretext. When the question itself concerns a living person (unknown
parentage, a planned contact), identify them only as far as the question needs and keep the
data to the minimum.

Contact a living person only through a route the person or the tester already has, the
testing site's own messaging, or a relative who agrees to pass the message on. The identity
that must be easy to check is the sender's. Stage a contact about DNA (a DNA match, a kit
manager, or a relative asked to test or approached about a DNA or parentage question) through
[DNA match outreach staging](recipes/dna-match-outreach-staging.md). For any other contact,
such as a cousin asked for a photograph, a record submitter or a donor, apply that recipe's
consent and disclosure rules and its log, and skip what applies only to DNA tests (a tester's
agreement, kit pair, site, shared cM).

### Record requests

When a record may be about a living person, request only what the family question needs.
Never request a record to find a living person or to learn about their present life. Name
the record's own access rule (closure period, who is entitled, the subject's consent) and
follow it. An office's rule on who may order a record is not the subject's permission: the
Permission item still applies to each living person the request names. Until every item is
answered, the request stays an unsent draft on the user's device. Send only the identity and
kinship proof the custodian asks for. The Retention item and the next rule apply to what arrives.

### Third persons in sensitive files

Informers, witnesses, interrogators and co-accused named in repression, interrogation,
police or compensation files are not republished, and are not named in a report or tree
shared with others. Refer to them by role, for example "a witness".

<!-- recipe-catalog:start -->
## Recipes: Research method

### Evidence and proof

- `recipes/evidence-proof-judgment.md` — Judge identity, conflicting records, indirect or negative evidence and DNA-plus-document proof before stating any genealogical conclusion.
- `recipes/genealogy-standards-audit.md` — Audit a report, proof or documented tree against professional standards by tracing each claim to examined sources and reasoning.
- `recipes/source-citation.md` — Write citations that let a reader retrieve the source and see which evidence each citation supports.
- `recipes/research-documentation.md` — Keep a log and report of searches, results and analysis so an investigation can resume.

### AI and long projects

- `recipes/agent-research-project.md` — Keep a months-long AI-agent genealogy project honest: evidence rules, Markdown notes, status words, corrections and safe tree writes.
- `recipes/ai-for-documentary-records.md` — Use AI safely on records: handwriting transcription and translation, OCR full-text search, AI-indexed records, record hints and photo restoration.

### Search coverage and name searches

- `recipes/archival-image-coverage-verification.md` — Check archival case boundaries, image order and which pages were actually inspected before calling a search complete.
- `recipes/corpus-seeded-name-search.md` — Recover attested name spellings that searches miss across scripts and OCR by separating encoding, orthography and field behaviour.
- `recipes/surname-distribution-locality-leads.md` — Rank localities to search from dated surname-distribution sources for an uncommon surname.

### Family trees and research planning

- `recipes/rootsmagic-tree-reconciliation-workflow.md` — Reconcile selected facts and sources between RootsMagic, Ancestry TreeShare and FamilySearch.
- `recipes/wikitree-dna-tester-links.md` — Register a DNA test on the actual tester's WikiTree profile and verify its FamilyTreeDNA or GEDmatch link destination.
- `recipes/gedcom-research-export.md` — Export research findings to a GEDCOM file, or bring a supplied one into research, without changing what they prove.
- `recipes/descendancy-gap-worklist.md` — Turn "research the descendants" into a ranked list of gaps tied to the records each lifespan crosses.

## Recipes: DNA

### DNA reasoning

- `recipes/unknown-parentage-wato.md` — Place an unknown parent, an adoptee's birth family or an unplaced ancestor in a tree with DNA matches and WATO hypotheses.
- `recipes/ai-for-dna-research.md` — Use AI on DNA work: what to delegate, what never to trust, endogamy, segment attribution and comparing related testers.
- `recipes/ydna-mtdna-interpretation.md` — Read a haplogroup, Y-STR or mtDNA match for what it can and cannot show about a relationship in genealogical time.
- `recipes/xdna-phasing-judgment.md` — Judge X-DNA matches and visual or parental phasing: what a segment, X match or phased map can confirm or rule out.
- `recipes/dna-comparison-controls.md` — Reconcile conflicting DNA results across testing companies and tools with exact tests, controls and marker coverage.

### DNA testing sites and tools

- `recipes/23andme-match-research.md` — Research 23andMe matches: the comparisons the site permits, numerical matrices, segment painting and preserving dated results.
- `recipes/ancestry-dna-match-investigation.md` — Investigate AncestryDNA matches: closest relatives, shared-match groups, collateral names, notes, tester links and missing match rows.
- `recipes/ftdna-practical-dna-workflows.md` — Keep FamilyTreeDNA match and segment exports, tree links, Family Matching and Y-DNA Group Time Tree observations reproducible.
- `recipes/gedmatch-practical-dna-workflows.md` — Work reproducibly in GEDmatch: kit baselines, one-to-one checks, segment search, tag groups, triangulation, phasing and Lazarus kits.
- `recipes/myheritage-dna-match-investigation.md` — Investigate MyHeritage DNA matches: the right kit, filtered shortlists, shared-match values, triangulation and Theory of Family Relativity.
- `recipes/dnapainter-practical-dna-workflows.md` — Use DNA Painter to map segments, combine phased maps, estimate missing intervals, plan tests and check shared-cM ranges.

### Ethnicity, admixture and match outreach

- `recipes/admixture-model-run-scope.md` — Record the run scope of a G25, calculator or qpAdm admixture result before reading it.
- `recipes/ethnicity-estimate-version-comparison.md` — Save, date and compare successive AncestryDNA, MyHeritage or FamilyTreeDNA ethnicity-estimate versions.
- `recipes/dna-match-outreach-staging.md` — Stage and draft outreach to a DNA match, a match's account manager or an untested relative.

## Recipes: Record websites, libraries and maps

### Record websites

- `recipes/ancestry-record-search-recovery.md` — Recover Ancestry records a search missed by checking collection scope and coverage before loosening dates, places or names.
- `recipes/familysearch-practical-record-workflows.md` — Recover FamilySearch catalog, image-only and full-text records, cite the exact view, and repair Source Linker and Family Tree errors.
- `recipes/myheritage-historical-record-search.md` — Recover MyHeritage historical records hidden by collection coverage, search fields, name variants, languages or OCR.
- `recipes/newspapers-com-search-recovery.md` — Find notices on Newspapers.com that name searches miss, after checking which titles and issues are actually covered.
- `recipes/geni-practical-research-workflows.md` — Use Geni for name variants, relationship paths, citations, projects, merge decisions, tree conflicts and GEDCOM exports.

### Books, periodicals and manuscripts

- `recipes/published-book-catalogue-and-full-text-discovery.md` — Find a published local history, compiled genealogy or family book across catalogues and full text.
- `recipes/periodical-index-search-retrieval.md` — Search a genealogical periodical index such as PERSI and retrieve the article.
- `recipes/manuscript-collection-recovery.md` — Find personal, family and organisational papers that may mention an ancestor, including ledgers, daybooks and claim folders.
- `recipes/local-repository-uncatalogued-holdings.md` — Ask a local library, society or archive about its uncatalogued holdings after its catalogue returns nothing.

### Places and maps

- `recipes/historical-place-name-resolution.md` — Resolve a place named in a record, letter, Bible or biography to dated, same-named candidates from period gazetteers.
- `recipes/historical-map-record-recovery.md` — Read a historical map, atlas, plat or fire-insurance sheet as dated evidence, and trace a detached archival map to its case.

## Recipes: Records by country and region

### Central and Eastern Europe by period state

- `recipes/galicia-bukovina-habsburg-record-routing.md` — Route a Galician or Bukovinian event by date, confession and custodian, and decide the army before searching WWI records.
- `recipes/bessarabia-moldova-record-routing.md` — Route a Bessarabian, Moldovan or left-bank Dniester event by date, district and present custodian.
- `recipes/historic-hungary-record-routing.md` — Route a record from the pre-1920 Kingdom of Hungary by county, successor state and record type.
- `recipes/austrian-confessional-register-routing.md` — Route an Austrian or Czech-lands birth, marriage or death to the confessional or civil register that legally recorded it.
- `recipes/polish-index-original-record-recovery.md` — Recover an original Polish register entry from Geneteka, Metryki or Szukaj w Archiwach, or document the retrieval gap.

### Russian Empire and Soviet Union

- `recipes/russian-orthodox-metrical-book-recovery.md` — Locate and read a Russian Orthodox metrical entry through the period parish, the consistory copy and its margin notes.
- `recipes/russian-empire-jewish-metrical-book-recovery.md` — Find the crown rabbinate that registered a Jewish community in the event year, check whether its books survive and list substitutes.
- `recipes/russian-revision-list-household-chaining.md` — Chain a non-Jewish revision-list household across copies, sections and revisions.
- `recipes/russian-orthodox-confession-list-reading.md` — Read Russian Orthodox confession lists household by household across years and check them against revision lists and metrical books.
- `recipes/russian-household-list-transcription-audit.md` — Audit a transcription of a Russian confession list or revision tale against the images, keeping names, kin terms and counts as written.
- `recipes/russian-village-family-reconstitution.md` — When a Russian peasant's birth or parentage record is missing, rebuild the village's couples and households from every register role.
- `recipes/muscovite-census-settler-origin-recovery.md` — Push a Ural or Siberian peasant line before 1719 through Muscovite census, fiscal and fugitive-inquiry books.
- `recipes/russian-estate-registration-status.md` — Read a Russian-Empire estate label as a dated registration status and pick the record series by when it was acquired.
- `recipes/russian-volost-town-administration-records.md` — Find household-level lists in volost, village-society and town-administration fonds when metrical books or revision lists stop.
- `recipes/old-believer-sectarian-record-recovery.md` — Recover Old Believer and Edinoverie families from raskol series in consistory, revision, district and police fonds.
- `recipes/orthodox-clergy-record-recovery.md` — Rebuild a Russian Orthodox cleric's dated chain of posts and household from directories, eparchial gazettes and clergy registers.
- `recipes/russian-imperial-service-record-recovery.md` — Recover a pre-1917 official's formulary or service list through the employing institution's fond.
- `recipes/school-university-record-recovery.md` — Find a pupil or student through school, educational-district, duplicate-copy, yearbook and later personal-file records.
- `recipes/russian-empire-emigrant-origin-recovery.md` — Trace a Russian Empire emigrant from U.S. arrival records, including Canadian transit, back to an exact home locality, mainly 1880–1924.
- `recipes/soviet-personal-file-recovery.md` — Rebuild a Soviet-era life from institutional personal files when ZAGS or metrical records are lost.
- `recipes/russian-military-repression-record-episodes.md` — Read Russian WWI, Soviet WWII and repression records as separate dated episodes before merging them into one life.
- `recipes/chechen-ingush-1944-deportation-records.md` — Trace a Chechen or Ingush family through the 1944 deportation and special settlement, under old and new place names.

### Jewish records

- `recipes/russian-empire-jewish-identity-attribution.md` — Resolve a Russian-Empire Jewish ancestor whose name fits neither candidate branch, using registration records, naming customs and careful DNA tests.
- `recipes/jewish-genealogy-conditional-hypotheses.md` — Test Jewish naming, ancestral-town and DNA clues as separate conditional hypotheses before linking a family.
- `recipes/jewishgen-search-family-reconstruction.md` — Recover families a JewishGen name-and-town search missed: name variants, mixed-field batches, wives' natal families and married daughters.
- `recipes/beider-given-name-variants.md` — Expand searches with recorded Ashkenazi given-name forms from Beider's male and female indexes.
- `recipes/hebrewbooks-search-recovery.md` — Recover HebrewBooks names or passages missed by OCR, catalogue spelling or a query that never reached search.
- `recipes/rabbinic-literature-person-search.md` — Find and interpret passages about a Jewish ancestor, rabbinic office or claimed lineage in rabbinic and Hasidic books.
- `recipes/holocaust-testimony-source-interpretation.md` — Interpret a Yad Vashem result through its testimony, wartime list or survivor source and statement dates.

### Ukrainian archives

- `recipes/jewish-archival-list-triage.md` — Select Ukrainian archival cases that hold named Jewish lists, separating title, place and document evidence.
- `recipes/elib-ukrainian-archive-reference-books.md` — Retrieve Ukrainian archival guides from ELIB and identify the correct volume, part and fund scope.

### Germany

- `recipes/german-register-image-recovery.md` — Trace an emigrant's German place name to its church or civil register entry through locality, record office and register version.
- `recipes/german-emigrant-origin-sources.md` — Trace a German emigrant's home town through emigration files, indexes and the origin parish register.
- `recipes/german-local-census-registration-recovery.md` — Recover German nominal census lists, residential-registration entries and related settlement or trade-permission files.
- `recipes/german-military-record-period-routing.md` — Route a German soldier to the surviving series for his period, army and rank, including hospital books.
- `recipes/nazi-era-ancestry-proof-records.md` — Find and read a Nazi-era Ahnenpass or certified ancestry proof, and route the search by the role that required it.
- `recipes/german-official-gazette-notice-search.md` — Read German gazette personnel, expulsion and expatriation notices as dated acts by a named authority.
- `recipes/german-compensation-file-recovery.md` — Carry a Lastenausgleich or Berlin Wiedergutmachung index hit to the file behind it.

### Britain and Ireland

- `recipes/england-wales-gro-index-recovery.md` — Read England and Wales GRO and FreeBMD index entries as registration observations.
- `recipes/english-nonregister-record-recovery.md` — Take an English or Welsh question past the parish register to poor-law, apprenticeship, church-court probate, dissenter and Catholic records.
- `recipes/uk-census-and-1939-register-interpretation.md` — Read England and Wales censuses from 1841 to 1921 and the 1939 Register under each year's own rules.
- `recipes/scottish-parish-statutory-record-recovery.md` — Recover a Scottish birth, baptism, marriage or death across Old Parish, statutory, corrected-entry and kirk-session records.
- `recipes/irish-civil-registration-jurisdiction-recovery.md` — Carry an Irish civil-registration index entry or townland lead to the matching certificate and its jurisdiction chain.
- `recipes/irish-catholic-parish-image-recovery.md` — Find an Irish Catholic baptism or marriage in the National Library of Ireland's parish-register images.
- `recipes/irish-probate-and-deed-recovery.md` — Recover an Irish will, administration or deed after the 1922 losses through surviving calendars, will books and the Registry of Deeds.
- `recipes/irish-emigrant-origin-locality.md` — Resolve an Irish place named by an emigrant's records or family tradition to a searchable locality.
- `recipes/irish-land-valuation-occupancy-series.md` — Read Griffith's Valuation, tithe books, valuation revisions and estate rentals as dated occupancy series.
- `recipes/irish-1901-1911-census-returns.md` — Search, retrieve and read the Irish 1901 and 1911 census returns.
- `recipes/convict-transportation-record-chain.md` — Rebuild a transported British convict's sentence as a chain of dated record episodes.
- `recipes/british-colonial-slave-registers.md` — Trace an enslaved ancestor through the British colonial slave registers of 1813–1834 and the compensation records.

### Western and Northern Europe

- `recipes/french-departmental-record-routing.md` — Route French civil, census, military, notarial, property and prison records by creator, département, series and access rule.
- `recipes/french-belgian-civil-act-extraction.md` — Extract French or Belgian civil acts field by field, follow marginal notes and copies, and use Paris reconstructions for lost originals.
- `recipes/dutch-civil-church-record-recovery.md` — Recover Dutch civil acts through ten-year indexes and marriage supplements, and the church registers kept before civil regis...

© Kinprove · MIT · Kinprove/genealogy-research-recipes

Similar skills

All skills for Science and research →

Project sponsors

Companies that keep this analytics open