[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F3MG1SFPFBF68S02F819SD":3,"skill-same:01M7F3MG1SFPFBF68S02F819SD":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":48},"01M7F3MG1SFPFBF68S02F819SD","genealogy-research-planner",null,"Use when genealogy-mode or the user needs the next search chosen, competing explanations tested or a stalled case unblocked. Not for running the searches themselves.","rfsbraz\u002Fgenealogy-agent-skills","rfsbraz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F770716?v=4","01M7F3GV59M34EQRKYSA0J1J6A","Rodrigo Braz","01M7F3GV619TKMR89TF23C02ZW",0,"MIT","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-planner\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: genealogy-research-planner\ndescription: \"Use when genealogy-mode or the user needs the next search chosen, competing explanations tested or a stalled case unblocked. Not for running the searches themselves.\"\nlicense: MIT\ncompatibility: \"Python 3.10+ for the gap finder (standard library only).\"\nmetadata:\n  author: Rodrigo Braz\ndisable-model-invocation: true\n---\n\n# Plan Genealogy Research\n\nRead the [shared research contract](..\u002Fgenealogy-mode\u002Freferences\u002Fshared-contract.md) and [data model](..\u002Fgenealogy-mode\u002Freferences\u002Fdata-model.md) before writing case state. Resolve sibling skills by their declared names if the host uses different folder names. This suite assumes the coordinator is installed alongside its workflow skills. Read only additional references relevant to this task. Those files point on to the coordinator's [GPS policy](..\u002Fgenealogy-mode\u002Freferences\u002Fgps-policy.md), [easy-use rules](..\u002Fgenealogy-mode\u002Freferences\u002Feasy-use.md), [revisions and projections](..\u002Fgenealogy-mode\u002Freferences\u002Frevisions-and-projections.md) and [host adapter contract](..\u002Fgenealogy-mode\u002Freferences\u002Fhost-adapter.md); read them when the task touches them.\n\n## Inputs\n\nActive question; existing observations and conclusions; candidate identities; source portfolios; coverage\u002Fsearch log; access and budget constraints.\n\n## Procedure\n\n1. State the question precisely and list plausible explanations, including an unknown\u002Funresolved option. Separate identity uncertainty from uncertainty about an event or relationship.\n2. For each explanation state what observations would support or contradict it. Identify which available sources can distinguish the explanations rather than merely repeat known names.\n3. Review already searched collections and exact coverage. Do not repeat a search unless the date range, query, index, source access or interpretation has materially changed.\n4. Rank actions qualitatively by discriminating value, expected information, independence, access, effort and dependencies. Record the rationale; avoid pseudo-precise probability scores.\n5. Specify each action: target creator\u002Fcollection; names and variants; period; locality; search\u002Fbrowse method; expected clue; stopping condition; result categories; fallback.\n6. Plan bounded batches. After findings, update hypotheses and the next action. Read enough surrounding material to establish context when necessary without expanding into unrelated family branches.\n7. If stalled, audit assumptions, original readings, locality, custody, naming variants, collateral relatives and source gaps. Seek an original behind an index, browse unindexed pages, inspect witnesses and neighbours, or search destination records for origins.\n8. If no useful feasible action remains, record what prevents resolution and what new evidence would restart it. Distinguish a budget pause from a conclusion that reasonably exhaustive research has been reached.\n\n## Output contract\n\nOrdered action list; hypothesis tests; coverage gaps; alternative strategy; explicit stop\u002Frestart conditions.\n\nUse the shared handoff envelope: case\u002Fquestion IDs, status, artifacts and evidence IDs, findings, uncertainties, actions actually performed, next actions and blockers. Store observations before conclusions; preserve field-level uncertainty.\n\n## Quality gates and failure handling\n\nDo not reward volume of searches or number of ancestors. Do not assume age estimates or repeated online trees outweigh better evidence. A broad goal does not authorize spending or contacting people.\n\nIf a required capability is unavailable, record what was and was not done, use a documented available fallback, and return a specific handoff. Never simulate a successful external action or fabricate a source, citation, tool result or reviewer report.\n\n## Tools and dependencies\n\nCase and search ledger; source\u002Frepository portfolios; optional estimates of actual tool cost and available budget. For a tree with gaps, run scripts\u002Fgap_finder.py `gaps` with a source registry folder: it lists the records that should exist for each person (detail) and the searches that find parents and children (expand), skips searches the case already settled and flags paid sources for approval. See [references\u002Fsource-registry.md](references\u002Fsource-registry.md).\n\n## Handoffs\n\nAcquisition executes actions; discovery fills source gaps; proof-evaluation assesses whether remaining searches matter to a conclusion.\n\n## Example\n\nAfter three name searches fail, inspect index coverage and the parish register itself, or pursue the person’s marriage, rather than repeat the same name query.\n\n## Bundled resources\n\n- [research-plan-template.md](assets\u002Fresearch-plan-template.md)\n- [source-registry.md](references\u002Fsource-registry.md)\n- [gap_finder.py](scripts\u002Fgap_finder.py)\n- [source-registry.schema.json](assets\u002Fsource-registry.schema.json)\n- [source-registry-template.json](assets\u002Fsource-registry-template.json)\n\n## GPS coverage and a manageable plan\n\nKeep the full question-specific source\u002Fcoverage plan in the case. Show the user only the next best action and, when helpful, two alternatives. In the coverage assessment record jurisdiction, period, record family, completed searches, gaps and why further avenues matter. Choose sources for their ability to distinguish hypotheses, not a fixed document count. A short displayed plan never limits the research necessary for a sound conclusion. Read the coordinator’s gps-policy.md before proposing that a question is resolved.\n","# Plan Genealogy Research\n\nRead the [shared research contract](..\u002Fgenealogy-mode\u002Freferences\u002Fshared-contract.md) and [data model](..\u002Fgenealogy-mode\u002Freferences\u002Fdata-model.md) before writing case state. Resolve sibling skills by their declared names if the host uses different folder names. This suite assumes the coordinator is installed alongside its workflow skills. Read only additional references relevant to this task. Those files point on to the coordinator's [GPS policy](..\u002Fgenealogy-mode\u002Freferences\u002Fgps-policy.md), [easy-use rules](..\u002Fgenealogy-mode\u002Freferences\u002Feasy-use.md), [revisions and projections](..\u002Fgenealogy-mode\u002Freferences\u002Frevisions-and-projections.md) and [host adapter contract](..\u002Fgenealogy-mode\u002Freferences\u002Fhost-adapter.md); read them when the task touches them.\n\n## Inputs\n\nActive question; existing observations and conclusions; candidate identities; source portfolios; coverage\u002Fsearch log; access and budget constraints.\n\n## Procedure\n\n1. State the question precisely and list plausible explanations, including an unknown\u002Funresolved option. Separate identity uncertainty from uncertainty about an event or relationship.\n2. For each explanation state what observations would support or contradict it. Identify which available sources can distinguish the explanations rather than merely repeat known names.\n3. Review already searched collections and exact coverage. Do not repeat a search unless the date range, query, index, source access or interpretation has materially changed.\n4. Rank actions qualitatively by discriminating value, expected information, independence, access, effort and dependencies. Record the rationale; avoid pseudo-precise probability scores.\n5. Specify each action: target creator\u002Fcollection; names and variants; period; locality; search\u002Fbrowse method; expected clue; stopping condition; result categories; fallback.\n6. Plan bounded batches. After findings, update hypotheses and the next action. Read enough surrounding material to establish context when necessary without expanding into unrelated family branches.\n7. If stalled, audit assumptions, original readings, locality, custody, naming variants, collateral relatives and source gaps. Seek an original behind an index, browse unindexed pages, inspect witnesses and neighbours, or search destination records for origins.\n8. If no useful feasible action remains, record what prevents resolution and what new evidence would restart it. Distinguish a budget pause from a conclusion that reasonably exhaustive research has been reached.\n\n## Output contract\n\nOrdered action list; hypothesis tests; coverage gaps; alternative strategy; explicit stop\u002Frestart conditions.\n\nUse the shared handoff envelope: case\u002Fquestion IDs, status, artifacts and evidence IDs, findings, uncertainties, actions actually performed, next actions and blockers. Store observations before conclusions; preserve field-level uncertainty.\n\n## Quality gates and failure handling\n\nDo not reward volume of searches or number of ancestors. Do not assume age estimates or repeated online trees outweigh better evidence. A broad goal does not authorize spending or contacting people.\n\nIf a required capability is unavailable, record what was and was not done, use a documented available fallback, and return a specific handoff. Never simulate a successful external action or fabricate a source, citation, tool result or reviewer report.\n\n## Tools and dependencies\n\nCase and search ledger; source\u002Frepository portfolios; optional estimates of actual tool cost and available budget. For a tree with gaps, run scripts\u002Fgap_finder.py `gaps` with a source registry folder: it lists the records that should exist for each person (detail) and the searches that find parents and children (expand), skips searches the case already settled and flags paid sources for approval. See [references\u002Fsource-registry.md](references\u002Fsource-registry.md).\n\n## Handoffs\n\nAcquisition executes actions; discovery fills source gaps; proof-evaluation assesses whether remaining searches matter to a conclusion.\n\n## Example\n\nAfter three name searches fail, inspect index coverage and the parish register itself, or pursue the person’s marriage, rather than repeat the same name query.\n\n## Bundled resources\n\n- [research-plan-template.md](assets\u002Fresearch-plan-template.md)\n- [source-registry.md](references\u002Fsource-registry.md)\n- [gap_finder.py](scripts\u002Fgap_finder.py)\n- [source-registry.schema.json](assets\u002Fsource-registry.schema.json)\n- [source-registry-template.json](assets\u002Fsource-registry-template.json)\n\n## GPS coverage and a manageable plan\n\nKeep the full question-specific source\u002Fcoverage plan in the case. Show the user only the next best action and, when helpful, two alternatives. In the coverage assessment record jurisdiction, period, record family, completed searches, gaps and why further avenues matter. Choose sources for their ability to distinguish hypotheses, not a fixed document count. A short displayed plan never limits the research necessary for a sound conclusion. Read the coordinator’s gps-policy.md before proposing that a question is resolved.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":25,"disable-model-invocation":26},{"author":12},"Python 3.10+ for the gap finder (standard library only).",true,"main","9a891a10f7b92951b5669c5207bd76d6f3ed155f","skills\u002Fgenealogy-research-planner","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002FINSTALL.md","https:\u002F\u002Fgithub.com\u002Frfsbraz","rodrigobraz.com","Senior Server Engineer at Scopely, on Stumble Guys. On the side I build SaaS and open-source tools, like deleterr.","2026-11-09 18:03:51",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":26},[38,41,44],{"tool":39,"command":40},"npx","npx skills add rfsbraz\u002Fgenealogy-agent-skills --skill genealogy-research-planner",{"tool":42,"command":43},"bunx","bunx skills add rfsbraz\u002Fgenealogy-agent-skills --skill genealogy-research-planner",{"tool":45,"command":46},"pnpm","pnpm dlx skills add rfsbraz\u002Fgenealogy-agent-skills --skill genealogy-research-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-planner\u002FSKILL.md",[49,55,61,65,69,73],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",302,"https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-planner\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Fresearch-plan-template.md","ASSET","资产文件",792,"https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-planner\u002Fassets\u002Fresearch-plan-template.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"assets\u002Fsource-registry-template.json",1039,"https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-planner\u002Fassets\u002Fsource-registry-template.json",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"assets\u002Fsource-registry.schema.json",3442,"https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-planner\u002Fassets\u002Fsource-registry.schema.json",{"path":70,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fsource-registry.md",4538,"https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-planner\u002Freferences\u002Fsource-registry.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fgap_finder.py","SCRIPT","脚本",27667,"https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-planner\u002Fscripts\u002Fgap_finder.py",[80,87,94,101,108,115],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7F3MZ99QVF8802RCCE8E82J","genealogy-transcribe-quick","Use when genealogy-mode or the user wants a fast first reading of a long document for searchable text and leads. Not for consequential readings, which need transcribe-detailed.","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-transcribe-quick\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7F3MS3EK931QGMZSTB1Y13D","genealogy-transcribe-detailed","Use when genealogy-mode or the user needs a diplomatic reading of chosen pages using four distinct handwriting methods. Not for a fast first pass, which transcribe-quick does.","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-transcribe-detailed\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7F3MKWXHEYD0WNMS1DES3X9","genealogy-source-discovery","Use when genealogy-mode or the user needs collections, volumes or entries found for an open question in catalogues and indexes. Not for mapping a new country's sources.","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-source-discovery\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7F3MAVQXB4TP4BV35KF8AHC","genealogy-research-maintenance","Use when genealogy-mode or the user needs case evidence kept consistent after discoveries, merges, imports or corrections. Not for planning the next search.","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-maintenance\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7F3M557VDJNDGN048CQRYZ8","genealogy-repository-discovery","Use when genealogy-mode or the user needs the archives, registries or libraries that hold records for a place and period. Not for writing to them or searching their catalogues.","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-repository-discovery\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7F3M10HAY4DR74H3T7XCDAE","genealogy-reporting","Use when genealogy-mode or the user wants findings written up as cited reports, timelines, trees or handoffs. Not for literary life stories, which genealogy-narrative writes.","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-reporting\u002FSKILL.md",[],[]]