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.
SkillScore82Maintained
Automatic
◆Knowledge Management pack
Last verified 8/13/2026
What it changes
Passed 16 of 20 test cases with the skill, and 5 of 20 without it.
Without skill27%
With skill82%
Checks it passed that the model alone missed
Specifies that dark theme is used by default
Identifies ~/.pro-workflow/data.db as the source database
States that pages in the sidebar are grouped by page_type
and 9 more in the full report
12 fixed6 passed either way4 still failing0 broke
Pass-rate lift
+55 pp
Tokens
+2%
Agent turns
0%
Response time
-51%
Model gemini-3.6-flashMeasured 8/13/2026v118 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
Which specific technical schema and tool versions are listed in the footer panel of the rendered output?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies schema versions, generator version, or optional embedding model details
Missed
Passed
case-18 · gemini-3.6-flash · 8/13/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md80 lines2 filesincludes scripts
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