llm-wiki

Manages durable project knowledge through wiki context lookup and controlled docs/wiki updates.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/vovanostm-public/multica --skill llm-wiki-vovanostm-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: llm-wiki
Source: https://github.com/vovanostm-public/multica/tree/main/workflow-bundles/multica-specops-v5/codex_skills/.agents/skills/llm-wiki
Command: npx skills add https://github.com/vovanostm-public/multica --skill llm-wiki-vovanostm-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose durable project knowledge when decisions and architecture facts live only in chat logs or issue threads. This Skill keeps a canonical docs/wiki as the source of truth, letting agents look up verified context and propose controlled wiki updates without inventing facts. ## Core Features & Use Cases - Wiki Context Lookup: Selects relevant wiki pages with reasons and freshness, verifying Basic Memory search results against the canonical docs/wiki before use. - Controlled Update Plans: Produces a wiki.update_plan before any edit, ensuring only the Wiki Curator mutates canonical pages and that lint checks run after mutation. - Contradiction and Secret Handling: Flags conflicts between wiki and evidence for owner review, and blocks potential secrets pending Security Reviewer approval. - Use Case: During a multi-stage workflow, an agent needs architecture context. The Skill returns typed context.wiki evidence with used_evidence, assumptions, blockers, and confidence instead of broad prose. ## Quick Start Ask the agent to look up the relevant wiki context for the current task and prepare a wiki update plan if any durable knowledge is missing.

Frequently Asked Questions about llm-wiki

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I look up project wiki context in an agent workflow?▼

Use StageContextPackage.wiki_context when present, then discover pages through Basic Memory search while verifying durable claims against the canonical docs/wiki. The Skill outputs context.wiki with selected pages, reasons, and freshness.

How do I update project wiki documentation safely?▼

Prepare a wiki.update_plan before editing anything. Only the Wiki Curator role mutates canonical docs/wiki pages, and a wiki lint script runs after every mutation to validate index, log, and schema consistency.

What is the difference between Basic Memory and docs/wiki?▼

docs/wiki is the canonical source of truth for durable project knowledge. Basic Memory is only an access, search, and graph layer; its projections must never be treated as authoritative without verification against docs/wiki.

What happens when wiki content conflicts with workflow evidence?▼

The contradiction is marked and routed to the owner for review rather than silently resolved. The Skill never invents durable facts when no relevant wiki page exists; it records the missing knowledge instead.

When should information not be added to the project wiki?▼

One-off debug noise stays in issue evidence rather than the wiki, and anything resembling a secret is blocked pending Security Reviewer approval. Only durable architecture or policy knowledge warrants a page or ADR update.