manage

Manage

Single-document CRUD against the gnosis-mcp knowledge base. Bulk operations (full re-ingest, git history, web crawl, prune) live in /gnosis:ingest — this skill is for point changes.

All write operations require GNOSIS_MCP_WRITABLE=true on the server process. If the server refuses, it returns a structured error — relay that to the user rather than swallowing it.

Usage

/gnosis:manage add path/to/doc.md                   # Index a single document
/gnosis:manage delete path/to/doc.md                # Remove one document
/gnosis:manage update path/to/doc.md --tags api,auth  # Patch metadata
/gnosis:manage related path/to/doc.md               # List link neighbours
/gnosis:manage stats                                 # Corpus inventory + health

Bulk actions — see /gnosis:ingest:

• ingest ./docs --prune — re-ingest + drop chunks for missing files
• ingest ./docs --wipe — nuclear reset + reindex
• ingest git <repo> — commit history
• ingest crawl <url> — web crawl

Action: $ARGUMENTS

---

add — index a single document

1. Read the file at $path from disk.
2. Extract metadata:
   • Title: frontmatter title: if present, else first H1
   • Category: frontmatter category:, else first path segment
   • Audience: frontmatter audience:, default "all"
   • Tags: frontmatter tags: as a list
3. Upsert via mcp__gnosis__upsert_doc:

   path: "<relative path from repo root>"
   content: "<full file content>"
   title: "<extracted>"
   category: "<extracted>"
   audience: "<extracted>"
   tags: [...]
   

4. Verify via mcp__gnosis__get_doc(path=<path>) — expect the document back. If it returns empty, writes aren't enabled on the server or there was a silent failure.
5. Report {path, title, chunks_written} — chunk count should roughly be len(content) / 2000 at the v0.11 default chunk size.

Content size cap

upsert_doc refuses content larger than GNOSIS_MCP_MAX_DOC_BYTES (default 50 MB). For bigger files: split them or bump the cap.