im-wiki-extractor

Convert long chat logs into structured knowledge graphs with traceable entities and relationships.

248|30|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/cafe3310/public-agent-skills --skill im-wiki-extractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: im-wiki-extractor
Source: https://github.com/cafe3310/public-agent-skills/tree/main/skills_parked/im-wiki-extractor
Command: npx skills add https://github.com/cafe3310/public-agent-skills --skill im-wiki-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill transforms large, unstructured group chat histories into structured knowledge graphs, reducing the difficulty of preserving important discussions, expertise, and relationships.

Core Features & Use Cases

  • Incremental Knowledge Extraction: Processes long chat archives through sliding-window chunks to avoid context limits while maintaining continuity.
  • Graph-Based Organization: Extracts entities, opinions, information, discussions, and relationships with source traceability using a memories-off knowledge base.
  • Use Case: Convert a technical community chat archive into a searchable knowledge repository that captures participants' expertise, shared resources, and evolving ideas.

Quick Start

Use the im-wiki-extractor skill to process my group chat logs and build a traceable knowledge graph with extracted entities and relationships.

Frequently Asked Questions about im-wiki-extractor

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

FAQPage Schema
How do I turn unstructured chat logs into a knowledge graph?

To turn unstructured chat logs into a knowledge graph, the Skill processes conversation archives to extract traceable entities, opinions, and relationships using chunked processing and a memories-off knowledge base for source attribution.

What is the best way to extract entities from long technical community chat archives?

Extracting entities from long technical community chat archives requires incremental processing through sliding-window chunks. This approach avoids context limits while maintaining conversation continuity to capture shared expertise and evolving ideas.

How does incremental knowledge extraction handle context limits in large conversation histories?

Incremental knowledge extraction handles large conversation histories by applying sliding-window chunks. This bypasses context limits while maintaining continuity, ensuring reliable knowledge graph updates across extensive project discussions.

Does building a traceable knowledge graph from chat logs require memocli integration?

Yes, building a traceable knowledge graph from chat logs requires memocli integration. It pairs with automated task tracking and source attribution to maintain reliable updates for extracted entities and relationships.

Can I use this knowledge graph extraction approach for historical conversation archives?

Yes, you can use this approach for historical conversation archives. It applies chunked processing and source attribution to transform unstructured group chat histories into a searchable knowledge repository with traceable relationships.

What are the limitations of extracting relationships from project discussions using sliding-window chunks?

A limitation of using sliding-window chunks for relationship extraction is the potential loss of context across non-adjacent chunks. Automated task tracking and source attribution are required to maintain reliable knowledge graph updates.