agentsclimarketplace
Sign in

Wiki graph

Skill galaxyuliana/wiki-graph/skills/wiki-graph

Render a markdown wiki, docs repo, or notes vault as an interactive knowledge graph — an Obsidian-style force view (self-contained HTML) plus an agent-readable graph.json. Use whenever the user invokes /wiki-graph, asks to see, refresh, watch, or schedule the knowledge graph, wants the wiki or docs visualized, or asks about hubs, orphans, broken links, or clusters in a docs repo. Works on any folder of markdown files; no dependencies beyond Python 3.From its SKILL.md

Install
npx -y skills add galaxyuliana/wiki-graph --skill wiki-graph

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.2 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

wiki-graph

Build the graph of the repo the user is working in and show it. Every node is a markdown file (frontmatter type/status/tags drive color, filters, and search); every edge is a real markdown link — both [text](path.md) and Obsidian [[wikilinks]].

All commands below use <skill-dir> for this skill's base directory (stated when the skill loads).

Default flow (manual build)

  1. ROOT = git rev-parse --show-toplevel (not a git repo → use the cwd).
  2. Pick the builder:
    • Repo vendors its own copy at <ROOT>/tools/wiki-graph/build.py: run that one — teams pin the builder in-repo for reproducibility.
    • Otherwise run the bundled copy: python3 "<skill-dir>/scripts/build.py" "$ROOT". Outputs land in $ROOT/.wiki-graph/ (override with a second positional arg if the user wants them elsewhere).
  3. Open wiki-graph.html from there (open on macOS, xdg-open on Linux, start on Windows) and relay the doc/link/orphan counts the script printed.
  4. Git stays clean automatically — .wiki-graph/ writes its own .gitignore. If the user wants the graph committed/shared, that's git add -f .wiki-graph.
  5. First build in a repo? Offer two one-time upgrades (do them only if the user agrees):
    • Append the knowledge-graph block to the repo's AGENTS.md (create the file if missing) so every coding agent — Codex, Cursor, Gemini CLI, Copilot, etc. — keeps the graph fresh and reads graph.json when asked about the docs. Template: integrations/AGENTS.md-snippet.md in this plugin's repo; adapt the builder path to this machine (use the vendored path if the repo has one, else this skill's scripts path).
    • Vendor the builder into the repo (cp -r <skill-dir>/scripts <ROOT>/tools/wiki-graph) if the team wants a version-pinned copy that works without this plugin installed.

Live mode (auto-updating)

  • In Claude Code with the plugin installed, a PostToolUse hook already rebuilds .wiki-graph/ after every markdown edit — building once (step above) is all it takes to turn that on for a repo.
  • When the user says live / watch / serve, run python3 "<skill-dir>/scripts/build.py" "$ROOT" --serve in the background, then tell them the URL it printed (default http://127.0.0.1:7177/wiki-graph.html). The open page polls graph.json and morphs in place — new docs flash into the web as they are written. Stop it when they ask (kill the background job).

Scheduled mode

When the user wants the graph rebuilt on a schedule (e.g. nightly):

  • Preferred, if your environment has a scheduler (Claude Code cron, CI cron): schedule python3 "<skill-dir>/scripts/build.py" "<ROOT>" --quiet.
  • Plain OS fallback — offer this crontab line (adjust paths): 0 7 * * * python3 <skill-dir>/scripts/build.py <ROOT> --quiet
  • For a public, always-fresh graph of a GitHub repo, point them at integrations/github-pages.yml in this plugin's repository — it publishes the graph to GitHub Pages on every push and on a daily cron.

Answering questions about the graph

Read $ROOT/.wiki-graph/graph.json (rebuild first if stale): nodes carry type, status, tags, in, out — in + out == 0 → orphan; high in → hub. edges are [from, to] doc paths. broken lists [source, target] links that point at missing files — offer to fix those when asked. --check exits 1 when broken links exist (useful in CI).

Notes

  • Optional per-repo config ROOT/.wiki-graph.json: {"title": "My Wiki", "roots": ["docs"], "ignore": ["vendor"]}.
  • Stdlib-only, ~1s on a 400-doc wiki; dot-dirs and node_modules are skipped.
  • Timeline replay appears automatically when git history (or frontmatter dates) span more than one day.

What ships with it: 2 files

52.0 KB alongside SKILL.md, 1 of them executable

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.