resolve-record-hint

Resolves draft record-hint e2e fixtures by encoding genealogist verdicts into expected-findings.json.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Draft genealogy e2e fixtures of genre record-hint start as unverified FamilySearch hint transcriptions, and hand-editing their expected-findings.json risks structural errors and invalid fields. This Skill walks a genealogist through confirming or refuting the hint, then writes the correct fixture files and validates them. ## Core Features & Use Cases - Issue and fixture discovery: Parses a GitHub issue titled "test <slug>" to extract the tree person and hint record URLs, then reads the fixture's README, expected-findings.json, and fixture.json. - Outcome encoding: Writes one of three outcomes (true match, corrected answer, or false match with avoid-polarity findings) using only spec-defined fields and required FamilySearch arks. - Validation and handoff: Runs the e2e fixture validator and updates the README's "Notes for reviewers" and fixture.json notes. - Use Case: A genealogist assigned GitHub issue "test chresten-nielsen-daughter" researches the hint on familysearch.org, concludes it is a false match, and the Skill writes the avoid/required finding pair with the disproving record's ark and validates the fixture. ## Quick Start Resolve the record-hint fixture assigned to me in GitHub issue "test <slug>" and encode my verdict in expected-findings.json.

Frequently Asked Questions about resolve-record-hint

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

FAQPage Schema
How do I resolve a record-hint e2e fixture?▼

Provide the GitHub issue number or fixture slug, research the tree person and hint record on familysearch.org, then state your verdict. The Skill writes expected-findings.json, updates the README and fixture.json notes, and runs the fixture validator.

What outcomes can a record-hint fixture resolution have?▼

Three outcomes exist: true match, answerable but differently with a corrected record, or false match with no findable substitute. Every outcome requires a resolvable FamilySearch ark in supporting_sources, with false matches using an avoid-polarity finding paired with a required finding.

Does the skill fetch the FamilySearch hint record itself?▼

No, the genealogist performs all record retrieval and makes the identity judgement by hand. The Skill only writes up their conclusion into the fixture files, since the identity call is the GPS work the benchmark measures.

Why does fixture validation fail after editing expected-findings.json?▼

Validation hard-fails on unrecognized fields such as expectation, which is not a real spec field, or on missing literal ark:/61903 references in supporting_sources. Only the fields id, type, description, details, polarity, supporting_sources, and required are permitted.

When should I not use this fixture resolution skill?▼

Do not use it to author a brand-new fixture from a FamilySearch PID, to interpret or grade a completed e2e run, or to mine a unit test from a miss. Those tasks belong to the author-e2e-fixture, interpret-e2e-result, grade-e2e-run, and mine-unit-test skills.