Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Genealogy Research: Find Your Ancestors

    1

    Turns your agent into a careful genealogist: finds where records are kept, searches every name variant and checks each find.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Genealogy Research: Find Your Ancestors

    Genealogy Research: Find Your Ancestors

    Example session with this skill installed

    My great-grandmother Anna Kolodina was born around 1895 in Puchezh, Kostroma province, Russia. Where are her birth records likely kept, and what should I search first? Please give me concrete next steps.

    • Read your context and instructions
    • Compiled the genealogy research

    I haven't found a record of Anna yet. I only worked out where the records should be and prepared search links.

    Where her birth record should be

    Then: Puchezh was in Yuryevets uezd (district), Kostroma province, in the 1890s. In the Orthodox Church, a birth was recorded as a baptism in the parish register (метрическая книга) of her family's church.

    • Now: Puchezh is in Ivanovo Oblast, not Kostroma Oblast. That means records may be in either of two archives:
      1.

    State Archive of Kostroma Oblast (ГАКО): the Kostroma Consistory fond holds the consistory's duplicate copies of parish registers for the whole province, including Yuryevets uezd. This is the main place to look for 1895. (From memory I think the fond is ф. 130. Check that in the archive's guide.)
    2.

    State Archive of Ivanovo Oblast (ГАИО): may hold the parish's own copies, because the district moved to Ivanovo after 1918.

    What to do, in order

    Ask your family about "Kolodina". Was it her maiden name or her married name? Was she born in the town itself or in a nearby village? Do you know her father's name (her patronymic)? A baptism register is arranged by parish and date, not by surname, so the parish matters most.
    2. Search the FamilySearch indexes, which is free and needs an account. Try every spelling:

    Look for scanned registers that have no index. In the FamilySearch Catalog, search the place "Russia, Kostroma" and look for "Church records" for Yuryevets uezd or Puchezh. Then try Yandex Archive, which has full-text search of scanned parish registers for some regions. Search "Колодин Пучеж". Without an index you'll need to read the baptisms for 1894–1896 page by page.
    4.

    Find which churches Puchezh had in 1895 on sobory.ru and in the 1890s–1900s directories of Kostroma diocese. Also ask on the Kostroma/Yuryevets section of forum.vgd.ru. Local researchers there often know which fond and inventory hold Puchezh's registers.
    5.

    Write to the archives if steps 2–4 turn up nothing. Ask ГАКО for a search of the 1894–1896 parish registers for Puchezh. If you can, give the parish, her father's name and her religion. Ask ГАИО the same question. The archives charge for searches. I can draft the letter in Russian for you to check and send.

    How to read what you find

    • Dates in the register are in the Julian (old-style) calendar. For 1895, add 12 days to get the modern date.
    • "Born around 1895" probably comes from an age stated later in life. Ages like that are often a few years off, so search 1892–1898.
    • An entry for "Анна" whose father is a Колодин is only a lead until you match two more facts, such as the parents' names, her later marriage or the village.

    I didn't search any database for her yet, and the fond number (ф. 130) is from memory, not checked. The biggest risk: if Kolodina was her married name, a birth-record search under that surname will never find her.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Family history research is where AI agents go wrong most easily: they guess archive names, search one spelling of a surname, and happily "confirm" a namesake as your great-grandfather. This skill turns your agent into a careful genealogist.

    It works on top of genealogy-mcp, a free, open-source MCP server (MIT, on PyPI and in the official MCP Registry) with 114 archives and databases in 55 countries and 24 research tools. The skill tells the agent which tool to use when, in what order, and how to report, so every session goes from a vague family story to concrete records and next steps.

    What your agent will do

    • Find where the records are kept today. Parish registers, censuses, revision and confession lists, military and repression files, civil registration. Borders moved (Russian Empire, Poland, Galicia, Bukovina, the Baltics, the Caucasus), so records are often in another country's archive. The agent checks that instead of guessing.
    • Search every form of a name. Pre-1918 spelling, female surname forms, transliterations (German, Polish, French, Spanish…), Daitch–Mokotoff codes. It runs live searches in open databases and gives you ready links for FamilySearch, Find a Grave, Geneteka, Arolsen and others.
    • Read old records correctly. Julian → Gregorian dates, dates given as church feasts, Church Slavonic numerals, ages → birth years, old terms.
    • Check every find before it enters your tree. Fact-by-fact comparison with a verdict (confirmed / probable / not your person). Common names need an extra fact before anything is accepted, so no invented relatives.
    • Remember the research. A project kept between sessions, in a folder or right inside your own GEDCOM file, with a log of every search, including the ones that found nothing.
    • Audit your tree before you upload it to MyHeritage or Ancestry: impossible dates, parents who are too young, duplicates, people without sources.
    • Draft requests to archives and registry offices for you to send.

    Who it is for

    Anyone researching ancestors from Russia and the former USSR, Poland, Ukraine, Belarus, the Baltics, Germany and the rest of Europe, the British Isles, the Americas or Australia, especially when the records are in another language or alphabet.

    What's inside

    • SKILL.md: the research workflow, the rules and the report format.
    • references/tools.md: all 24 tools with their arguments.
    • references/examples.md: five worked sessions.
    • config/: ready MCP configs for Claude Code, Claude Desktop, Cursor and VS Code.

    Tested end to end in Claude Code with the current release on Python 3.10–3.13.

    Requires genealogy-mcp server installation. Cannot bypass paywalls or create accounts on sites like FamilySearch. Transcription accuracy depends on image quality.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Genealogy MCP
    uv (Python tool runner)
    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access

    File Scopes

    genealogy-research/**
    *.ged

    Network: only two server tools go online, and only when called: search_online sends the searched names to the one open database chosen (Internet Archive, Chronicling America, WikiTree, Open Archives or Open List), and place_history sends a place name to Wikidata. Files: the research project is read and written only at the folder or .ged path the user gives (a backup copy is kept before every change). Terminal: only for the one-time install command (uvx). No credentials or environment secrets are used.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Every candidate record is compared fact by fact with what you already know (names, patronymic, parents, year, place), with tolerance for name variants, old-style dates and rounded ages. The agent only accepts a record as your ancestor when two or more independent facts besides the name agree, and for very common names it asks for one more specific fact such as the village, the mother's maiden name or a sibling. Anything weaker is kept as a lead, never written into your tree as fact.

    It is designed for the Model Context Protocol (MCP) and integrates seamlessly with Claude Desktop, Claude Code, Cursor, and Windsurf, requiring the `genealogy-mcp` server to function.

    No. The skill works with free and open sources and builds ready search links for sites such as FamilySearch (free account) or Ancestry; if a site needs a login or a subscription, you open the link and sign in yourself. The genealogy-mcp server it uses is free and open source.

    Yes, the skill includes a verification engine that audits existing GEDCOM files for logical inconsistencies, such as impossible birth dates or missing archival citations, ensuring your tree meets professional standards.

    One command in Claude Code: `claude mcp add genealogy -- uvx genealogy-mcp@latest` (it needs uv, which installs Python by itself). For Claude Desktop, Cursor and VS Code the skill includes ready config snippets. If the server is not connected, the agent stops and walks you through the setup instead of guessing.

    New in Research & Analysis