mini-context-graph

Ingest documents into a wiki and typed knowledge graph with provenance.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/fizznix/mini-context-graph --skill mini-context-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mini-context-graph
Source: https://github.com/fizznix/mini-context-graph/tree/main
Command: npx skills add https://github.com/fizznix/mini-context-graph --skill mini-context-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps agents stop re-deriving knowledge from scratch by turning ingested documents into a persistent wiki plus a typed knowledge graph with evidence, so answers compound over time.

Core Features & Use Cases

  • Wiki-first knowledge compounding: Maintains summaries, entity pages, and topic pages so future queries hit the fast path first.
  • Typed entity/relation graph with provenance: Extracts entities and relations, stores confidence-weighted edges, and links every claim back to source chunks for auditability.
  • Graph traversal with evidence: Uses BFS (depth-capped) to assemble relevant subgraphs for multi-hop questions and returns supporting documents/chunks.

Quick Start

Ask an agent to ingest a new document by following ingestion.md, extract entities/relations, call ingest_with_content with supporting_text for each item, then query the knowledge graph with query_with_evidence to get an evidence-backed answer.

Frequently Asked Questions about mini-context-graph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does a knowledge graph with provenance help agents answer multi-hop questions?

A knowledge graph with provenance links extracted entities and confidence-weighted relations back to source documents. It enables agents to traverse depth-capped BFS subgraphs and retrieve multi-hop answers with direct evidence chunk links.

How do I ingest unstructured text into a wiki and knowledge graph for agent memory?

You ingest unstructured text by following YAML-guided extraction rules to extract entities and relations, then call the ingestion process with supporting text for each item to store normalized nodes and edges in JSON.

What's the best way to stop an agent from re-deriving knowledge from ingested documents every time?

Use a wiki-first retrieval system that builds persistent summaries and entity pages. This compounding wiki allows future queries to hit a fast path instead of re-processing unstructured text from scratch.

Do I need YAML extraction rules and an ontology to build a typed knowledge graph?

Yes, YAML-guided extraction rules and ontology-based normalization are required. They define how entities and relations are typed, normalized, and stored with confidence thresholds in the JSON knowledge graph.

How does querying a knowledge graph with evidence work for document retrieval?

Querying with evidence uses depth-capped BFS traversal to assemble relevant subgraphs from the typed knowledge graph. It returns answers alongside supporting documents and source text chunks for auditability.

Can I store knowledge graph nodes and edges without a database using JSON?

Yes, the typed knowledge graph stores nodes and edges directly in JSON files with confidence thresholds and evidence chunk links. This persistent JSON structure enables compounding wiki-first retrieval without external databases.