wiki-view
Skill50 starsChanged 7 months agoMITView on GitHub
Wiki dashboard — browse pages, view stats, knowledge graph, export. Use on: 'wiki dashboard', 'wiki stats', 'show wiki', 'wiki pages', 'list wiki', 'wiki graph', 'export wiki', 'wiki overview'.
In this repository4 other files it gives its agents.
- wiki-maintainSkill
- wiki-readSkill
- wiki-serveSkill
- wiki-writeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Read .wiki/index.md, .wiki/log.md, .wiki/overview.md:
- Very specific: line 34
Read all pages, extract [[wiki-links]] and related: fields:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wiki View
Dashboard, graph visualization, stats, and export for the wiki.
Resolve .wiki/ from plugin install scope. If not found, say "No wiki found."
Arguments
/wiki-view— dashboard summary (page count, recent activity, top topics)/wiki-view pages— list all pages grouped by type/wiki-view stats— detailed statistics (page count, links, confidence distribution, stale %)/wiki-view graph— knowledge graph visualization (Mermaid diagram)/wiki-view graph <slug>— graph centered on a specific page (2-hop neighborhood)/wiki-view export html— export entire wiki as single HTML file/wiki-view export md— export as single markdown bundle/wiki-view export json— export as JSON knowledge graph (nodes + edges)/wiki-view artifacts <type>— generate study guide, timeline, glossary, or comparison table
Dashboard
Read .wiki/index.md, .wiki/log.md, .wiki/overview.md:
- Page count and breakdown by type
- Last 5 activity log entries
- Current open questions from overview.md
- Confidence distribution (high/medium/low)
Graph
Read all pages, extract [[wiki-links]] and related: fields:
- Generate Mermaid flowchart showing page connections
- Color by type (concept=blue, entity=green, source=gray, idea=yellow)
- Highlight orphans (no incoming links) in red
- For
--slug: show only 2-hop neighborhood of that page
Export
- HTML: Render all pages through markdown → styled single HTML document
- Markdown: Concatenate all pages with
---separators - JSON:
{"nodes": [...], "edges": [...]}knowledge graph format
Artifacts
Generate derivative documents from wiki content:
/wiki-view artifacts study-guide <topic>— structured study guide from topic cluster/wiki-view artifacts timeline <topic>— chronological timeline of events/developments/wiki-view artifacts glossary— terms and definitions from all pages/wiki-view artifacts compare <slug1> <slug2>— side-by-side comparison table
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.