llm-wiki-newsroom
Reduces knowledge decay and fragmentation by automating wiki maintenance and cross-linking while keeping review separate from creation.
Harness engineering applied to knowledge production: a self-evolving multi-agent newsroom that turns your documents into a cross-linked markdown wiki. A "reground" loop pulls published pages back in before they go stale — writer ≠ reviewer, local-first, a structured alternative to RAG.
- Generate a searchable wiki from scattered internal documentation and technical guides automatically.
- Ask Claude to review and cross-link existing pages to prevent outdated information from spreading.
- Automate periodic fact-checking of published wiki pages against source documents to catch drift.
Reduces knowledge decay and fragmentation by automating wiki maintenance and cross-linking while keeping review separate from creation. Structured approach mitigates hallucination risk compared to standard RAG pipelines.
Technical writing teams and documentation leads managing large, interconnected knowledge bases that need continuous freshness without manual curation overhead.
https://github.com/alfadur7/llm-wiki-newsroom
By alfadur7
How to Get It
claude plugins install alfadur7/llm-wiki-newsroom
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me generate a searchable wiki from scattered internal documentation and technical guides automatically
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 166 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 166 GitHub stars; contributors unknown; last commit 0d ago; license MIT.