lantern-rag-dollhouse

Consolidate fragmented local repositories and artifacts into a RAG-ready markdown knowledge base.

3|5|Updated May 26, 2026
One-click install
npx skills add https://github.com/alex-place/lantern-os --skill lantern-rag-dollhouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lantern-rag-dollhouse
Source: https://github.com/alex-place/lantern-os/tree/main/skills/lantern-rag-dollhouse
Command: npx skills add https://github.com/alex-place/lantern-os --skill lantern-rag-dollhouse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns scattered repos, reports, PDFs, images, and convergence notes into one controllable RAG dollhouse so you can find, audit, and reuse source material without relying on chat memory.

Core Features & Use Cases

  • Flat RAG consolidation: Merge approved local sources into a single markdown knowledge base with traceable paths and evidence labels.
  • Asset and reference intake: Organize literal PDFs, images, charts, and supporting notes into references and assets for on-demand retrieval.
  • Source-state governance: Separate local_inspected, github_metadata_only, external summaries, and held items so you do not overstate what exists or copy unsafe material.
  • Update and purge loops: Rebuild manifests, refresh the flat file, and age out re-derivable outputs while preserving source truth.
  • Use Case: A founder wants one printable, auditable memory spine for Lantern OS, plus a disciplined intake plan for new repos and media.

Quick Start

Use the lantern-rag-dollhouse skill to consolidate the approved local sources into the flat RAG file and update the asset manifest.

Frequently Asked Questions about lantern-rag-dollhouse

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

FAQPage Schema
How do I consolidate local repos and PDFs into a single RAG knowledge base?

Source-state governance separates local_inspected items from github_metadata_only entries and external summaries. This strict labeling preserves provenance and prevents the system from treating metadata-only repositories as fully cloned local material.

How do I update and purge outdated assets from a consolidated knowledge base?

Updating and purging outdated assets requires rebuilding manifests and refreshing the flat file. This process ages out re-derivable outputs while preserving source truth, keeping the knowledge base current without losing original provenance or held items.

What is the best way to track provenance when merging local repositories into a RAG knowledge base?

Tracking provenance when merging local repositories requires strict source-state labeling and boundary checks. This Skill preserves provenance by applying reference refreshes and manifest rebuilding, ensuring source truth is maintained without overstating what exists.

What limitations exist when consolidating external summaries with local repositories for RAG?

A key limitation when consolidating external summaries with local repositories is the risk of overstating existing material. The Skill applies boundary checks and separates external summaries from local_inspected items to preserve provenance and avoid copying unsafe material.