What problem does it solve?
A persistent research-wiki prevents your team from repeatedly re-deriving context by consolidating papers, ideas, experiments, claims, and relationships into a single evolving knowledge base.
Core Features & Use Cases
- Structured knowledge capture: Store papers, ideas, experiments, and claims with stable node IDs and a consistent schema.
- Relationship graph with typed edges: Maintain evidence-backed links (e.g., extends, addresses_gap, tested_by) in graph/edges.jsonl while auto-generating Connections views.
- Context-efficient discovery: Generate query_pack.md for fast, bounded summaries that prioritize gaps and failed ideas for better downstream ideation.
- Operational lifecycle: Initialize the wiki, ingest papers, batch sync backfilled arXiv IDs, query the landscape, lint health, and view stats.
- Use cases: Build a durable field map for thesis/research projects, systematically track what works/doesn’t, and power ideation/claim-evaluation workflows that rely on an up-to-date graph.
Quick Start
Initialize the wiki by running the research-wiki skill with the init argument so the required folders and schema files are created.
