author-e2e-fixture

Authors end-to-end test fixtures for the GPS genealogy research benchmark from FamilySearch snapshots or research documents.

3|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill author-e2e-fixture-pioneeraiacademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: author-e2e-fixture
Source: https://github.com/PioneerAIAcademy/cowork-genealogy/tree/main/.claude/skills/author-e2e-fixture
Command: npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill author-e2e-fixture-pioneeraiacademy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating benchmark test cases for genealogy research agents requires manually snapshotting FamilySearch trees, stripping answers, and writing expected findings — a slow, error-prone process. This Skill automates the mechanical work while guiding the author through the judgement calls. ## Core Features & Use Cases - PID-based fixture authoring: Snapshot a well-researched deceased person's FamilySearch tree, strip a focused subset (the "answer"), and record expected findings for scoring. - PID-less document path: Construct a starting tree from a bundled research report, research log, or proof article when FamilySearch access is unavailable. - Record-hint fixtures: Author fixtures where the answer lives in a historical record hint rather than the tree itself. - Use Case: A benchmark maintainer says "make a benchmark from this PID" — the Skill snapshots the tree, scaffolds fixture.json and starting-research.json, strips the answer, validates against JSON Schemas, and enforces the living-person gate before handoff. ## Quick Start Ask the assistant to create an e2e fixture from a FamilySearch person ID, for example: "Author an e2e fixture for PID L2QR-9XY about recovering his parents in the 1850s."

Frequently Asked Questions about author-e2e-fixture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an e2e test fixture from a FamilySearch person ID?▼

Confirm the person is deceased, then run the snapshot command with a slug and PID from the eval/harness directory. The script fetches and normalizes the tree, prints an id index, and you then scaffold metadata, write expected findings, strip the answer ids, and validate.

How do I build a genealogy benchmark fixture without FamilySearch access?▼

Use the PID-less path: read the research document end to end, separate the known starting context from the documented conclusion, and construct the starting GedcomX tree manually. Scaffold with --subject-id I1 instead of --pid, leaving source_pid as the PID-TODO placeholder.

Can I commit e2e fixtures about living persons to FamilySearch benchmarks?▼

No. FamilySearch terms of service forbid committing fixtures about living persons, and the snapshot script re-checks every person in the tree and refuses on any who are living or unmarked. Confirm the subject is deceased before fetching anything.

Why does the snapshot script refuse to overwrite an existing fixture?▼

A fixture is snapshotted once because re-fetching a mutable upstream tree would silently rewrite the test and make scores incomparable across runs. To re-strip, re-run the strip command against the committed snapshot; use snapshot --check to detect upstream drift.

What is a record-hint fixture in genealogy benchmark testing?▼

A record-hint fixture is a PID-path variant where the answer was never in the tree but lives in a historical record matched with unverified confidence. It uses scaffold --genre record-hint and strip --none, keeping the starting tree identical to the snapshot.