Skip to main content
Yanked

This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.2.1 instead.
Reason given by maintainers: version error

graph-wiki

A digital brain you grow with your AI agent.

It remembers what you figure out, connects it to what you already know,
and answers when you ask.

PyPI Ask DeepWiki PRs Welcome X

graph-wiki

English | 简体中文


You solve a hard problem on a Tuesday. Three months later, in a different repo, you solve it again from scratch — because the answer lived in a chat log you'll never find.

This fixes that. Point it at a folder, tell your agent what to remember, and it compiles what you learn into interconnected markdown you own. The pattern comes from Andrej Karpathy's LLM Wiki gist: compile knowledge once and keep it current, instead of asking an LLM the same questions forever or re-running RAG every time.

Your second brain. Your AI agent is how you grow it.

Every skill here is a markdown file that any agent — Claude Code, Cursor, Codex, Windsurf, Gemini CLI, and many more — reads and runs. Deterministic local helpers handle hashing and bounded text ranges; there is no hosted runtime, API key, or vendor lock-in.

60 seconds

pip install graph-wiki-skills
cd /path/to/your/project
graph-wiki setup --vault ~/brain

Setup installs skills only in the current project. Open that project in your agent and say "set up my wiki".

Prefer not to touch a terminal? Give your agent this and it'll do the whole thing:

https://github.com/wenxueliu/graph-wiki — set up my wiki

Other paths — git clone, Skills CLI, multiple vaults → Installation

What you actually do

Feed it. Local Markdown, plain-text, and reStructuredText documents are ingested through a resumable, context-bounded pipeline. Agent histories and web research use their dedicated skills.

/wiki-folder-ingest ~/research
/wiki-update                        # distill the repo you're standing in
/wiki-capture                       # save this conversation
/wiki-history-ingest claude         # mine everything you've ever asked Claude

Ask it. Answers come back with [[wikilink]] citations, not vibes.

/wiki-query what do I know about rate limiting?
/wiki-narrate MCP security          # a cited briefing on a topic
/wiki-digest week                   # what did I learn this week?

Find that session you can't name.

graph-wiki sessions-build
graph-wiki sessions-query "the auth bug with the weird retry loop"

Keep it honest. The vault gets messy on its own; these clean it.

/wiki-lint            # broken links, orphans, contradictions
/wiki-dedup           # "RSC" and "React Server Components" are one page now
/cross-linker         # weave new pages into the graph
/wiki-status          # what's ingested, what's pending, where the hubs are

All 50 skills → Skills Reference

See it

Open the vault in Obsidian and hit the graph view (Cmd/Ctrl+P → "Open graph view"). Say "color my graph" and it tints nodes by tag, category, or visibility.

graph-wiki graph view

Or export the whole graph to graph.json, GraphML (Gephi/yEd), Neo4j Cypher, or a self-contained interactive graph.html.

Why this and not a notes folder

  • It compiles, it doesn't accumulate. New knowledge merges into existing pages. Contradictions get flagged. Nothing gets duplicated.
  • It only reads what changed. A manifest tracks every source ingested, so the second run processes the delta — not your whole library again.
  • You can tell knowledge from guessing. Every claim is tagged extracted, ^[inferred], or ^[ambiguous], and lint flags pages drifting into speculation.
  • Queries stay cheap as it grows. Titles, tags, and summaries get read before page bodies. 20 pages or 2000, roughly the same cost.
  • It's yours. Plain markdown in a folder. Push it to a private repo, open it in Obsidian, grep it, delete it. No service, no lock-in, nothing leaves your machine.
  • Works where you already work. One bundled .skills/ directory, linked into each selected agent under your project.

More → Architecture

Documentation

These docs are available in English and Simplified Chinese.

Installation pip, clone, agent-driven setup, multiple vaults
Skills Reference All 50 skills and their slash commands
Agent Compatibility The full matrix + per-agent manual setup
CLI Reference Every graph-wiki subcommand
Configuration Config vars, QMD semantic search, _raw/ staging, GitHub sync
Architecture The four ingest stages, vault structure, what we added to Karpathy's pattern
Session Brain Topic graph over your agent session history
Contributing Adding skills, keeping the English and Chinese docs in sync

Contributing

This is early. The skills work, but there's room to make the brain smarter — better cross-referencing, sharper deduplication, bigger vaults, new ingest sources. If you have a workflow that could be a skill, PRs are welcome.

License

MIT

Metadata

Release files for graph-wiki-skills 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for graph-wiki-skills 0.1.0
File Size Uploaded Provenance
graph_wiki_skills-0.1.0.tar.gz 1.4 MB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for graph-wiki-skills 0.1.0
File Interpreter ABI Platform
graph_wiki_skills-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 2.1 MB

Release files / graph_wiki_skills-0.1.0.tar.gz

Download URL graph_wiki_skills-0.1.0.tar.gz
Size 1.4 MB
Tags Source
SHA-256 checksum
How to use checksums
6e572140ac478acf12bc3646229fddc09afd99cfa7790b50ae75765d33a7c61a
BLAKE2b-256 checksum
How to use checksums
4e6a4b2ea2ef0d4a74a97d78f04c70390908cb264c5594d57800a4b69594fb6f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Release files / graph_wiki_skills-0.1.0-py3-none-any.whl

Download URL graph_wiki_skills-0.1.0-py3-none-any.whl
Size 689.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8fccd1cc43cdd5bd167a1d6e87b56ab82f01deea9aa924ec5f65774f60beca60
BLAKE2b-256 checksum
How to use checksums
0d05ba60bc5962f02b5589991d88f066e6ecc03df7e2fc2954ba69752e353529
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Security for graph-wiki-skills 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page