init-raglisted

rag plugin initial setup (configure · start) — auto-creates the `.noory/rag/` directory, the `raw/` material store, `settings.json`, and the project `.gitignore`. A setup task that does not erase existing data. Example utterances "rag setup", "start rag", "rag config", "init-rag", "set up rag", "attach rag to the project". (For the initialization/reset that erases the index, use `rag-clear`.)
noory-code/noory-ai · ★ 0 · AI & Automation · score 75

Install: claude install-skill noory-code/noory-ai

# init-rag — rag initial setup > Before executing this workflow, read and apply `../HOST_CONTRACT.md`. ## What Creates a RAG index workspace (`.noory/rag/`) at the root of the project you are currently working on, and writes the default folder where the user will place material (`.noory/rag/raw/`) and the indexing policy (`settings.json`). If it is already set up, it says so and exits. > The MCP server resolves the project root through the shared host contract. Behavior is identical on macOS, Linux, and Windows. ## Steps 1. **Status check**: call the MCP tool `rag_get_settings`. - On a normal response, print "Already initialized. Current settings: …" and exit (then guide to `/rag:rag-status`). - On a `settings not found` error, proceed to the next step. 2. **Source-candidate scan**: from the project root, glob for the following candidates and present only the ones that exist to the user. - `docs/`, `documentation/`, `notes/`, `wiki/`, `README.md`, `CHANGELOG.md`, `ARCHITECTURE.md` - If any are found, use the host question tool to choose among `[candidates to add (multiSelect), use only .noory/rag/raw/]`. 3. **Write settings**: call `rag_set_settings`. Default payload: ```json { "sources": [ { "path": ".noory/rag/raw/", "recursive": true, "include": ["**/*.md", "**/*.mdx", "**/*.txt", "**/*.pdf", "**/*.png", "**/*.jpg", "**/*.jpeg", "**/*.gif", "**/*.webp"] } ], "embedding": { "provider": "local", "m