research-wiki

To build a persistent knowledge graph from research papers, use a skill that ingests reading notes and maintains typed relationships across papers, ideas, experiments, and claims. It creates a queryable field map by storing structured entity relationships in a graph file.

Organizing scattered research notes for retrieval involves creating a persistent knowledge base that deduplicates information and tracks evidence. This approach maintains an audit trail of what changed and generates compact summaries for downstream ideation without re-deriving everything from scratch.

Yes, you can track typed relationships between experiments and claims by maintaining a structured entity graph. This process fits workflows that ingest papers and stores typed nodes and relationships as edges in a JSONL file for deterministic schema-driven updates.

You generate compact summaries from a research wiki by producing a budgeted query pack. This query-friendly markdown file helps downstream ideation and retrieval reuse the wiki efficiently, preventing valuable research from getting lost over time.

No external dependencies are required to initialize a research wiki. The process uses a canonical helper script resolved from a local tools directory and persists wiki artifacts including graph edges and query packs with deterministic schema-driven updates.

A research knowledge base loses valuable information over time because reading notes remain scattered and unconnected. Compounding this knowledge base by capturing papers, ideas, experiments, claims, and their relationships prevents loss and maintains a persistent audit trail.