[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F3JCEAF5678DXRB03MXPRR":3,"skill-same:01M7F3JCEAF5678DXRB03MXPRR":54},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7F3JCEAF5678DXRB03MXPRR","genealogy-identity-resolution",null,"Use when genealogy-mode or the user must decide whether record mentions are the same person: common names, aliases, merges. Not for relationships between known people.","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-identity-resolution\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: genealogy-identity-resolution\ndescription: \"Use when genealogy-mode or the user must decide whether record mentions are the same person: common names, aliases, merges. Not for relationships between known people.\"\nlicense: MIT\nmetadata:\n  author: Rodrigo Braz\ndisable-model-invocation: true\n---\n\n# Resolve Person Identities\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\nPerson mentions; candidate persons; cited timelines; geographic and naming context; uncertainty and conflicting evidence.\n\n## Procedure\n\n1. Build a candidate table from all plausible identities, retaining an unknown alternative. Preserve separate IDs; normalization aids matching but never overwrites original names.\n2. Compare age intervals, family relationships, spouses, residences, occupations, signatures, witnesses, institutions and migration chronology. Explain agreement and disagreement for each candidate.\n3. Weight evidence by relevance, reliability and independence rather than counting matches. Repeated indexes or online trees derived from the same document add no independent support.\n4. Test chronological and geographic feasibility with explicit assumptions. Distinguish an unusual event from a contradiction; avoid unsupported biological or travel impossibility rules.\n5. Investigate disconfirming records and alternatives. Consider namesakes, remarriage, reused infant names, aliases, informant errors, boundary changes and multiple households.\n6. State whether mentions can be linked, remain candidates, or must be kept distinct. Tie the decision to observations and a written rationale. An apparently exact name\u002Fdate match can remain ambiguous.\n7. Propose a merge only after evidence review. Use a reversible mapping that preserves original IDs, assertions and provenance; record what changes and the ability to undo it. Update dependencies rather than deleting inconvenient evidence.\n8. Route consequential uncertainty to proof-evaluation and independent-review. If unresolved, specify the record most likely to distinguish candidates.\n\n## Output contract\n\nCandidate matrix; proposed mention-person links; identity conclusion\u002Fstatus; merge or separation proposal; disconfirming evidence and next test.\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\nNever auto-merge on fuzzy name similarity alone. Do not interpret two differently named records as separate people solely because surnames differ. Preserve unresolved links outside accepted tree relationships.\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\nTimeline\u002Fquery tools; transparent candidate matching; source-dependence graph; reversible change ledger.\n\n## Handoffs\n\nPlanner pursues discriminating sources; proof\u002Freview assesses the conclusion; maintenance applies authorized reversible updates.\n\n## Example\n\nTwo men share name and village but have distinct spouses and contemporaneous children. Keep separate candidates and investigate further instead of attaching both families to one person.\n","# Resolve Person Identities\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\nPerson mentions; candidate persons; cited timelines; geographic and naming context; uncertainty and conflicting evidence.\n\n## Procedure\n\n1. Build a candidate table from all plausible identities, retaining an unknown alternative. Preserve separate IDs; normalization aids matching but never overwrites original names.\n2. Compare age intervals, family relationships, spouses, residences, occupations, signatures, witnesses, institutions and migration chronology. Explain agreement and disagreement for each candidate.\n3. Weight evidence by relevance, reliability and independence rather than counting matches. Repeated indexes or online trees derived from the same document add no independent support.\n4. Test chronological and geographic feasibility with explicit assumptions. Distinguish an unusual event from a contradiction; avoid unsupported biological or travel impossibility rules.\n5. Investigate disconfirming records and alternatives. Consider namesakes, remarriage, reused infant names, aliases, informant errors, boundary changes and multiple households.\n6. State whether mentions can be linked, remain candidates, or must be kept distinct. Tie the decision to observations and a written rationale. An apparently exact name\u002Fdate match can remain ambiguous.\n7. Propose a merge only after evidence review. Use a reversible mapping that preserves original IDs, assertions and provenance; record what changes and the ability to undo it. Update dependencies rather than deleting inconvenient evidence.\n8. Route consequential uncertainty to proof-evaluation and independent-review. If unresolved, specify the record most likely to distinguish candidates.\n\n## Output contract\n\nCandidate matrix; proposed mention-person links; identity conclusion\u002Fstatus; merge or separation proposal; disconfirming evidence and next test.\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\nNever auto-merge on fuzzy name similarity alone. Do not interpret two differently named records as separate people solely because surnames differ. Preserve unresolved links outside accepted tree relationships.\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\nTimeline\u002Fquery tools; transparent candidate matching; source-dependence graph; reversible change ledger.\n\n## Handoffs\n\nPlanner pursues discriminating sources; proof\u002Freview assesses the conclusion; maintenance applies authorized reversible updates.\n\n## Example\n\nTwo men share name and village but have distinct spouses and contemporaneous children. Keep separate candidates and investigate further instead of attaching both families to one person.\n",{"name":5,"license":15,"metadata":24,"description":7,"disable-model-invocation":25},{"author":12},true,"main","9a891a10f7b92951b5669c5207bd76d6f3ed155f","skills\u002Fgenealogy-identity-resolution","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":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add rfsbraz\u002Fgenealogy-agent-skills --skill genealogy-identity-resolution",{"tool":41,"command":42},"bunx","bunx skills add rfsbraz\u002Fgenealogy-agent-skills --skill genealogy-identity-resolution",{"tool":44,"command":45},"pnpm","pnpm dlx skills add rfsbraz\u002Fgenealogy-agent-skills --skill genealogy-identity-resolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-identity-resolution\u002FSKILL.md",[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",309,"https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-identity-resolution\u002Fagents\u002Fopenai.yaml",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7F3MG1SFPFBF68S02F819SD","genealogy-research-planner","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.","https:\u002F\u002Fgithub.com\u002Frfsbraz\u002Fgenealogy-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgenealogy-research-planner\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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",[],[]]