Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Russian Revision Lists 1795–1858: Trace Jewish Ancestors

    1

    *One skill from the Genealogy Toolkit pack by the same author.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Russian Revision Lists 1795–1858: Trace Jewish Ancestors

    Russian Revision Lists 1795–1858: Trace Jewish Ancestors

    Example session with this skill installed

    My great-great-grandfather Leib Rosenberg appears in the 1858 revision list of a Podolia shtetl, age 42, household no. 115. How do I find him in 1850 and 1834?

    • Read your context and instructions
    • Compiled the russian revision lists

    First: which age is which

    Before using "42", read the printed header of the 1858 list. In most lists the first age column is «по последней ревизии» (at the last revision), the age in 1850; the age in 1858 sits under «нынѣ налицо» (now present). From here on every age is written with its year.

    RevisionExpected ageSearch by
    185842 (now present)household no. 115 is valid only in this list
    185034, from the bridge column (check it)name + patronymic + age + community, not no. 115
    1834about 18, from the 1850 list's own bridge columnthe same; check both the meshchane and the guild lists

    Plan

    1. Copy the 1858 entry word for word: Leib's patronymic, wife, children with ages, and the «выбыло» (departed) column: who died, who was conscripted, when.
    2. Write the bridge line: "age at the last revision — 34, so in 1850 look for age 34". If the 1858 file has two number columns («№ 9 ревизіи», «№ 10 ревизіи»), the 9th-revision number points straight to the 1850 household.
    3. In 1850, find the household by Leib's patronymic, age 34 and the children's names. Expect a different household number.
    4. From the 1850 entry take his age in 1834 and repeat. In 1834 check each estate list separately: numbering restarts from 1 in each.
    5. If Leib seems missing in 1850, look for duplicated lists and clerks' corrections («ошибкою») before calling it a zero. A "not found" is reported with the pages, spellings and lists checked.

    Next step: send me the Commons file name or a scan of the 1858 page, and we will read the header and the entry together.

    Names in this example are fictional. The agent reports nothing as found until it has seen the page.

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

    About this skill

    One skill from the Genealogy Toolkit pack by the same author. Instructions in English.

    Who this is for

    • You found an ancestor in an 1858 or 1850 revision list and want to go further back.
    • Your family came from the Pale of Settlement (Ukraine, Belarus, Lithuania, Bessarabia, Poland) and you are reading revision lists on Wikimedia Commons or FamilySearch.
    • A search failed because the surname "is not there" in an early list.

    The problem

    Revision lists are the backbone of research before 1858, but they are easy to misread. The first age column usually belongs to the previous revision, so one wrong column shifts a birth year by 16 years. Family numbers change between revisions. Before the 1804 surname law many Jews have no surname at all. An AI agent left alone will chain the wrong households and sound confident.

    What your agent does with this skill

    • Reads the printed header first and writes every age together with its year.
    • Chains generations rung by rung (1858 → 1850 → 1834 → 1816 → 1811 → 1795) through the "по последней ревизии" (at the last revision) column, never skipping a revision.
    • Matches households by name, patronymic, age and household make-up, not by family number.
    • Before the 1820s searches by patronymic, age and community, not by surname.
    • Handles double Jewish given names, merchants vs meshchane, separate lists with numbering that restarts, duplicated lists inside one file and the clerks' own corrections («ошибкою»).
    • Covers the 1874–75 Jewish military census as a bridge to 1858 and the 1882 rural registration lists.

    Why it does not make things up

    • Every age and name is quoted with the file, page and household number.
    • Every finding carries a bridge line: "age at the previous revision — NN, so in <year> look for age NN".
    • "Not found" only with stated coverage: which lists, which pages, which spellings.

    Author

    Anna Shefel, family-history researcher. Free step-by-step article on the method: https://shefelchana.github.io/genealogy-guide-ru/#/en/articles/reading-revision-lists

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Research & Analysis.

    Covers the revisions of 1795–1858 and related lists for the Jewish population of the former Russian Empire. A method skill: it does not search databases or download scans by itself, and handwriting quality limits what can be read.

    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 buying a skill.

    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 today

    Method skill only: no scripts, no network calls, no accounts needed. You bring the scans (Wikimedia Commons, FamilySearch, archive PDFs).

    Permissions

    No special permissions declared or detected

    Listedtoday

    What's inside

    Frequently Asked Questions

    By chaining households, not surnames. It moves one revision at a time through the "age at the last revision" column, matches name + patronymic + age + household make-up, and before the 1820s searches by patronymic and community, because many Jews had no fixed surname yet (the surname law dates from 1804).

    The revisions of 1795, 1811, 1816, 1834, 1850 and 1858, plus the 1874–75 Jewish military census and the 1882 rural registration lists, for the Jewish population of the former Russian Empire (Pale of Settlement: Ukraine, Belarus, Lithuania, Bessarabia, Poland). Earlier revisions (1719–1782) include few Jews.

    It tells your agent what to look for and how to read it. The scans themselves come from Wikimedia Commons, FamilySearch or archive PDFs; the full Genealogy Toolkit adds skills and scripts for finding and extracting those scans.

    Any agent that loads SKILL.md: Claude Code, the Claude app, Cursor, Codex CLI and others. No scripts and no accounts are needed.

    Yes: this is one of the 26 skills of the Genealogy Toolkit by the same author, sold separately for those who only need revision lists.

    Only a result with stated coverage: which lists and pages were read, which spellings were tried, and whether the index or the file itself was checked. Without that, the agent reports "not checked", not "not found".

    New in Research & Analysis