القائمة
Cluster existing concepts and sources into a thematic topic page under wiki/topics/ so related knowledge is grouped and cross-referenced in the graph.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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-topic |
| description | Cluster existing concepts and sources into a thematic topic page under wiki/topics/ so related knowledge is grouped and cross-referenced in the graph. |
| allowed-tools | ["Bash","Read","Write"] |
You group already-ingested concepts and sources into a thematic topic page under
wiki/topics/. Topic pages are an organizing layer — they do not introduce new
knowledge; they surface relationships that already exist in the graph.
Read README.md first. Work only from wiki pages and graph edges that are
already in the workspace. Do not read raw/ source files and do not invent
entries that lack a wiki page. If the user wants to include something not yet
ingested, tell them to run /lumi-ingest first, then return here.
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/topics/<slug>.md already exists:node _lumina/scripts/wiki.mjs read-meta topics/<slug>
exit 2 (not found) — continue to step 3.
exit 0 (exists) — read the file, then show the user the title and
created date. Ask exactly one question with three options in the user's
language (no other action until answered). Explain the choices plainly:
Topic "<title>" already exists.
[s] skip — abort, no changes (default)
[r] refresh — propose a new candidate list and update the page; preserve `created` and `<!-- user-edited -->` sections
[a] abort — same as skip but log the user's intent
Map blank/Enter to skip. Do not proceed without an explicit choice.
node _lumina/scripts/wiki.mjs list-entities --type sources
node _lumina/scripts/wiki.mjs list-entities --type concepts
If the user named a seed concept that already exists as a concept page, also fetch its immediate neighbours (the topic title itself is never a seed slug — the topic page does not exist yet, so do not run read-edges against it):
node _lumina/scripts/wiki.mjs read-edges concepts/<seed-slug>
From the combined output, select 5-10 candidate sources and 5-10 candidate concepts most relevant to the topic. On a small wiki with fewer than 5 of either, propose all relevant ones — a shorter list is fine. Present them as a numbered list with a one-line reason for each. Group sources and concepts separately. Explain that the user can:
Do not write anything until the user explicitly approves the list.
Write wiki/topics/<slug>.md with valid topic frontmatter and the four
standard sections. Use today's date for both created and updated on a
new page; on a refresh keep the original created date.
Required frontmatter fields: id, title, type: topic, created,
updated, key_sources (array of source slugs the user approved).
Page structure:
---
id: <slug>
title: "<Topic Title>"
type: topic
created: YYYY-MM-DD
updated: YYYY-MM-DD
key_sources:
- sources/<slug>
- ...
---
## Description
<!-- A short paragraph explaining what this topic covers and why the grouped
sources and concepts belong together. Write in document_output_language. -->
## Key sources
<!-- One bullet per approved source: [[sources/<slug>]] — one sentence on why
it belongs here. -->
## Key concepts
<!-- One bullet per approved concept: [[concepts/<slug>]] — one sentence on
the concept's role in this topic. -->
## Open questions
<!-- Bullet list of unresolved questions, tensions, or gaps the topic surface.
Leave blank if none are obvious; the user can fill this in later. -->
Write edges for every approved source and concept. Call add-edge once for
the forward relationship from the topic page — the engine writes the
reverse edge automatically. For each approved source:
node _lumina/scripts/wiki.mjs add-edge topics/<slug> includes_source sources/<source-slug>
For each approved concept:
node _lumina/scripts/wiki.mjs add-edge topics/<slug> covers_concept concepts/<concept-slug>
node _lumina/scripts/wiki.mjs log research-topic "created topic <slug> covering <N> sources, <M> concepts"
On a refresh, write "refreshed topic <slug> ..." instead.
wiki/index.md and structural checks stay current:node _lumina/scripts/lint.mjs --fix --json
If summary.errors > 0, read the lint output, address each error, and re-run
before telling the user the skill is done.
/lumi-check in a fresh session or via a subagent after this run. A
blank context catches bias from the reasoning chain that just built the
topic page.raw/ files at any point. All information comes from already-ingested
wiki pages and graph edges./lumi-ingest first.created date and any
<!-- user-edited --> sections verbatim. Only updated, key_sources, and
non-marked sections may change.wiki/topics/<slug>.md exists with valid frontmatter (id, title,
type: topic, created, updated, key_sources containing at least one
entry) and all four standard sections (Description / Key sources / Key
concepts / Open questions).add-edge, with the reverse edge on each
source and concept page written automatically by the engine.node _lumina/scripts/lint.mjs --fix --json leaves summary.errors === 0.wiki/log.md has an append-only research-topic entry recording the
slug, source count, and concept count.wiki/log.md with the actual decision taken.