Menu
Seed terminal foundation pages for stable background knowledge so future ingestion can link to common concepts without duplicating definitions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run lint.mjs --json, summarize findings by severity, offer to apply --fix for auto-fixable checks (L01/L03/L06/L07/L09), self-check re-run to confirm 0 errors, and surface advisory warnings for user attention. Use this whenever the user asks to "check the wiki", "run lint", "verify the graph", "are there broken links?", "what's wrong with the wiki?", "health check", or "are there missing reverse links?". Also fires for: weekly review requests, before committing wiki changes, after a bulk ingest session, or any time the user wants to know the structural state of the wiki.
Guided wiki page authoring and refactoring: apply user-directed edits to a wiki page with schema validation and bidirectional-edge integrity preserved. Use this whenever the user asks to update, fix, revise, rewrite, correct, or clean up a wiki page — even if they don't say "edit". Also fires for: "fix the reverse link on X", "update the summary for Y", "set importance to 4 on Z", "the lint check found a missing link in ...", or any request that modifies one wiki page without ingesting a new source.
Turn a raw source file into structured wiki pages: source page, concept and person stubs, wiki.mjs-managed graph edges, citation edges, and a log entry. Pauses at four checkpoints (draft, lint, verify, finalize) so you can review before the work is committed to the wiki — accept, revise, or quit at any checkpoint without losing progress. Resumable across sessions. Use this whenever the user says "ingest", "add", "file", "process", "summarize into the wiki", "create a wiki page for", or drops a filename from raw/sources/. Also fires for: "I added a PDF to raw/sources/", "add this paper to the wiki", "parse this article", "what should I do with raw/sources/X?", or any request to bring a new source into the wiki graph. Also accepts Mode B input — paper title, arxiv ID, or URL, without a local file path. Examples: "ingest paper 2604.03501v2", "ingest arxiv:2604.03501", "ingest https://arxiv.org/abs/2604.03501". The skill fetches the PDF automatically in that case. Also handles whole books, theses, and other 50+ p
Check that wiki notes match the sources they cite. Flags statements that appear in a wiki page but are not supported by the cited material, statements that contradict other parts of the same page, and (with --external) statements contradicted by current web search results. Reports findings for the user to review; never edits notes automatically. Run on one page (`/lumi-verify <slug>`), the whole wiki (`/lumi-verify --all`), or only recently-changed pages (`--since <date>`). Use after AI adds new wiki pages, before sharing or exporting the wiki, or as a periodic health check on older pages. Trigger on phrases like "verify", "fact-check the wiki", "is this page accurate?", "check sources", "retro verify". Operates on sources/* pages in v0.9; other page types are skipped.
Ingest one book chapter into the wiki and extract character mentions, theme tags, and plot beats into the graph. Use whenever the user wants to ingest, file, or process a chapter — including phrasings like "I just finished chapter 3", "add this chapter to the wiki", "file chapter 2 of [book]", or "track what happened in chapter 5".
Answer questions from what the wiki already knows, citing the wiki pages behind every claim so the user can open and verify them. Reads only — never changes the wiki unless the user explicitly asks to save the answer as a page. Use this whenever the user asks a question whose answer should come from the wiki — even if they don't say "ask". Also fires for: "what does the wiki say about X", "compare X and Y from what we've ingested", "summarize the wiki's coverage of X", "what concepts relate to Y", "find all sources that mention Z", "what have we learned about X", or any synthesis or retrieval request over accumulated wiki content. If a question could be answered from raw/ but isn't in the wiki yet, surface the gap, list the matching raw/ files so the user can open them directly, and suggest /lumi-ingest instead of reading raw/.
| name | lumi-research-prefill |
| description | Seed terminal foundation pages for stable background knowledge so future ingestion can link to common concepts without duplicating definitions. |
| allowed-tools | ["Bash","Read","Write"] |
You create stable foundation pages under wiki/foundations/ for background
concepts. Foundation pages are terminal references: normal wiki pages may link to
them, but they do not require reverse links.
Read README.md first. Use the research pack Wikipedia fetcher when background
material should come from a public encyclopedia:
python3 _lumina/tools/fetch_wikipedia.py --help
node _lumina/scripts/wiki.mjs read-meta foundations/<slug>
When speaking with the user, follow the README language rule exactly. Use the configured communication language, translate workflow terms, and avoid technical tool words unless the user asks for them.
node _lumina/scripts/wiki.mjs slug "<topic title>"
wiki/foundations/<slug>.md already exists:node _lumina/scripts/wiki.mjs read-meta foundations/<slug>
exit 2 (not found) — continue to step 3.
exit 0 (exists) — read the file, then show the user the title, created
date, and the most recent line in wiki/log.md that references this slug.
Ask exactly one question with three options in the user's language (no other
action until answered). Do not expose internal terms; explain the choice as
"leave it unchanged", "refresh the public background text", or "stop and log
the decision":
Foundation "<title>" already exists.
[s] skip — abort, no changes (default)
[r] refresh — re-fetch from Wikipedia, update non-marked sections and `updated`; preserve `created`, `aliases`, and `<!-- user-edited -->` sections
[a] abort — same as skip but log the user's intent
Do not proceed without an explicit choice. Map blank/Enter to skip.
python3 _lumina/tools/fetch_wikipedia.py page "<title>"
exit 0 — use the JSON output directly.
exit 2 AND stderr is JSON with kind == "disambiguation" — run a search
to surface candidates:
python3 _lumina/tools/fetch_wikipedia.py search "<title>" --limit 5
Present the numbered results (title + snippet) in the user's language and let the user:
manual to paste content directly.Re-run page with the chosen title, or accept the user-pasted content.
exit 2 for any other reason (empty title, page not found) — surface the
error field from stderr JSON and abort.
exit 3 (network error) — tell the user and offer two options: retry, or paste content manually.
Write wiki/foundations/<slug>.md with valid foundation frontmatter:
id, title, type: foundation, created, updated.
Also include the optional aliases field — an array of strings listing
alternative names users or sources might write for this concept (abbreviations,
expansions, common misspellings). Example: for a foundation titled "Reinforcement
Learning from Human Feedback", use aliases: ["RLHF", "human feedback RL"].
Propose a list of 2–5 plausible alternate names, then ask the user to confirm
or edit before writing. An empty list is fine if nothing obvious applies.
Alternate names must be unique across all foundations — lint.mjs L10 will
error on collisions.
Foundation pages do not carry provenance or confidence frontmatter fields
(those belong on source pages). When the user later ingests a source that
references this foundation material, /lumi-ingest will set those fields on the
source page. To help that decision, note in the log entry whether the fetch was
replayable (Wikipedia snapshot saved to raw/), partial (summary only), or
missing (no fetch — manual entry). This keeps the audit trail clear without
polluting foundation frontmatter.
Example log note: prefilled foundation reinforcement-learning (provenance: replayable — Wikipedia snapshot saved)
Keep the body concise: definition, scope notes, and external references.
Log the addition:
node _lumina/scripts/wiki.mjs log research-prefill "prefilled foundation <slug>"
wiki/index.md and structural checks stay current:node _lumina/scripts/lint.mjs --fix --json
/lumi-check in a fresh session or via a subagent after this run.
A blank context catches bias from the reasoning chain that just wrote the
foundation page./lumi-ingest for wiki
knowledge extracted from project sources.created date and
any <!-- user-edited --> sections verbatim. Only updated and non-marked
sections may change.lint.mjs --fix --json reports
L10-alias-conflict, resolve manually before completing the run — there is no
automatic fix.node _lumina/scripts/lint.mjs --fix --json has updated wiki/index.md if
needed and leaves summary.errors === 0.wiki/log.md has an append-only research-prefill entry.wiki/log.md with the actual decision taken.