graphify

Converts folders of code, docs, papers, and images into a clustered knowledge graph with HTML, JSON, and audit report outputs.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/unnxt30/skills --skill graphify-unnxt30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphify
Source: https://github.com/unnxt30/skills/tree/main/graphify
Command: npx skills add https://github.com/unnxt30/skills --skill graphify-unnxt30

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphifyy.

What problem does it solve? Understanding a large mixed corpus — a new codebase, a reading list of papers, or a personal notes folder — requires reading everything manually, and connections across files stay invisible. graphify turns any folder into a persistent, queryable knowledge graph with community detection and an honest audit trail showing which relationships were extracted versus inferred. ## Core Features & Use Cases - Multi-format extraction: Combines deterministic AST parsing for code with parallel LLM subagents for docs, papers, and images, plus Whisper transcription for video and audio files. - Community detection and analysis: Clusters the graph, identifies god nodes and surprising cross-document connections, and labels communities with plain-language names. - Multiple outputs: Generates interactive HTML, GraphRAG-ready JSON, GRAPH_REPORT.md, Obsidian vaults, wikis, GraphML, SVG, and Neo4j Cypher exports. - Query and audit: Supports BFS/DFS graph queries, shortest-path lookups, node explanations, and tags every edge as EXTRACTED, INFERRED, or AMBIGUOUS with confidence scores. - Use Case: Point it at an unfamiliar repository to get a navigable architecture graph with labeled communities before touching any code, or drop papers and notes into a folder to discover cross-document connections. ## Quick Start Run /graphify on the current directory to build a knowledge graph and open the generated graph.html report.

Frequently Asked Questions about graphify

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

FAQPage Schema
How do I build a knowledge graph from a codebase or folder of documents?

Run /graphify on the target path. It detects file types, extracts code structure via AST parsing, dispatches parallel subagents for docs and images, clusters the result into communities, and outputs interactive HTML plus GraphRAG-ready JSON.

What file types does graphify support for knowledge graph extraction?

graphify handles code files, Markdown and text docs, PDF papers, images, and video or audio files. Video and audio are transcribed with Whisper first, then treated as documents during semantic extraction.

Can I export a knowledge graph to Neo4j or Obsidian?

Yes. Use --neo4j to generate a Cypher import file or --neo4j-push to write directly to a running Neo4j instance. The --obsidian flag generates a vault with one note per node plus a canvas file for community layout.

How does graphify handle large folders with many files?

If a corpus exceeds 2 million words or 200 files, graphify shows the top subdirectories and asks which subfolder to process. Extraction results are cached, so incremental runs with --update only reprocess new or changed files.

Why does graphify mark some graph edges as INFERRED or AMBIGUOUS?

Every edge carries a confidence label: EXTRACTED for relationships explicit in the source, INFERRED for reasoned connections with a 0.4-0.9 confidence score, and AMBIGUOUS for uncertain ones. This audit trail separates found facts from model inference.

What are the limitations of graphify HTML visualization?

HTML visualization is skipped for graphs over 5000 nodes because they become unusable in a browser. For very large graphs, use the Obsidian vault export or query the graph.json output programmatically instead.