Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Pogrom Records 1918–1922: Find Jewish Victims & Survivors

    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
    Pogrom Records 1918–1922: Find Jewish Victims & Survivors

    Pogrom Records 1918–1922: Find Jewish Victims & Survivors

    Example session with this skill installed

    My great-grandmother's brother Moishe Kravets disappeared around 1919 in a shtetl near Fastov. Can you check the pogrom databases?

    • Read your context and instructions
    • Compiled the pogrom records 1918

    Identification set

    FieldValues to search
    SurnameKravets, Kravetz, Kravec, Krawiec, wildcard Krav*; Кравец, Кравц
    Given nameMoishe, Moshe, Movsha, Mosko; Mikhail as a Russian form
    Placethe shtetl, the neighbouring shtetls, Fastov, Kyiv (refugees died there in winter 1919–1920)
    Age in 1919to ask the family: an approximate age narrows the hits

    What I will run

    Lipes database (jewishpogroms.info), Latin only. First a control query, Lipes, which should return about 23–24 records; if it fails, the site is down and a zero means nothing. Then each spelling, the wildcard Krav*, and the shtetl without a surname.
    2. Am HaZikaron (pogrom.amhazikaron.org), Cyrillic substring: Кравец, Кравц, and the place.
    3. Cross-check: the same person in both databases with the same archive file is one piece of evidence, not two.
    4.

    For any hit: fond / inventory / file / folio, then the DAKO R-3050 inventory on Wikisource, then the scan on Wikimedia Commons, then the page read word for word.

    How results will be reported

    • Database row only: a hint ⚪, not a fact.
    • Row + archive page with a second identifier (age, patronymic, address): a finding.
    • Nothing found: the full log — databases, spellings, control query, date — so the next search does not repeat this one.

    Next step: tell me the shtetl and Moishe's approximate age, and I will start with the control query.

    Names in this example are fictional. No search results are shown here because none were run.

    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

    • Your family lived in a shtetl of Kyiv, Podolia, Volhynia, Kherson, Ekaterinoslav or Chernigov province in 1917–1922.
    • Someone "vanished" or died around 1919–1921, and the family speaks of a pogrom, a gang, an orphanage or money "from America".
    • You are checking a whole family for those years and need the pogrom sources done properly.

    The problem

    The records exist, but they are split between volunteer databases with different search rules (one is Latin-only, the other Cyrillic substring), archival fonds in Kyiv, and about 900 scans on Wikimedia Commons. A database row is not a proof, and an empty result often means a broken query, not an absent person.

    What your agent does with this skill

    • Builds an identification set first: every spelling in Latin and Cyrillic, Jewish and Russian forms of the given name, the shtetl, neighbouring shtetls and the nearest city.
    • Searches the Lipes database (jewishpogroms.info, about 77,000 records with archive references) and Am HaZikaron (pogrom.amhazikaron.org, about 7,900 victims with sources), with wildcards and a search by place.
    • Runs a control query before trusting any zero.
    • Turns a database row into fond / inventory / file / folio, finds the file in the DAKO R-3050 inventory and the scan on Commons, and reads the page word for word: age, address, who reported, relief sum.
    • Covers the living too: 1922 relief recipients with addresses, orphanage children, refugees — often the lead to an American branch through a hometown society.
    • Includes a small Python script for both databases and a search-log template.

    Why it does not make things up

    • A database row alone is reported as a hint; a finding needs the archive page with a second identifier (age, patronymic, address, relatives).
    • "Not found" only with the log: databases, spellings, mode, control query, date.

    Author

    Anna Shefel, family-history researcher. Open guide: https://shefelchana.github.io/genealogy-guide-ru/

    Covers 1917–1922 pogrom records of Ukraine and neighbouring regions. The databases are volunteer projects: fields can be shifted and coverage is incomplete, so a database zero is never proof. The script depends on the two public sites being online.

    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 today

    Requires

    Jewishpogroms
    Amhazikaron

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files

    Allowed Hosts

    jewishpogroms.info
    pogrom.amhazikaron.org

    Shell/Python: the bundled script pogrom_search.py. Network: jewishpogroms.info and pogrom.amhazikaron.org (public search pages), Wikisource and Wikimedia Commons for inventories and scans. Read/Write Files: a search log in the user's project folder.

    Listedtoday

    What's inside

    Frequently Asked Questions

    The Lipes database (jewishpogroms.info, about 77,000 records with archive references; Latin-only search), Am HaZikaron (pogrom.amhazikaron.org, about 7,900 victims with sources; Cyrillic search), the Kyiv relief committee fond DAKO R-3050 with its inventories and about 900 scans on Wikimedia Commons, TsDAVO fond 2497 and the YIVO Tcherikower archive.

    No. The same sources list the wounded, the robbed, widows, 1922 relief recipients with addresses, children in orphanages and refugees, so it is worth checking living relatives too. A relief recipient on a hometown-society list is often a lead to the American branch.

    No. A database row is a hint. The skill takes your agent to the archive page and counts it as a finding only when the name matches together with a second identifier: age, patronymic, place, relatives or address.

    No accounts. Python 3 is optional: the bundled script queries both databases without a browser. Without Python the agent follows the same steps in the browser.

    The agent checks that the control query worked, tries every spelling and the place without a surname, and writes a search log. "Not found" is reported only with that log, so a later search does not have to repeat it.

    Yes: it is one of the 26 skills of the Genealogy Toolkit by the same author, sold separately for those who only need the pogrom records.

    New in Research & Analysis