
from research-hub15
Operate Zotero, Obsidian and NotebookLM research workflows via CLI, MCP, and dashboard to collect, organize, and produce literature reviews and AI briefs.
Research Hub provides an AI-operable research workspace that connects Zotero, Obsidian, and NotebookLM (individually or together). It automates common researcher workflows — discovery, ingestion, clustering, note generation, and NotebookLM uploads — and exposes CLI and MCP server commands for integration into agent hosts and dashboards. Typical tasks include running full literature reviews, importing local files, generating AI briefs, and serving a dashboard for interactive management.
Use Research Hub when you need to automate academic or knowledge-work research tasks: gather and curate papers, backfill metadata in Zotero, create Obsidian notes, cluster source documents, produce AI-generated briefs, or upload bundles to NotebookLM. It's appropriate for researchers, data scientists, and teams that want repeatable research pipelines accessible via CLI or an MCP host.
research-hub dashboard, research-hub setup, research-hub auto, research-hub serve, research-hub doctor).doctor first, use --no-nlm for smoke tests).Compatible with CLI-friendly agents and MCP hosts; integrations noted for Claude Code, Cursor, Codex, and Gemini.
Research Hub is a research workflow orchestration skill combining Zotero, Obsidian, and NotebookLM. The SKILL.md is well-structured with clear workflow selection and operating rules. All 7 runnable scripts failed: Python scripts depend on the `research_hub` package which isn't available standalone, shell scripts need a git repo, and the .bat file is Windows-only. The code itself is high quality — well-documented, proper error handling, rate limiting — but requires the full project installed to function.
research_hubpytestyamljsonschemaWell-crafted research tool with thorough Python code (backfill_zotero.py is ~600 lines with rate limiting, backup, dry-run). Shell scripts follow best practices (set -euo pipefail, backup before overwrite). No security concerns. Main limitation: scripts are tightly coupled to the research_hub package and can't be audited independently. The .bat file leaks a local username/path but that's low severity.