| name | llm-wiki |
| description | 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.
|
| metadata | {"author":"guanyang","version":"4.1","category":"knowledge-management"} |
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:
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.
- Read source file: Read the specified file from
raw/
- Extract key information: Identify entities, concepts, core arguments, data, conclusions
- Discuss key points with user: Report key findings, confirm focus areas
- 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/
- 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
- Maintain cross-references:
[[wikilinks]] between all related pages
- 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
- Update index.md: Add/update entries with confidence and status (format: see
index-spec)
- Update lifecycle.md (if exists): New pages get new rows; existing pages update access and last_accessed
- Record log (format: see
log-spec)
Verification
After completion, check:
query
Retrieve knowledge from wiki and synthesize answers to user questions.
- Read index.md: Locate relevant pages, prioritizing high confidence and active status
- Read relevant pages: Deep-read entities, concepts, summaries, etc.
- Freshness check: Core pages with confidence < 0.6 or stale → proactively search the web for latest information
- 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
- 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
- Provide citations: Reference specific wiki pages and original material sources in the answer; web-sourced information includes source links
- Offer archival: If the answer has reuse value → ask user whether to save to comparisons/ or synthesis/
- 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.
- 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)
- 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)
- 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
- Log archival:
python3 skills/llm-wiki/scripts/log-archive.py (run with --dry-run first to preview, then remove the flag to execute)
- Generate fix list: Consolidate script reports + semantic check results, execute fixes after user confirmation
- Record log
Verification
After fixes, re-run lint-check.py to confirm:
publish
Produce polished, audience-facing deliverables from wiki content.
- Clarify requirements: Confirm type (post/report/slides/tutorial/newsletter), audience, length
- Locate source material: Read index.md, prioritize high-confidence active pages
- Read sources: Deep-read relevant pages
- Generate draft: Write deliverable based on wiki content, save to appropriate
output/ subdirectory (format: see output-page-spec)
- Format adaptation:
[[wikilinks]] → standard links or plain text; citations use footnotes; adapt format by type (see output-page-spec)
- Update lifecycle (if lifecycle.md exists): Referenced pages → lifecycle.md access +1, last_accessed updated; index.md confidence +0.15
- User review: Present draft, revise based on feedback
- Record log
Verification
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.
- Identify target: Read the target page's current content and core conclusions
- Web search: Search for latest developments, version updates, and disruptive changes on the topic
- Diff assessment: Compare latest information with existing wiki content, identify significant additions or conflicts
- Request confirmation: Report findings to user, ask whether to persist as new raw material
- Execute update (after user confirmation): Save as
raw/articles/[date]-[topic].md, invoke ingest to update wiki
- Record log
