search-full-text

Executes Lucene-style full-text searches against FamilySearch AI-transcribed historical document images.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Indexed genealogy search only finds people recorded as principals in structured name/date/place fields, missing witnesses, heirs, neighbors, and appraisers mentioned in narrative records. This Skill searches the raw transcript text of FamilySearch's AI-transcribed document images to surface those non-principal mentions while maintaining a GPS-conformant audit trail. ## Core Features & Use Cases - Lucene-style query construction: Builds queries with required terms (+), exclusions (-), phrases, and wildcards tuned to handwriting-transcription error patterns, with explicit handling of compound Iberian surnames and abbreviation variants. - GPS audit logging: Logs every search (including nil results) to research.json with staged result sidecars, and updates plan item status through structured appends. - Result triage and handoff: Triages staged result stubs, checks tree attachment status, and passes promising records to record-extraction. - Use Case: A researcher needs to find Patrick Flynn appearing as a witness in Schuylkill County deeds. The Skill runs an unscoped +Patrick +Flynn query, filters hits by place afterward, logs the search, and queues the record for extraction. ## Quick Start Run a full-text search for Patrick Flynn as a witness in FamilySearch historical documents and log the results to my research project.

Frequently Asked Questions about search-full-text

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

FAQPage Schema
How do I find a person mentioned as a witness in FamilySearch records?▼

Use full-text search with the surname in the name field or +GivenName +Surname in keywords, then filter by place after the initial search. FTS searches raw transcript text, so it finds witnesses, heirs, and neighbors that indexed search misses.

What is the difference between FamilySearch full-text search and indexed records search?▼

Full-text search queries raw AI transcript text with no fuzzy matching or Soundex, while indexed search matches structured name/date/place fields. FTS uniquely surfaces non-principal mentions but carries roughly a 10% transcription error rate.

Why does my FamilySearch full-text search return zero results?▼

Zero results usually mean overly restrictive terms, unsearched spelling or abbreviation variants, or a coverage gap since FTS covers only a growing subset of collections. Iterate up to five variant queries with wildcards before declaring a negative result.

Should I include place and date filters in the first full-text query?▼

No. Place filters match collection metadata rather than document content, causing false positives, and collection dates may differ from document dates. Search by name only first, then apply place, year, and record type filters after reviewing hit counts.

How do I search compound Spanish surnames in historical documents?▼

Require the two surnames as separate co-occurrence terms like +Naveda +Somarriba, never as a single phrase. The father's and mother's surnames appear on different people in parentage records, so phrase queries miss them.