# LLM Wiki

> Use this skill when the user wants to digest notes or articles into a structured wiki, ask questions answered from compiled knowledge, check wiki health, produce polished deliverables (blog posts, reports, slides), or verify whether wiki content is still up-to-date. Activate even if the user doesn't say "wiki" — phrases like "organize this", "digest this article", "look this up for me", "write a blog post", "check the knowledge base" all qualify.

- Skill: `guanyang/llm-wiki` (Agent Skill, multi-file: 11 files)
- Install (CLI): `npx skillmds@latest add guanyang/llm-wiki`
- Raw SKILL.md: https://api.skillmd.com/api/skills/guanyang/llm-wiki/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: guanyang (https://skillmd.com/u/guanyang)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/guanyang/llm-wiki

---


# LLM Wiki

## Usage

| Subcommand | Usage | When to Use |
|--------|------|---------|
| `ingest` | `/llm-wiki ingest <raw/path/filename>` | User provides new material to digest |
| `query` | `/llm-wiki query <question>` | User asks a question to be answered from wiki |
| `lint` | `/llm-wiki lint` | User requests a wiki health check |
| `publish` | `/llm-wiki publish <type> [topic]` | User requests polished output |
| `refresh` | `/llm-wiki refresh <topic>` | Re-verify a specific topic via web search |

Types: `post` | `report` | `slides` | `tutorial` | `newsletter`

## References (Load on Demand)

Do not pre-load. Only load when the corresponding trigger condition is met:

| Document | Trigger Condition |
|------|---------|
| [references/wiki-page-spec.md](references/wiki-page-spec.md) | When creating a new wiki page — need frontmatter format |
| [references/output-page-spec.md](references/output-page-spec.md) | When generating polished output — need output format and directory conventions |
| [references/tags-spec.md](references/tags-spec.md) | When tagging a page — unsure which tags are available |
| [references/naming-spec.md](references/naming-spec.md) | When naming a new page — unsure of naming rules |
| [references/index-spec.md](references/index-spec.md) | When updating index.md for the first time — need to confirm table format |
| [references/log-spec.md](references/log-spec.md) | When writing a log for the first time — need to confirm record format |
| [references/lifecycle-spec.md](references/lifecycle-spec.md) | When encountering confidence anomalies, needing to understand decay formulas, or handling supersession/demotion |

## Gotchas

- **Never modify any file in `raw/`**. Raw is the immutable source of truth. Newly fetched web information must also be saved as new files.
- **lifecycle.md is pluggable**. All lifecycle steps are conditional on "if lifecycle.md exists" — skip if it doesn't.
- **index.md uses table format** — each row contains confidence and status columns, not list format.
- **Deliverables must be standalone readable**. Publish output must not contain `[[wikilinks]]` — convert to standard links or plain text.
- **A single ingest may update 10–15 pages** — this is normal. Don't hesitate because of many changes.
- **Stale pages can be referenced but must be annotated**. When a query references a stale page, note "this information may be outdated" in the answer.
- **refresh must wait for user confirmation** before persisting web-fetched information into raw.

---

## ingest

Read source files from `raw/`, extract knowledge, create/update wiki pages.

1. **Read source file**: Read the specified file from `raw/`
2. **Extract key information**: Identify entities, concepts, core arguments, data, conclusions
3. **Discuss key points with user**: Report key findings, confirm focus areas
4. **Create/update wiki pages** (format: see `wiki-page-spec`; tags: see `tags-spec`; naming: see `naming-spec`):
   - Summary page → `wiki/summaries/`
   - Entity page → `wiki/entities/`
   - Concept page → `wiki/concepts/`
5. **Handle contradictions**: New material contradicts existing content → explicitly annotate in the page, citing both old and new sources; if lifecycle.md exists, contradiction page confidence −0.15
6. **Maintain cross-references**: `[[wikilinks]]` between all related pages
7. **Lifecycle assessment** (if lifecycle.md exists):
   - New page: set initial confidence (thin 0.55 / substantial 0.65 / multi-source 0.75 / synthesis 0.80)
   - Existing page confirmed by new source: confidence +0.10
   - Check promotion: entity/concept in summary mentioned by 2+ materials → create entity/concept
   - Check supersession: core conclusion overturned → old page superseded_by → new page, status → archived, add supersession notice to body
8. **Update index.md**: Add/update entries with confidence and status (format: see `index-spec`)
9. **Update lifecycle.md** (if exists): New pages get new rows; existing pages update access and last_accessed
10. **Record log** (format: see `log-spec`)

### Verification

After completion, check:
- [ ] All new pages have complete frontmatter
- [ ] All `[[wikilinks]]` point to existing pages
- [ ] index.md page count is updated
- [ ] log.md has a new entry appended

---

## query

Retrieve knowledge from wiki and synthesize answers to user questions.

1. **Read index.md**: Locate relevant pages, prioritizing high confidence and active status
2. **Read relevant pages**: Deep-read entities, concepts, summaries, etc.
3. **Freshness check**: Core pages with confidence < 0.6 or stale → proactively search the web for latest information
4. **Synthesize answer**: Answer based on wiki + web information. If significant new findings or conflicts are discovered → ask user whether to persist as new raw material
5. **Update lifecycle** (if lifecycle.md exists): Hit pages → lifecycle.md access +1, last_accessed updated; index.md confidence +0.05. Do not modify the queried pages themselves
6. **Provide citations**: Reference specific wiki pages and original material sources in the answer; web-sourced information includes source links
7. **Offer archival**: If the answer has reuse value → ask user whether to save to comparisons/ or synthesis/
8. **Record log**

> When wiki information is insufficient, you may refer back to `raw/` for supplementation, and update the wiki accordingly.

---

## lint

Check wiki health and fix issues.

1. **Run structural check script**: `python3 skills/llm-wiki/scripts/lint-check.py`, outputs a JSON report containing:
   - Page count verification (actual vs declared)
   - Orphan page list (no incoming links)
   - Missing page list (referenced but not created)
   - Missing frontmatter fields
   - One-way link list (A→B but B↛A)
2. **Run lifecycle check script** (if lifecycle.md exists): `python3 skills/llm-wiki/scripts/lifecycle-check.py`, outputs a JSON report containing:
   - Time decay suggestions (base decay × type coefficient = actual decay, with current/suggested confidence)
   - State transition suggestions (which pages should move from active → stale or stale → archived)
3. **LLM semantic check** (based on script reports + page content):
   - Contradiction detection: Contradictory claims between pages
   - One-way link evaluation: Assess each one-way link for semantic relevance to determine if back-reference is needed
   - Demotion assessment: Whether synthesis/comparison core conclusions have been disproven by new material → set status to stale, confidence −0.15, add warning to body
   - Promotion suggestions: Pages meeting promotion criteria but not yet promoted
   - Staleness probing: High-frequency topics in stale pages → suggest user execute `refresh` (wait for confirmation)
   - Lint pass reward: Pages with no contradictions get confidence +0.02
4. **Log archival**: `python3 skills/llm-wiki/scripts/log-archive.py` (run with `--dry-run` first to preview, then remove the flag to execute)
5. **Generate fix list**: Consolidate script reports + semantic check results, execute fixes after user confirmation
6. **Record log**

### Verification

After fixes, re-run `lint-check.py` to confirm:
- [ ] All confirmed items in the issue list are fixed
- [ ] No new broken links
- [ ] index.md page count is accurate

---

## publish

Produce polished, audience-facing deliverables from wiki content.

1. **Clarify requirements**: Confirm type (post/report/slides/tutorial/newsletter), audience, length
2. **Locate source material**: Read index.md, prioritize high-confidence active pages
3. **Read sources**: Deep-read relevant pages
4. **Generate draft**: Write deliverable based on wiki content, save to appropriate `output/` subdirectory (format: see `output-page-spec`)
5. **Format adaptation**: `[[wikilinks]]` → standard links or plain text; citations use footnotes; adapt format by type (see `output-page-spec`)
6. **Update lifecycle** (if lifecycle.md exists): Referenced pages → lifecycle.md access +1, last_accessed updated; index.md confidence +0.15
7. **User review**: Present draft, revise based on feedback
8. **Record log**

### Verification

- [ ] Deliverable contains no `[[wikilinks]]`
- [ ] Deliverable page frontmatter is complete
- [ ] Source citations presented as footnotes or bibliography

> When synthesis confidence ≥ 0.85, proactively suggest publishing. For briefing types, semi-automation is possible: read recent log.md entries and summarize.

---

## refresh

Re-verify a specific topic via web search and update wiki if needed.

1. **Identify target**: Read the target page's current content and core conclusions
2. **Web search**: Search for latest developments, version updates, and disruptive changes on the topic
3. **Diff assessment**: Compare latest information with existing wiki content, identify significant additions or conflicts
4. **Request confirmation**: Report findings to user, ask whether to persist as new raw material
5. **Execute update** (after user confirmation): Save as `raw/articles/[date]-[topic].md`, invoke ingest to update wiki
6. **Record log**