rdeknijf/scorecard
.claude/skills/scorecard/SKILL.md
Generate a research scorecard comparing the original MyHeritage GEDCOM baseline against the current tree to show all discoveries made by AI research. Use when: (1) user asks "what have we discovered?", "show me the score", "scorecard", "/scorecard", (2) user wants to show progress to family members, (3) after a research session to summarize what was accomplished. Compares by UID matching (not record IDs) to handle Gramps Web renumbering.
$ install --global
skillsauthnpx skillsauth add rdeknijf/ai-genealogy-kit scorecardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 9:00 PM1.8s1 file scanned
SKILL.md
- name:
- scorecard
- description:
- |
- author:
- Claude Code
- version:
- 1.0.0
- date:
- 2026-03-15
Genealogy Research Scorecard
Problem
After research sessions that add ancestors, enrich records, and cite archive sources, it's hard to see the cumulative impact. The scorecard compares the original MyHeritage export against the current tree to quantify everything that's been discovered.
Context / Trigger Conditions
- User asks for a scorecard, progress summary, or "what have we found"
- User wants to show family members what the AI research has accomplished
- End of a research session — summarize the session's additions
/scorecardcommand
Solution
Run the scorecard script:
uv run .claude/skills/scorecard/scripts/scorecard.py
Optional arguments for custom paths:
uv run .claude/skills/scorecard/scripts/scorecard.py [baseline.ged] [current.ged]
Defaults to private/original_myheritage_baseline.ged and private/tree.ged.
How It Works
-
UID matching — MyHeritage assigns
_UIDfields to every record. Gramps Web renumbers record IDs (I500xxx → I0xxx), but UIDs persist. The script matches records across files by UID, not by GEDCOM ID. -
New people detection — Anyone in the current tree with no UID match in the baseline is genuinely new. Split into:
- Research additions (I600xxx series — added by archive research)
- Smart Match additions (other IDs — came via Gramps Web)
-
Enrichment detection — For UID-matched people, compares birth dates, places, death dates, parent links, occupations, and archive source citations (S600xxx series).
-
Source counting — Only counts S600xxx sources (our archive citations), not the original MyHeritage sources.
-
Family connections — Counts new F600xxx family records.
Output
A formatted scorecard showing:
- New ancestors discovered (research vs Smart Match)
- Official archive sources cited (with titles)
- Existing records enriched (birth/death dates, places, parents, occupations)
- Per-person enrichment details
- Grand total of new facts
Notes
- The baseline file (
original_myheritage_baseline.ged) must exist in the project root. This is the unmodified first export from MyHeritage. - The I600xxx/F600xxx/S600xxx ID convention is specific to this project's research workflow — records added by AI research use this range to avoid conflicts with Gramps Web's auto-numbering.
- GEDCOM slash formatting differences (e.g.,
de Knijfvs/de Knijf/) are NOT counted as changes — the script compares by UID, not name text.
Related Skills
rdeknijf/wiewaswie
tools
VerifiedTrustedCommunity
Search Dutch civil registry records (births, marriages, deaths) on WieWasWie.nl via direct JSON API calls, with Open Archives API as a secondary source and Playwright browser automation as fallback. Use this skill whenever you need to look up or verify a person in Dutch civil records, check a birth/marriage/death date against official archives, or find parents/spouses from indexed Burgerlijke Stand records. Triggers on: "look up on wiewaswie", "check the birth record", "find the marriage certificate", "verify this date in the civil registry", "/wiewaswie", or any request to search Dutch genealogical records for a specific person. Also use when comparing GEDCOM data against official sources or when a Tier B verification is needed.
2SKILL.mdUpdated Apr 17, 2026
rdeknijf/voc-opvarenden
development
VerifiedTrustedCommunity
Search the VOC Opvarenden database for Dutch East India Company crew records (1699-1794). Uses the Nationaal Archief HUB3 API — 853,785 indexed entries with rich detail: name, origin, rank, ship, fate (died/returned/deserted), service dates, VOC chamber, and links to original scans. Use this skill when: "search VOC records", "VOC crew", "VOC opvarenden", "sailed to Batavia", "Dutch East India Company", "VOC soldier", "VOC sailor", "/voc-opvarenden", or when looking for ancestors who may have sailed with the VOC. Also use when checking Daniel Pieterse Knijf (1704, Woerden) or any Knijf/Knijff VOC connections. No login required.
2SKILL.mdUpdated Apr 17, 2026
rdeknijf/verify-scans
tools
VerifiedTrustedCommunity
Generate a scan verification page for the user to review AI-extracted genealogy findings against actual document scans. The user clicks through records, confirms or rejects each one, and confirmed records become Tier A evidence in FINDINGS.md. Use this skill when: "verify scans", "show me what needs verifying", "review pending scans", "scan verification", "/verify-scans", or when the user wants to upgrade research findings from Tier C/D to Tier A by visually confirming document scans. Also use after a research session that produced scan-backed findings that need human confirmation.
2SKILL.mdUpdated Apr 17, 2026
rdeknijf/streekarchief-midden-holland-optimized
tools
VerifiedTrustedCommunity
Search indexed person records at Streekarchief Midden-Holland (samh.nl) via the Memorix Genealogy REST API. No browser automation needed — returns structured JSON in ~50ms per query. Based in Gouda, covers municipalities: Gouda, Haastrecht, Schoonhoven, Waddinxveen, Noord-Waddinxveen, Moerkapelle, Moordrecht, Ammerstol, Broek, Vlist, and surrounding areas in the Midden-Holland region of South Holland. 3M+ person records with DTB (doop/trouw/begraven), BS (geboorte/huwelijk/overlijden), and Inschrijvingaktes. 36 Knijf results found, including Gijsbert de Knijf records in Gouda and van der Knijf in Waddinxveen. Scans available for most records. Triggers on: "search Gouda archive", "Streekarchief Midden-Holland", "SAMH", "Haastrecht records", "Schoonhoven records", "/streekarchief-midden-holland", or any genealogy research in the Gouda/Midden-Holland area. No login required. Parallelizable — run multiple queries simultaneously.
2SKILL.mdUpdated Apr 17, 2026