Skip to main content
skill CX Codex

wiki-viewer — Claude Code skill: one HTML file for your wiki

wiki-viewer writes a pro-workflow wiki out as a single HTML file with pages, sources, claims, a seed queue, a link graph and search. Useful for handing research state to someone else.

MIT ★ 2,966 updated 2026-09-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow
Open on GitHub

What wiki-viewer does

Point it at a pro-workflow wiki and it produces one .html file: a header with wiki metadata, a sidebar of pages grouped by page_type, the selected page with rendered markdown and citations, tables for sources and seeds, plus an SVG graph of cross-links. Search runs in the browser over titles, summaries and page text. Data comes from ~/.pro-workflow/data.db, so the wiki has to exist first.

Run node $SKILL_ROOT/scripts/render.js <slug>, adding --out <path> for a different destination or --theme dark|light for the theme. With no flags you get <wiki-root>/derived/viewer.html in dark. CSS, SVG and JavaScript are inline, and nothing loads from a CDN or a <script src=> tag, so the file works from disk or from a static host.

The output is a snapshot. Edit the wiki and you re-render by hand. The link graph is computed once and baked into SVG, search does substring and token matching with ranking left to SQLite, and markdown goes through a small parser in the file that skips raw HTML.

What it helps with

  • see what an auto-research run actually built
  • send a whole wiki to a teammate as one file
  • jump to a page by a word from its content
  • spot orphan pages in the cross-link graph
  • turn a pending seed into a prompt for the next run

Example prompts for the agent

  • Render the agent-memory wiki as an HTML viewer
  • Build the viewer for the incident wiki into viewer.html with the light theme
  • Show the seed queue and link graph for the agent-memory wiki

How to install wiki-viewer

1Plugin marketplace

/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow

This installs the whole pro-workflow plugin with all its skills

2Skills CLI (Vercel)

npx skills add rohitg00/pro-workflow --skill wiki-viewer -a claude-code

3Manually: put the files in place

~/.claude/skills/wiki-viewer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/wiki-viewer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about wiki-viewer

How do I install wiki-viewer in Claude Code?

From the marketplace: /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow.

What does wiki-viewer do?

It renders a pro-workflow wiki as one self-contained HTML file with markdown pages, sources, seeds, a link graph and in-page search.

Does the HTML file stay in sync with the wiki?

No. Every render is a snapshot, so you run render.js again after a batch of edits.

Source text

SKILL.md · MIT
---
name: wiki-viewer
description: Render a self-contained HTML viewer for a pro-workflow wiki. Pages, sources, claims, seed queue, page-link graph and full-text search all in one file. No external dependencies, no JS framework, S3-uploadable. Use when the user wants to browse a wiki visually, share its current state with someone, audit research progress, or hand off a knowledge base. Inspired by Thariq Shihipar's "Unreasonable Effectiveness of HTML" — favors information density and shareability over markdown-only outputs.
user-invocable: true
---

# Wiki Viewer

Single-file HTML view of a pro-workflow wiki. Reads `~/.pro-workflow/data.db`, dumps the wiki into one self-contained HTML document with in-browser search, link graph and a seed-queue panel.

## Why HTML, not markdown

- **Information density** — pages, sources, claims, seeds, link graph in one viewport
- **Visual clarity** — long wikis are unreadable as raw markdown; HTML scales
- **Shareability** — upload to S3, send the URL; recipient does not need pro-workflow installed
- **Two-way interaction** — "copy as seed" buttons turn open questions into seed queue prompts you can paste back into Claude Code
- **Auditable** — quick visual proof that the auto-research loop produced something useful

## When to use

- After a `/wiki research` run, to see what it built
- Before sharing a wiki with a teammate or with leadership
- Code review: render a `codebase`-flavored wiki for an unfamiliar module
- Incident review: render an `incident` wiki for a post-mortem readout
- Periodic audits: stale-claim detection, orphan-page review

## Commands

```
node $SKILL_ROOT/scripts/render.js <slug> [--out <path>] [--theme dark|light]
```

Defaults:

- output: `<wiki-root>/derived/viewer.html`
- theme: `dark`

## What ships in the file

| Panel | Contents |
|-------|----------|
| Header | wiki slug, flavor, scope, root path, last-update timestamp, page count, source count, kill-switch status |
| Sidebar | page list grouped by `page_type`, in-page filter input |
| Main | selected-page detail: title, summary, full markdown content (rendered), inline citations resolve to source rows |
| Sources | table of every `wiki_sources` row + manual `sources.md` rows |
| Seeds | seed-queue table grouped by status; "copy as research prompt" button per pending seed |
| Link graph | SVG force-layout of cross-page citations + back-links |
| Search | in-browser substring + token search over title/summary/content |
| Footer | meta: schema versions, embedding model if present, generator version |

## Self-contained

No CDN, no external fonts, no `<script src=>`. Inline CSS, inline SVG, inline JS only. Result is a single `.html` file that opens locally or from any static host.

## Compose with the rest

```bash
# Generate after auto-research run completes
/wiki research agent-memory --max-pages 5
node skills/wiki-viewer/scripts/render.js agent-memory
open ~/.pro-workflow/wikis/agent-memory/derived/viewer.html

# Hand off to a teammate
aws s3 cp ~/.pro-workflow/wikis/agent-memory/derived/viewer.html s3://my-bucket/agent-memory.html --acl public-read
```

## Design principles

1. **Type-first** — every panel reads as text; visualizations are auxiliary, not load-bearing.
2. **Zero decoration** — no gradients, no glow, no atmospheric backgrounds.
3. **Color is meaning** — Anthropic coral marks the active page and CTAs only.
4. **Print-friendly** — `@media print` collapses sidebars so the markdown content prints clean.

## Limits (initial release)

- Markdown rendering is a small in-file parser (headings, lists, code blocks, links, blockquotes, tables, footnote citations). No HTML-in-markdown.
- Link graph is precomputed and serialized as SVG; no live re-layout.
- Search is substring + tokenized AND match. BM25 stays in SQLite; the viewer is a snapshot.
- Re-render after each batch of changes. The file is not live.

## Future hooks (not in initial release)

- `--include-council` to bundle every linked council transcript inline
- `--include-survey` to bundle generated surveys
- "Copy as council prompt" buttons next to claims tagged `contested`
- Diff view: `--against <previous.html>` to highlight new claims since a prior render

© Rohit Ghumare · MIT · rohitg00/pro-workflow

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set83

The whole set →
deslop deslop trims unnecessary code from the current branch diff and checks SKILL.md files. Run it before committing or reviewing a skill for release. CX Codex +1 ★ 2,966repo stars wiki-builder wiki-builder is a Claude Code skill that creates a structured knowledge base from Markdown pages and an FTS5 index in SQLite. It persists between sessions and is queryable by the agent. CX Codex +1 ★ 2,966repo stars token-efficiency token-efficiency cuts conversational fluff, caps tool executions per task, and stops Claude Code from repeatedly editing working implementations. CX Codex +1 ★ 2,966repo stars wiki wiki is a Claude Code command that builds and maintains persistent research wikis. It stores markdown files, indexes them in SQLite FTS5, and retrieves context via BM25. CX Codex +1 ★ 2,966repo stars llm-council llm-council runs multi-model deliberation in three stages: parallel drafts, anonymous peer rankings, and final synthesis by a designated chairman. CX Codex +1 ★ 2,966repo stars design-engineering The design-engineering skill guides interface animation choices and UI reviews. Use it when refining a component, transition, modal, or other interactive state. CX Codex +1 ★ 2,966repo stars permission-tuner The permission-tuner skill reads permission prompts and auto mode denials from your session logs, then suggests permission rules and autoMode entries to reduce interruptions. CX Codex +1 ★ 2,966repo stars batch-orchestration batch-orchestration decomposes large codebase changes into independent units and runs parallel agents in isolated git worktrees. CX Codex +1 ★ 2,966repo stars

Project sponsors

Companies that keep this analytics open