wiki-pipeline

Export NetworkX or Neo4j graph entities into Markdown wiki pages with wiki-links.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill wiki-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-pipeline
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/.claude/skills/wiki-pipeline
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill wiki-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns graph-backed PDF knowledge into structured wiki pages, making it easy to publish, synchronize, and maintain entity documentation without manual copy-paste.

Core Features & Use Cases

  • Graph to Wiki Export: Converts NetworkX or Neo4j entities into Markdown wiki pages with internal wiki-links.
  • Incremental and Reverse Sync: Keeps wiki pages and the source graph aligned through event-driven updates and change detection.
  • Search Indexing: Re-indexes exported wiki content with hybrid search for fast retrieval and discovery.
  • Use Case: A team can export extracted PDF entities into a documentation vault, keep drafts updated as the graph changes, and push approved wiki edits back into the knowledge graph.

Quick Start

Ask the wiki-pipeline skill to export the current graph into markdown wiki pages and keep the wiki synchronized with incremental updates.

Frequently Asked Questions about wiki-pipeline

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

FAQPage Schema
How do I export graph entities into structured wiki pages?

To export graph entities into structured wiki pages, use this Skill to convert NetworkX or Neo4j data into Markdown with deterministic export, automatic wiki-link generation, and idempotent updates for consistent documentation.

What is reverse sync from edited markdown back to a knowledge graph?

Reverse sync from edited markdown captures changes made to exported wiki pages and pushes approved edits back into the source knowledge graph, keeping graph entities and wiki documentation aligned through change detection.

How do I keep wiki pages synchronized with source graph data incrementally?

Keep wiki pages synchronized with source graph data through event-driven incremental forward sync, which detects graph changes and applies idempotent updates to existing markdown pages without full re-export.

Does this wiki export approach work with Neo4j and NetworkX graphs?

Yes, this wiki export approach works with both Neo4j and NetworkX graphs, converting entities into Markdown pages while running consistency checks between the wiki content and the underlying graph structure.

How does hybrid search indexing work for exported wiki content?

Hybrid search indexing for exported wiki content re-indexes Markdown pages during the export process, enabling fast retrieval and discovery of entity documentation across the synchronized wiki vault.

What are the limitations of syncing markdown wiki pages with a knowledge graph?

Limitations of syncing markdown wiki pages include the requirement for deterministic export to maintain consistency, meaning non-deterministic graph structures or unsupported entity formats may fail idempotent update checks and block synchronization.