Skill by ara.so — Daily 2026 Skills collection.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionautoresearch-genealogyExecute the skills CLI command in your project's root directory to begin installation:
Fetches autoresearch-genealogy from aradotso/trending-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate autoresearch-genealogy. Access via /autoresearch-genealogy in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
22
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
22
stars
Skill by ara.so — Daily 2026 Skills collection.
A structured system of autoresearch prompts, Obsidian vault templates, archive guides, and methodology references for AI-assisted genealogy research. Built for Claude Code's autonomous research loops, adaptable to any AI tool or manual workflow.
/autoresearch prompts that autonomously search the web, update your vault, and self-verify results# Clone the repository
git clone https://github.com/mattprusak/autoresearch-genealogy.git
cd autoresearch-genealogy
# Copy vault template into your Obsidian vault
cp -r vault-template/ ~/path/to/your/ObsidianVault/genealogy/
# Or copy to any markdown editor folder
cp -r vault-template/ ~/Documents/my-genealogy/
No package manager or build step required — this is a pure markdown/prompt project.
autoresearch-genealogy/
├── prompts/ # 12 autoresearch prompt files for Claude Code
├── vault-template/ # 19-file Obsidian vault starter kit
│ ├── Family_Tree.md
│ ├── Research_Log.md
│ ├── Open_Questions.md
│ ├── templates/ # Person, certificate, postcard, region, etc.
│ └── ...
├── archives/ # 24 country/region research guides
├── reference/ # 9 methodology documents
├── workflows/ # 7 step-by-step process guides
└── examples/ # 6 anonymized worked examples
Open vault-template/Family_Tree.md and fill in what you already know, starting with yourself and working backward:
---
title: Family Tree
last_updated: 2026-03-19
generations_documented: 3
lines_active: 2
---
# Family Tree
## Generation 1 (Self)
- **Name**: Jane Smith (b. 1985, Chicago, IL)
## Generation 2 (Parents)
- **Father**: John Smith (b. 1955, Detroit, MI)
- **Mother**: Mary O'Brien (b. 1958, Boston, MA)
## Generation 3 (Grandparents)
- **Paternal Grandfather**: Robert Smith (b. ~1920, unknown)
- **Paternal Grandmother**: Helen Kowalski (b. ~1925, Poland?)
Photograph or scan certificates, letters, postcards. Use the OCR workflow:
See: workflows/ocr-pipeline.md
/autoresearch prompts/01-tree-expansion.md
/autoresearch prompts/02-cross-reference-audit.md
Each prompt in prompts/ follows this structure:
## Goal
[What this iteration should accomplish]
## Metric
[Measurable success condition — e.g., "increase sourced person files from N to N+10"]
## Direction
[Step-by-step instructions for the AI]
## Verify
[Cross-check to run after each iteration]
## Guard Rails
[What NOT to do — prevent hallucination, preserve source rigor]
## Iterations
[How many loops to run before stopping for human review]
## Protocol
[Output format, file naming, YAML fields to populate]
| File | Purpose |
|---|---|
01-tree-expansion.md |
Push every branch back using web research |
02-cross-reference-audit.md |
Find and fix discrepancies between tree and sources |
03-findagrave-sweep.md |
Locate Find a Grave memorials for deceased ancestors |
04-gedcom-completeness.md |
Sync GEDCOM file with vault data |
05-source-citation-audit.md |
Verify every person has ≥2 independent sources |
06-unresolved-persons.md |
Identify and resolve unnamed people in documents |
07-timeline-gap-analysis.md |
Find life events where records should exist but don't |
08-open-question-resolution.md |
Systematically attack every open research question |
09-bygdebok-extraction.md |
Extract data from digitized local history books |
10-colonial-records-search.md |
Search pre-1800 colonial American records |
11-immigration-search.md |
Locate passenger manifests and naturalization records |
12-dna-chromosome-analysis.md |
Analyze per-chromosome ancestry data |
# In Claude Code terminal or chat:
/autoresearch prompts/08-open-question-resolution.md
# With a specific vault path context:
/autoresearch prompts/03-findagrave-sweep.md --context vault-template/Family_Tree.md
vault-template/templates/person.md)---
full_name: ""
birth_date: ""
birth_place: ""
death_date: ""
death_place: ""
father: ""
mother: ""
spouse: ""
children: []
confidence: "Moderate Signal" # Strong Signal | Moderate Signal | Speculative
sources: []
open_questions: []
last_updated: ""
---
# [Full Name]
## Life Events
| Event | Date | Place | Source |
|-------|------|-------|--------|
| Birth | | | |
| Marriage | | | |
| Death | | | |
## Sources
1. [Source 1 — type, repository, date accessed]
2. [Source 2 — type, repository, date accessed]
## Open Questions
- [ ] Question 1
- [ ] Question 2
## Notes
[Narrative summary, naming variant notes, contextual history]
vault-template/templates/certificate.md)---
document_type: "" # birth | death | marriage | baptism
document_date: ""
repository: ""
file_reference: ""
transcribed_by: ""
transcription_date: ""
confidence: ""
---
# Certificate: [Type] — [Name] — [Year]
## Transcription
[Verbatim transcription of the document]
## Key Data Extracted
- **Subject**:
- **Date**:
- **Place**:
- **Witnesses/Informants**:
- **OfficiantMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added autoresearch-genealogy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in autoresearch-genealogy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
autoresearch-genealogy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: autoresearch-genealogy is the kind of skill you can hand to a new teammate without a long onboarding doc.
autoresearch-genealogy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
autoresearch-genealogy has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend autoresearch-genealogy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: autoresearch-genealogy is focused, and the summary matches what you get after install.
Keeps context tight: autoresearch-genealogy is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in autoresearch-genealogy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 69