Family History Research Planning for Muse
Plan first, search second: disciplined genealogy methodology
- What
- Plan first, search second: disciplined genealogy methodology
- Cost
- Free
- Needs
- a family-history research project or question (an ancestor to research, a brick wall to break through). No accounts or API keys required.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A methodology-first companion for family history: its core rule is plan before searching — when you mention an ancestor, it gathers what you already know, defines the research question, and builds a structured research plan (objectives, FAN-principle strategy, prioritized sources, timeline, success criteria) before any search happens. Beyond planning it generates Evidence Explained–style citations for 14+ record types, runs a seven-step evidence analysis and conflict-resolution framework (source inventory, reliability ranking, comparison matrix, GPS compliance check, proof argument with proof levels), and keeps disciplined research logs of every session, including negative results. Ships with ready-to-use templates (research plan, citation library, evidence analysis, research log) and deep references on citation templates, evidence evaluation, research strategies, and GPS guidelines. Discovered via skills.sh. Honest note: this is a planning and methodology skill — it structures and documents your research rather than finding ancestors for you, and execution only proceeds on your explicit request. It complements rather than duplicates the genealogy research-partner skill: use this one to plan, that one to dig. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @emaynard.
Version:
Quick answer
Family History Research Planning for Muse is a free Muse skill built on a simple rule: plan first, search second, as a disciplined genealogy methodology. When you mention an ancestor, it gathers what you already know, defines the research question, and builds a structured research plan with objectives, a FAN-principle strategy, prioritized sources, a timeline and success criteria.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 7334d3dStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a family-history research project or question (an ancestor to research, a brick wall to break through). No accounts or API keys required. Install "Family History Research Planning for Muse" for me. A methodology-first companion for family history: builds a structured research plan (objectives, FAN-principle strategy, prioritized sources, timeline, success criteria) before any search happens, generates Evidence Explained–style citations for 14+ record types, runs a seven-step evidence analysis and conflict-resolution framework, and keeps disciplined research logs. Repository: https://raw.githubusercontent.com/emaynard/claude-family-history-research-skill/7334d3d400740fda3de1c54c90e186307f8f1176/SKILL.md Pinned version: install the code at commit 7334d3d400740fda3de1c54c90e186307f8f1176 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files: references/, assets/templates/) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "family-history-planning". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. describe the ancestor or research question I want to plan for). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 7334d3d · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.